From: Oliver Neukum <oneukum@suse.de>
To: roma1390 <roma1390@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: INFO: task khubd:271 blocked for more than 120 seconds.
Date: Wed, 16 Jun 2010 10:30:35 +0200 [thread overview]
Message-ID: <201006161030.36000.oneukum@suse.de> (raw)
In-Reply-To: <4C188AEA.3010109@gmail.com>
Am Mittwoch, 16. Juni 2010 10:27:22 schrieb roma1390:
> Hello,
>
> Oliver Neukum wrote:
> > Am Mittwoch, 16. Juni 2010 10:03:42 schrieb roma1390:
> >> Hello,
> >>
> >>
> >> We got this on our production system. Kernel: 2.6.26-2-amd64.
> >> This seems to be related with http://bugzilla.kernel.org/show_bug.cgi?id=13316 and still is open. Sadly to have such long standing bugs in common used subsystems like USB.
> >>
> >
> > Under which conditions did you get this? Physical unplug, S3 or S4?
> >
> > Regards
> > Oliver
>
> this was normal operation (no unplug, no S3 or something like that). This is on-line
> server. There is posible issue with usb device itself or physical usb port. Which
> sometimes causes device disconections, reconnections.
>
> Of course it's posible to fix on hardware level, but OS can't do such nasty things also.
Yes, this is a kernel bug. It would be helpful to have a bit more of context.
Could you post a bit more of your dmesg before the oops?
Regards
Oliver
next prev parent reply other threads:[~2010-06-16 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 8:03 INFO: task khubd:271 blocked for more than 120 seconds roma1390
2010-06-16 8:22 ` Oliver Neukum
2010-06-16 8:27 ` roma1390
2010-06-16 8:30 ` Oliver Neukum [this message]
[not found] ` <4C188F22.90808@gmail.com>
[not found] ` <201006161326.47203.oneukum@suse.de>
2010-06-16 12:22 ` roma1390
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=201006161030.36000.oneukum@suse.de \
--to=oneukum@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=roma1390@gmail.com \
/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