From: Logan Rathbone <loganrathbone@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: USB 2.0 (EHCI) keeps crapping out (3.2.29)
Date: Mon, 24 Dec 2012 22:02:11 -0500 [thread overview]
Message-ID: <50D91733.2040000@gmail.com> (raw)
*** 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
Devices that have previously been mounted and accessed successfully
begin giving input/output errors when I try to ls them.
rmmod'ing ehci_hcd and modprobe'ing it again resolves the issue until it
occurs again.
It *could* be a hardware problem, but it seems odd that unloading &
reloading the module instantly makes it work perfectly again.
Via USB 1.1/2.0 controller from circa 2002-2003.
If anyone has any ideas, please let me know...
logan@logancomp:~$ /sbin/lspci |grep -i usb
00:10.0 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.1 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.2 USB controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1
Controller (rev 80)
00:10.3 USB controller: VIA Technologies, Inc. USB 2.0 (rev 82)
logan@logancomp:~$ cat /proc/cmdline
auto BOOT_IMAGE=Slackware ro root=802 nohz=off highres=off
clocksource=jiffies acpi_enforce_resources=lax vt.default_utf8=0
next reply other threads:[~2012-12-25 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-25 3:02 Logan Rathbone [this message]
2012-12-25 4:10 ` USB 2.0 (EHCI) keeps crapping out (3.2.29) Rob Landley
2012-12-25 4:26 ` Logan Rathbone
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=50D91733.2040000@gmail.com \
--to=loganrathbone@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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