From: Greg KH <gregkh@suse.de>
To: Mark Lord <lkml@rtr.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: pl2303 ttyUSB0: pl2303_open - failed submitting interrupt urb, error -28
Date: Mon, 12 Jun 2006 15:23:04 -0700 [thread overview]
Message-ID: <20060612222304.GA21459@suse.de> (raw)
In-Reply-To: <448DE6EA.8020708@rtr.ca>
On Mon, Jun 12, 2006 at 06:12:58PM -0400, Mark Lord wrote:
> Greg KH wrote:
> >On Mon, Jun 12, 2006 at 05:54:21PM -0400, Mark Lord wrote:
> >>Okay, with these two patches from -mm, the USB no longer dies
> >>when I plug in my hub/dock device:
> >>
> >>gregkh-usb-improved-tt-scheduling-for-ehci.patch
> >>gregkh-usb-usb-rmmod-pl2303-after-28.patch
> >>
> >>So let's get these pushed upstream sooner than later, please!
> >
> >It will happen after 2.6.17 is out, as they are in the queue to do so.
>
> 2.6.18 will do, I suppose.
>
> But has the *real* bug been fixed with these patches,
> or merely "avoided" ?
The tt-scheduling patch should have fixed the "real" bug.
> Eg. If usb_submit_urb() ever fails again (low on memory, etc..)
> inside pl2303_open(), will we be back with the same bug?
>
> What's the *real* actual bug here?
There are two of them.
The fact that the urb submission in the pl2303 driver fails, and is now
handled properly is fixed in the pl2303 patch.
The fact that we can (hopefully) handle scheduling TT in the EHCI driver
fixes the real problem with plugging slow or full speed devices into a
USB 2.0 hub (not root hub). That's fixed by the tt patch.
So we should have finally covered both of them now.
thanks,
greg k-h
next prev parent reply other threads:[~2006-06-12 22:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 20:06 pl2303 ttyUSB0: pl2303_open - failed submitting interrupt urb, error -28 Mark Lord
2006-06-12 20:20 ` Mark Lord
2006-06-12 20:26 ` Lee Revell
2006-06-12 20:41 ` Mark Lord
2006-06-12 20:49 ` Greg KH
2006-06-12 20:56 ` Mark Lord
2006-06-12 21:15 ` Mark Lord
2006-06-12 21:28 ` Greg KH
2006-06-12 21:36 ` Mark Lord
2006-06-12 21:54 ` Mark Lord
2006-06-12 22:03 ` Greg KH
2006-06-12 22:12 ` Mark Lord
2006-06-12 22:23 ` Greg KH [this message]
2006-06-12 23:15 ` Mark Lord
2006-06-12 23:21 ` Mark Lord
2006-06-13 11:46 ` Frank Gevaerts
2006-06-13 16:26 ` Luiz Fernando N. Capitulino
2006-06-13 17:45 ` Luiz Fernando N. Capitulino
2006-06-14 11:52 ` [PATCH] clean tty fields on failed device open Frank Gevaerts
2006-06-14 13:49 ` Luiz Fernando N. Capitulino
2006-06-14 13:52 ` Frank Gevaerts
2006-06-14 14:13 ` Luiz Fernando N. Capitulino
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=20060612222304.GA21459@suse.de \
--to=gregkh@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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