From: Greg KH <gregkh@suse.de>
To: "Éric Piel" <E.A.B.Piel@tudelft.nl>
Cc: Alan Stern <stern@rowland.harvard.edu>,
LKML <linux-kernel@vger.kernel.org>,
linux-usb@vger.kernel.org, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Regression 3.0-rc5+ : khubd blocked
Date: Fri, 1 Jul 2011 06:29:19 -0700 [thread overview]
Message-ID: <20110701132919.GB8902@suse.de> (raw)
In-Reply-To: <4E0DC172.9010504@tudelft.nl>
On Fri, Jul 01, 2011 at 02:45:38PM +0200, Éric Piel wrote:
> Hello,
> I've come across to what looks like a regression in the kernel a
> few commits after 3.0-rc5.
>
> When I turn off a usb hub, to which my mouse and keyboard are connected,
> and then turn it on again, they are not detected again. After unplugging
> it and waiting a few minutes I get a "task khubd:621 blocked for more
> than 120 seconds."
>
> I haven't investigated much. It seems reproducible here on my x86_64
> laptop. It doesn't seem to happen on a 3.0-rc4. Maybe important, my
> kernel already has commit 2e34b429a404675dc4fc4ad2ee339eea028da3ca
> "Merge branch 'usb-linus' of
> git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb-2.6"
>
> Let me know if you need me to investigate more, or maybe there is
> already a fix for that bug?
Can you run 'git bisect' to track it down to the exact patch that causes
the problem?
thanks,
greg k-h
next prev parent reply other threads:[~2011-07-01 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 12:45 Regression 3.0-rc5+ : khubd blocked Éric Piel
2011-07-01 13:29 ` Greg KH [this message]
2011-07-01 15:21 ` Alan Stern
2011-07-01 15:41 ` Éric Piel
2011-07-01 16:12 ` Sarah Sharp
-- strict thread matches above, loose matches on Subject: below --
2011-07-01 16:20 Éric Piel
2011-07-01 17:19 ` Alan Stern
2011-07-01 20:08 ` Sarah Sharp
2011-07-01 20:40 ` Alan Stern
2011-07-01 20:53 ` Sarah Sharp
2011-07-01 22:05 ` Éric Piel
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=20110701132919.GB8902@suse.de \
--to=gregkh@suse.de \
--cc=E.A.B.Piel@tudelft.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.