On Mon, 2 Oct 2006, matthieu castet wrote: > Hi, > > Alan Stern wrote: > > > > > > > You can start by turning on CONFIG_USB_DEBUG for your kernel and then > > posting a copy of the dmesg log showing what happens when one of those > > peculiar disconnects occurs. Post also a stack trace (Alt-SysRq-T); the > > khubd process is the one that matters most. > I had to comment > usb 4-2: link qh0-00ff/f7e2c180 start 0 [2/0 us] > usb 4-2: unlink qh0-00ff/f7e2c180 start 0 [2/0 us] > because it flooded my log. > > When it fails I got : > > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: fatal command > 010039 (park)=0 ithresh=1 Async Periodic period=256 RUN > Oct 2 20:25:20 localhost kernel: ehci_hcd > 0000:00:10.3: fatal status e008 Async Periodic Recl FLR > Oct 2 20:25:20 localhost > kernel: ehci_hcd 0000:00:10.3: fatal command 010039 (park)=0 ithresh=1 > Async Periodic period=256 RUN Oct 2 > 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: fatal status e008 > Async Periodic Recl FLR > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: > fatal command 010039 (park)=0 ithresh=1 Async Periodic period=256 RUN > Oct 2 20:25:20 localhost kernel: > ehci_hcd 0000:00:10.3: fatal status e008 Async Periodic Recl FLR > Oct 2 20:25:20 localhost kernel: hub 4-0:1.0: state 7 ports 6 chg 0000 > evt 0004 > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: GetStatus port > 2 status 00180b POWER sig=j PEC CSC CONNECT > Oct 2 20:25:20 localhost kernel: hub 4-0:1.0: port 2, status 0501, > change 0003, 480 Mb/s > Oct 2 20:25:20 localhost kernel: usb 4-2: USB disconnect, address 2 > Oct 2 20:25:20 localhost kernel: usb 4-2: usb_disable_device nuking all > URBs > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: shutdown urb > f7b6f7ac pipe c0010280 ep2in-bulk > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: shutdown urb > f7b6f720 pipe c0010280 ep2in-bulk > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: shutdown urb > f7b6f694 pipe c0010280 ep2in-bulk > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: shutdown urb > f7b6f8c4 pipe c0010280 ep2in-bulk > Oct 2 20:25:20 localhost kernel: ehci_hcd 0000:00:10.3: shutdown urb > f7b6f838 pipe c0010280 ep2in-bulk > Oct 2 20:25:20 localhost kernel: zd1211rw 4-2:1.0: zd_chip_control_leds > error -19 > Oct 2 20:25:51 localhost last message repeated 31 times > Oct 2 20:26:37 localhost last message repeated 46 times
That "fatal command" and "fatal status" stuff doesn't look good. > The stack trace is : > Oct 2 20:28:47 localhost kernel: khubd D 0000000A 0 93 > 6 95 10 (L-TLB) > Oct 2 20:28:47 localhost kernel: c39e5e9c 00000046 00000001 > 0000000a c39acab0 3dd3db96 000004f9 000001e8 > Oct 2 20:28:47 localhost kernel: c39acbc0 c39e5ea4 00000000 > 0c16cbbf 00000000 0013827e 0013827e f75242ec > Oct 2 20:28:47 localhost kernel: f7ba3200 c028960b c0357f18 > c0357f18 0013827e c011e077 c39acab0 c0357b20 > Oct 2 20:28:47 localhost kernel: Call Trace: > Oct 2 20:28:47 localhost kernel: [<c028960b>] schedule_timeout+0x7a/0x95 > Oct 2 20:28:47 localhost kernel: [<c011e077>] process_timeout+0x0/0x5 > Oct 2 20:28:47 localhost kernel: [<f887b5fe>] > ehci_endpoint_disable+0xae/0x15e [ehci_hcd] > Oct 2 20:28:47 localhost kernel: [<c0220b6a>] > hcd_endpoint_disable+0x1b5/0x1bd > Oct 2 20:28:47 localhost kernel: [<c02219f2>] > usb_disable_endpoint+0x4e/0x4f > Oct 2 20:28:47 localhost kernel: [<c0221b23>] > usb_disable_device+0x62/0x12d > Oct 2 20:28:47 localhost kernel: [<c021d9f7>] usb_disconnect+0x85/0x109 > Oct 2 20:28:47 localhost kernel: [<c021e94a>] hub_thread+0x556/0xd3d > Oct 2 20:28:47 localhost kernel: [<c011351e>] try_to_wake_up+0xed/0x10b > Oct 2 20:28:47 localhost kernel: [<c0288d15>] schedule+0x537/0x551 > Oct 2 20:28:47 localhost kernel: [<c0126ae9>] > autoremove_wake_function+0x0/0x2d > Oct 2 20:28:47 localhost kernel: [<c021e3f4>] hub_thread+0x0/0xd3d > Oct 2 20:28:47 localhost kernel: [<c0126a35>] kthread+0xad/0xd8 > Oct 2 20:28:47 localhost kernel: [<c0126988>] kthread+0x0/0xd8 > Oct 2 20:28:47 localhost kernel: [<c0101005>] kernel_thread_helper+0x5/0xb You could try using 2.6.18-mm1. There was a change made to ehci-hcd in order to work around a bug in the VIA controllers. It looks like that same bug may be affecting you. Alan Stern ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
