Skip to contentSkip to conversation

2.6.21-rc6 USB Keyboard hangs (EHCI/UHCI/HID)

DISCUSSION Matthias Andree 2 participants 5 messages Apr 9, 2007 – Apr 15, 2007

lore
Share & tools
lore
#0 lore raw

Please Cc: me on replies, as I read linux-kernel sporadically and am not subscribed to linux-usb-devel at all.

Greetings,

I have seen my USB keyboard drivers lock up several times now with my M$ Natural Ergonomic Keyboard, both on SUSE 10.2's current kernel as well as 2.6.21-rc6 today. I don't ever recall this happen with older SUSE 10.0 kernels. The keyboard is connected to a USB2.0 hub with single transaction translator (at least that's what FreeBSD 6.2 says), which is connected to a via root hub.

Symptoms are that the keyboard LEDs go off and no further input is impossible (I'm typing this into a PS/2 keyboard). Replugging does not help. Trying to unload ehci-hcd hangs modprobe, and additionally I've got a stuck khubd (not sure if that's related), else no logging.

I'm rebuilding the kernel with HID/USB debugging cranked up to see if I can get some detail out of the situation. Any specific kernel debugging options that might help me debug this further?

Thanks,

Signature · 1 line
Matthias Andree
#1 lore raw
Quoted 12 lines · Matthias Andree

Please Cc: me on replies, as I read linux-kernel sporadically and am not subscribed to linux-usb-devel at all.

Greetings,

I have seen my USB keyboard drivers lock up several times now with my M$ Natural Ergonomic Keyboard, both on SUSE 10.2's current kernel as well as 2.6.21-rc6 today. I don't ever recall this happen with older SUSE 10.0 kernels. The keyboard is connected to a USB2.0 hub with single transaction translator (at least that's what FreeBSD 6.2 says), which is connected to a via root hub.

Quoted 8 lines

Symptoms are that the keyboard LEDs go off and no further input is impossible (I'm typing this into a PS/2 keyboard). Replugging does not help. Trying to unload ehci-hcd hangs modprobe, and additionally I've got a stuck khubd (not sure if that's related), else no logging.

I'm rebuilding the kernel with HID/USB debugging cranked up to see if I can get some detail out of the situation. Any specific kernel debugging options that might help me debug this further?

It would help to see a trace from usbmon showing what happens during a lockup. You can find the instructions in the kernel source file Documentation/usb/usbmon.txt.

To help keep the trace simple, try to avoid plugging any other USB devices into that hub or any other high-speed USB devices into the computer.

Also, it might help to see a stack trace of khubd (Alt-SysRq-T) when it gets stuck.

Alan Stern

#2 lore raw
Quoted 27 lines · Alan Stern
Quoted 12 lines · Matthias Andree

Please Cc: me on replies, as I read linux-kernel sporadically and am not subscribed to linux-usb-devel at all.

Greetings,

I have seen my USB keyboard drivers lock up several times now with my M$ Natural Ergonomic Keyboard, both on SUSE 10.2's current kernel as well as 2.6.21-rc6 today. I don't ever recall this happen with older SUSE 10.0 kernels. The keyboard is connected to a USB2.0 hub with single transaction translator (at least that's what FreeBSD 6.2 says), which is connected to a via root hub.

Quoted 8 lines

Symptoms are that the keyboard LEDs go off and no further input is impossible (I'm typing this into a PS/2 keyboard). Replugging does not help. Trying to unload ehci-hcd hangs modprobe, and additionally I've got a stuck khubd (not sure if that's related), else no logging.

I'm rebuilding the kernel with HID/USB debugging cranked up to see if I can get some detail out of the situation. Any specific kernel debugging options that might help me debug this further?

It would help to see a trace from usbmon showing what happens during a lockup. You can find the instructions in the kernel source file Documentation/usb/usbmon.txt.

Quoted 5 lines

To help keep the trace simple, try to avoid plugging any other USB devices into that hub or any other high-speed USB devices into the computer.

Also, it might help to see a stack trace of khubd (Alt-SysRq-T) when it gets stuck.

I arrived at the computer today, to find khubd in D state again, but unfortunately, it does not show up in Alt-SysRq-T output. Do kernel threads show up there at all? 2.6.18.8-0.1 with SUSE patches on openSUSE 10.2.

I had stopped usbmon before however, so I don't know what the events have been leading to this lockup. Sorry. I'll leave usbmon running now.

Signature · 1 line
Matthias Andree
#3 lore raw
Quoted 4 lines · Matthias Andree

I arrived at the computer today, to find khubd in D state again, but unfortunately, it does not show up in Alt-SysRq-T output. Do kernel threads show up there at all? 2.6.18.8-0.1 with SUSE patches on openSUSE 10.2.

As far as I know, all tasks including kernel threads should show up. They certainly do on my machine. However you're the second person to report that khubd doesn't appear after getting stuck in a D state.

Clearly something strange is going on. I wish I knew what it was...

Quoted 2 lines

I had stopped usbmon before however, so I don't know what the events have been leading to this lockup. Sorry. I'll leave usbmon running now.

Something else you can do is turn on CONFIG_USB_DEBUG and then check the dmesg log for anything significant.

Alan Stern

#4 lore raw
Quoted 7 lines · Alan Stern
Quoted 4 lines · Matthias Andree

I arrived at the computer today, to find khubd in D state again, but unfortunately, it does not show up in Alt-SysRq-T output. Do kernel threads show up there at all? 2.6.18.8-0.1 with SUSE patches on openSUSE 10.2.

Quoted 5 lines

As far as I know, all tasks including kernel threads should show up. They certainly do on my machine. However you're the second person to report that khubd doesn't appear after getting stuck in a D state.

Clearly something strange is going on. I wish I knew what it was...

Me too. Thanks for your patience. We'll track this down. A german proverb is "Mühsam ernährt sich das Eichhörnchen" which means we're collecting our pieces (literally food), but very slowly and hard.

Quoted 5 lines
Quoted 2 lines

I had stopped usbmon before however, so I don't know what the events have been leading to this lockup. Sorry. I'll leave usbmon running now.

Something else you can do is turn on CONFIG_USB_DEBUG and then check the dmesg log for anything significant.

That would require recompiling a production kernel, but I've now backgrounded usbmon spamming my disk, with just the keyboard attached to the external USB2.0 hub (the other device would have been my Eizo FlexScan L768 19" TFT) in the hope that it will come up with something, should khubd hang again before Friday...

Best regards,

Signature · 1 line
Matthias Andree