Arch Linux

Cannot reproduce on my 32-bit Arch, everything works fine.

I suppose it is a good idea to attach my rc.conf file perhaps there is another module that is causing my issues.

One more thing: if you upgrade your kernel, you need to reboot to get the modules working properly.

The problem persists through reboots. I have also tried ACPI=off noapic and nolapic boot options to no avail.

Please let me know if I can do anything additional to help get to the bottom of this. I find it interesting that devices work fine if the USB module is reloaded. It makes me think that the module is talking to the USB device just fine, but it is not getting the interrupt for new devices for one reason or the other. I'm not sure what has changed to stop this. I think I will just start downgrading my kernel till it works again. I'll let you know what I find.

downgrading to kernel 3.2.2.-1 fixed the Issue. So the problem is with the kernel sometime after that. Also, had to downgrade the virtual box modules and the nvidia driver, but I don't think these are the issue. Any thoughts at this point would be helpful.

This is the config for 3.2.2-1:

This is the diff between the 3.2.2 kernel config and the 3.3.2 kernel config. I figure this will be more helpful.

I have the same bug with a 2008 Macbook(4,1) running archbang latest with 3.3.5-1-ARCH

My user is added to the proper groups (dbus, storage, disk). Nothing new appears in /sys/block after inserting a USB drive. Running lsusb -v detects the usb properly. It seems like a kernel issue, please fix this!

i have found a fix for this issue: append this line to you /etc/rc.local and reboot:

modprobe -r ehci-hcd

Everything works fine after this!

With this you disable USB2.0 support.

I am aware of this. Oddly enough reloading the module shortly after does the trick for good.

I can confirm this on my machine as well (HP Mini 5103, 32-bit system), I even tried kernel 3.4.0 from testing. Also tried removing virtualbox modules completely (and rebooting, of course), just to see if they're not causing the issue, but no luck.

Reloading the module doesn't work for good, it only detects connected devices. If I connect any other device (or remove and reconnect the same device) afterwards, situation remains, device remains undetected.

For me it seems the problem was actually caused by laptop-mode-tools setting the USB ports to autosuspend. Disable that if you are using laptop-mode-tools.

I've been affected by what seems to be a similar issue, but it doesn't occur at boot. If I move a lot of data over USB, ehci_hcd hangs and all USB devices quit responding. This happens with several hard disk, my mobile phone and my USB wireless card. sudo rmmod ehci_hcd && sudo modprobe ehci_hcd brings it all back up.

I will run a full update this weekend, repro the issue and pull some data. Hopefully there will be something helpful in there.

Another workaround is to turn off autosuspend entirely. Specify usb.autosuspend=-1 for the kernel.
P.S. I suppose this is an upstream issue.

I have the same problem with the boot, with the extra that modprobe --remove ehci_hcd results in:
[ 960.423296] INFO: task modprobe:912 blocked for more than 120 seconds.
[ 960.423302] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
and the modprobe to go into uninterruptable sleep.
This also happens if run in rc.local (unable to boot that way)

At boot usb devices are detected correctly, but after that only removing them works.
Removing and plugging in a device that has been detected:
[ 1250.500027] usb 3-1: USB disconnect, device number 2

I guess the most important lines from rc.conf:

MOD_AUTOLOAD="yes"
MODULES=()
DAEMONS=(syslog-ng network netfs crond dbus ntpdate sshd fam samba gdm tvheadend httpd)

Affected kernels noticed: 3.4.6, 3.4.7
Not a laptop.


I've been having problems with USB earlier. From some point in 2.6.3x or so
khubd started crashing randomly, going into uninterruptable sleep. All devices that
were working at the time (mouse) continued to work, but devices like dvb card and
webcam could not be connected to afterwards. I'm not sure if this problem persists,
it did continue to the 3.2.x at least, but I haven't seen khubd halt in 3.3.x.

All that time rmmod ehci_hcd has halted.
This is should not be a hardware problem, I have changed everything but the display
around the installation.

Is there a bug report in bugzilla.kernel.org for this?

Still a problem with 3.6.6?

3.6.6-1 still affected for me.

Status on 3.7.x?

I can confirm this is still an issue on kernel 3.6.11-1 x86_64
Has no one resolved this?
It seems the suggestion of
"Specify usb.autosuspend=-1 for the kernel."
would be an acceptable work around for a desktop that is always on. can someone tell me where the config file is and/or how to change this option?

tpowa, I still see this on 3.7.4, but I use a custom kernel.

ssgross, see https://wiki.archlinux.org/index.php/Kernel_parameters

Status on 3.8?

Afectby me in 3.8 but The workaround forusb.susoend=-1 solve the problem here

Status on 3.9?

For me was fix'd but I don't know