Created attachment 22788 [details]
2.6.31rc6 kernel log
The usb subsystem seems to completely crash at random intervals of time. Sometime it happens 5 minutes from boot, sometimes 30 mins, and sometime 5-8hrs from boot. I first experienced this issue somewhere in the 2.6.30.* tree.
Usually what happens is that I will be using X and my mouse stops responding. As you probably figured my mouse is a usb mouse. However, I can use the keyboard (non-usb) and X is still alive. If I attempt to plug in a usb flash drive nothing shows up in dmesg (2.6.31rc6) or on 22.214.171.124 I get a kernel trace.
I have attached the dmesg and kernel.log files from 2.6.31rc6 along with the dmesg output from 126.96.36.199.
Let me know how I can help or if you need any more information.
Created attachment 22789 [details]
dmesg log 2.6.31rc6
Created attachment 22790 [details]
188.8.131.52 demsg log
Can you provide the output in the kernel log for running Alt-Sysrq-T when you feel the USB subsystem is locked up? We need some hint as to what is going on here.
Alright, I will do that the next time the usb system locks up.
Created attachment 22797 [details]
kernel.log w/ Sysrq+T output
Sysrq+T output around 19:08
This time the freeze happened when I was away from the computer so I am not sure if the Sysrq+T output will be helpful.
However, I rmmod ehci_hcd and that resulted in usb working again. After, I modprobe ehci_hcd and usb continues to work, for right now. I suppose this suggests that the ehci_hcd module is the one causing problems.
>I first experienced this issue somewhere in the 2.6.30.* tree.
that means it did not happen with older kernel releases ?
if you are unsure, could you test with older kernels?
That would be correct. I built this machine in July, when I believe the kernel release was at 2.6.27 or 2.6.28 and usb was fine. I'd say within the last month I started noticing problems.
would you dare to try git-bisecting this problem or at least try to determine, which kernel release worked without problems and with what kernel release the problem started to happen ? having exact information like that makes troubleshooting easier....
I will try to narrow it down to the first major release in which the problem started to occur. Then I will do a git bisect. This might take a while, because I may not experience the problem for 7-8hrs.
Just an update. I updated the nvidia drivers to the newest beta release and it seems as if the problem has gone away. I haven't experienced the issue for the past two days.
It seems that the binary drivers were some how taunting the kernel's usb subsystem.
Imagine that :(
thanks for letting us know, I'll close this out.
another proof, that kernel issues with closed-sourc modules loaded shouldn´t be investigated until those modules are unloaded. i have overseen that the kernel was tainted.....