On Tue, 23 Mar 2004, Ari Pollak wrote: > Attached is the output of alt-sysrq-t. I noticed that there is no > mention of khubd in the trace output while the mouse is connected, but > it does show up in the output before I connect a mouse. Also, removing > usbmouse and hid modules while the USB mouse is connected does succeed.
If you then unplug the mouse after removing usbmouse and hid, do you still get the suspend_hc/wakeup_hc problem? > I also noticed this in ps output. Notice "D" under the STAT column. > root 835 0.0 0.0 0 0 ? DW 13:02 0:00 [khubd] I'm a little unclear about the the timing here. Was the ps command run before the mouse was connected? If it was, then you're right, something's funny. Normally khubd waits in an interruptible sleep. Or was the ps command run after the mouse was connected? In that case, khubd ought to show up in the task dump also. It's possible that your syslog daemon managed to lose some of the data from the task dump; dmesg will be more reliable. It seems clear that khubd is blocked waiting for _something_. I would like to know what. Best approach: Do Alt-SysRq-t (with dmesg to capture the output) before connecting the mouse, again while the mouse is connected, and then after the mouse is disconnected. To minimize the length of the task list, you can turn off your X server first. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
