From: Logan Rathbone <loganrathbone@gmail.com>
To: Rob Landley <rob@landley.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: USB 2.0 (EHCI) keeps crapping out (3.2.29)
Date: Mon, 24 Dec 2012 23:26:56 -0500 [thread overview]
Message-ID: <50D92B10.8080508@gmail.com> (raw)
In-Reply-To: <1356408600.31232.2@driftwood>
On 12/24/2012 11:10 PM, Rob Landley wrote:
> On 12/24/2012 09:02:11 PM, Logan Rathbone wrote:
>> *** NOTE: Kindly CC me directly if you reply to list since I'm not an
>> LKML subscriber. ***
>>
>> Running vanilla 3.2.29 (Slackware 14.0). I also had this issue on
>> 2.6.37.6 and *possibly* 2.6.33.x, but I don't recall.
>>
>> Every now and again (could be every few days, could take a couple of
>> weeks...
>> depends.) USB 2.0 stops working. My scanner as well as certain
>> mass-storage
>> devices that are USB-2.0 compatible fail to function all of a sudden.
>>
>> With the said mass storage devices, I get lots of errors like this in
>> my logs:
>>
>> hub 1-0:1.0: unable to enumerate USB device on port 3
>
> What is the _first_ error that shows up in dmesg when the failure occurs?
I *think* this is the first error that appears:
usb 1-3: USB disconnect, device number 3
sd 5:0:0:0: Device offlined - not ready after error recovery
That second message is sometimes:
usblp0: removed
But honestly I can't recall if my USB 2.0 printer stopped working at
that point in time. The effect of the crap-out is mainly noticeable on
my mass storage devices since I can't mount them (the device nodes do
not get created by udev until I rmmod & modprobe ehci_hcd again or reboot).
I also see stuff like this scattered throughout (hard to tell if it's
one of the first or last errors that pops up though... I think it's the
last. It usually pops up after a whole whack of the "unable to
enumerate" errors:
ehci_hcd 0000:00:10.3: force halt; handshake f8044014 0000c000 00000000
-> -110
prev parent reply other threads:[~2012-12-25 4:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 3:02 USB 2.0 (EHCI) keeps crapping out (3.2.29) Logan Rathbone
2012-12-25 4:10 ` Rob Landley
2012-12-25 4:26 ` Logan Rathbone [this message]
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=50D92B10.8080508@gmail.com \
--to=loganrathbone@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.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