From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Greg KH <greg@kroah.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: 3.0-rc6: USB khubd deadlock when hub is powered down
Date: Thu, 7 Jul 2011 13:42:03 -0700 [thread overview]
Message-ID: <20110707204203.GA13931@xanatos> (raw)
In-Reply-To: <20110707212449.261ffa78@stein>
On Thu, Jul 07, 2011 at 09:24:49PM +0200, Stefan Richter wrote:
> On Jul 07 Greg KH wrote:
> > Can you test Linus's tree, along with a patch sent yesterday from Alan
> > Stern to the linux-usb mailing list (attached below)? That should
> > resolve this issue, if not, please let us know.
>
> OK. I am using 3.0-rc6-71-g4dd1b49 plus Alan's "USB: additional
> regression fix for device removal" now. So far it survived a dozen of
> power toggles of the hub and the attached devices. Thanks.
>
> Alan Stern wrote:
> > Still, we need to rewrite this stuff. A possible race remains,
>
> On a general level, the last few kernel.org releases have all been rather
> weak. Dissatisfied,
For USB regressions or the kernel overall? Yes, last kernel release had
some nasty regressions-disguised-as-bug-fixes in the USB tree as well.
My fault there, not sure how to improve other than coming up with a list
of every possible plug-unplug/reset/configure/alt setting change
combination possible and testing before sending any thing at all.
Suggestions welcome, testing appreciated.
Sarah Sharp
next prev parent reply other threads:[~2011-07-07 20:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 8:05 Stefan Richter
2011-07-07 13:29 ` Stefan Richter
2011-07-07 13:38 ` Stefan Richter
2011-07-07 14:10 ` Greg KH
2011-07-07 19:24 ` Stefan Richter
2011-07-07 20:42 ` Sarah Sharp [this message]
2011-07-07 21:56 ` Stefan Richter
2011-07-08 14:12 ` Alan Stern
2011-07-08 17:43 ` Stefan Richter
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=20110707204203.GA13931@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stefanr@s5r6.in-berlin.de \
--cc=stern@rowland.harvard.edu \
/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®