linux-kernel - Re: USB 2.0 (EHCI) keeps crapping out (3.2.29)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 24 Dec 2012 23:26:56 -0500
From:	Logan Rathbone <loganrathbone@...il.com>
To:	Rob Landley <rob@...dley.net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: USB 2.0 (EHCI) keeps crapping out (3.2.29)



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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/