Re: khbud stuck in D state

[Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>]

On Sun, 18 Nov 2007, Andrew Morton wrote:

> On Sun, 18 Nov 2007 01:51:12 -0800 Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> 
> > Running RH 2.6.23.1-49.fc8 on a new laptop (lenovo t61p).  Unplugged the
> > serial mouse, plugged it into the other port, plugged my camera into the
> > original port and found everything in USB land to be dead.
> > 
> > 
> > dmesg:
> > 
> > usb 5-2: USB disconnect, address 2
> > 
> > (that's it)
> > 
> > That was the mouse:
> > 
> > Nov 17 16:28:45 t61p kernel: usb 5-2: new low speed USB device using uhci_hcd and address 2
> > Nov 17 16:28:45 t61p kernel: usb 5-2: configuration #1 chosen from 1 choice
> > Nov 17 16:28:46 t61p kernel: input: Microsoft Microsoft Wireless Optical Mouse® 1.00 as /class/input/input11
> > Nov 17 16:28:46 t61p kernel: input: USB HID v1.11 Mouse [Microsoft Microsoft Wireless Optical Mouse® 1.00] on usb-0000:00:1d.0-2                       
> > 
> > khubd is here:
> > 
> > Nov 17 17:46:44 t61p kernel: khubd         D ffff81007ed95be0     0   205      2
> > Nov 17 17:46:44 t61p kernel:  ffff81007ed95c30 0000000000000046 0000000000000000 ffffffff8102e900
> > Nov 17 17:46:44 t61p kernel:  ffff81007ed95cf0 ffff81007ed9a000 ffffffff81370660 ffff81007ed9a278
> > Nov 17 17:46:44 t61p kernel:  000000007ed95bf0 ffff81007ed95c40 ffffffffffffffff 0000000100485032
> > Nov 17 17:46:44 t61p kernel: Call Trace:
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff8102e900>] find_busiest_group+0x25b/0x6a2
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff8125bc22>] schedule_timeout+0x8a/0xad
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff8103f48e>] process_timeout+0x0/0x5
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff8125bc1d>] schedule_timeout+0x85/0xad
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff8125b77b>] wait_for_completion_timeout+0x96/0xd7
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff81030e96>] default_wake_function+0x0/0xe
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff811ad8a8>] usb_start_wait_urb+0x67/0xa6
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff811adae2>] usb_control_msg+0xc8/0xeb
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff811a8c1c>] hub_port_init+0x37a/0x572
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff811aa2e1>] hub_thread+0x65f/0xc08
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff810493dd>] autoremove_wake_function+0x0/0x2e
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff811a9c82>] hub_thread+0x0/0xc08
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff81049288>] kthread+0x47/0x73
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff8100c9e8>] child_rip+0xa/0x12
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff81049241>] kthread+0x0/0x73
> > Nov 17 17:46:44 t61p kernel:  [<ffffffff8100c9de>] child_rip+0x0/0x12
> > Nov 17 17:46:44 t61p kernel: 
> > 
> > Will fiddle with it a bit.
> 
> ooh, the mouse came back to life.  The camera has still not been noticed.
> 
> lsusb takes about 30 seconds then says
> 
> Bus 002 Device 001: ID 0000:0000  
> Bus 007 Device 001: ID 0000:0000  
> Bus 006 Device 002: ID 17ef:1003  
> Bus 006 Device 001: ID 0000:0000  
> Bus 005 Device 003: ID 045e:00e1 Microsoft Corp. 
> Bus 005 Device 001: ID 0000:0000  
> Bus 001 Device 001: ID 0000:0000  
> Bus 004 Device 001: ID 0000:0000  
> Bus 003 Device 003: ID 0a5c:2110 Broadcom Corp. 
> Bus 003 Device 002: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
> Bus 003 Device 001: ID 0000:0000  

Is this still not working?  Does it work any better with a vanilla 
2.6.23.1 kernel?  What does CONFIG_USB_DEBUG reveal?

Alan Stern


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel