From: Colin Leroy <colin.lkml@colino.net>
To: David Brownell <david-b@pacbell.net>
Cc: linux-usb-devel@lists.sourceforge.net,
Colin Leroy <colin@colino.net>,
Linux-kernel@vger.kernel.org,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>
Subject: Re: [linux-usb-devel] [PATCH] Ohci-hcd: fix endless loop (second take)
Date: Fri, 26 Nov 2004 18:37:49 +0100 [thread overview]
Message-ID: <20041126183749.1a230af9@jack.colino.net> (raw)
In-Reply-To: <200411260928.18135.david-b@pacbell.net>
On 26 Nov 2004 at 09h11, David Brownell wrote:
Hi,
> So instead of waiting a moment for the ED to finish
> its normal processing and move from state ED_UNLINK
> into ED_IDLE, you want to always clobber the whole
> USB device tree attached to that bus? That'd happen
> quite routinely.
Yeah. Sorry. Also, just noticed that this patch seemed
to work because I overlooked the unsigned bit, makeing my
hack not go though sanitize - which changes eb->state and
thus does not get back to the ED_UNLINK path. Duh... I must
have been tired.
> This isn't a good patch either... maybe your best
> bet would be to find out why the IRQs stopped getting
> delivered.
It's probably a linux-wlan-ng issue... What do you think
of these logs ?
#resume logs...
#disconnecting the stick:
usb 4-1: USB disconnect, address 2
ohci_hcd 0001:10:1b.1: IRQ INTR_SF lossage
hfa384x_usbin_callback: Fatal, failed to resubmit rx_urb. error=-19
hfa384x_dorrid: ctlx failure=REQ_TIMEOUT
prism2sta_mlmerequest: Failed to read eth1 statistics: error=-5
#reconnecting the stick:
usb 4-1: new full speed USB device using address 3
usb 4-1: control timeout on ep0out
maybe the lwlan driver should catch these and kill the urbs or
something?
Thanks for your help, I'm not an expert at all in the usb world...
--
Colin
next prev parent reply other threads:[~2004-11-27 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-26 10:30 Colin Leroy
2004-11-26 17:28 ` [linux-usb-devel] " David Brownell
2004-11-26 17:37 ` Colin Leroy [this message]
2004-11-26 17:57 ` David Brownell
2004-11-26 22:12 ` Benjamin Herrenschmidt
2004-11-29 8:04 ` Colin Leroy
2004-11-29 22:26 ` Benjamin Herrenschmidt
2004-11-29 22:34 ` Colin Leroy
2004-11-29 22:43 ` Benjamin Herrenschmidt
2004-11-30 0:41 ` David Brownell
2004-11-26 18:46 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041126183749.1a230af9@jack.colino.net \
--to=colin.lkml@colino.net \
--cc=Linux-kernel@vger.kernel.org \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=colin@colino.net \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®