On Tue, Dec 04, 2012 at 04:55:26PM -0500, Alan Stern wrote: > On Tue, 4 Dec 2012, Piergiorgio Sartor wrote: > > > Hi Alan, > > > > thanks for the patch. > > > > One question, which kernel version should I use > > for this patch? > > > > It's the latest from git? > > I think it should work with any fairly recent kernel. The patch was > written against linux-next from about six weeks ago. I don't think > much has changed in this area for a while. > > Alan Stern Hi Alan, the output of lspci: 00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3) (prog-if 20 [EHCI]) Subsystem: ASUSTeK Computer Inc. Device 81c0 Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 22 Memory at fe02e000 (32-bit, non-prefetchable) [size=256] Capabilities: [44] Debug port: BAR=1 offset=0098 Capabilities: [80] Power Management version 2 Kernel driver in use: ehci_hcd --- --- --- --- The output of "dmesg" with your patch: [ 773.387144] ehci_hcd 0000:00:0b.1: Waited too long for the async schedule status (0/8000), giving up [ 803.804848] ehci_hcd 0000:00:0b.1: alan start cur time 4295471040 last scan 4295440395 [ 803.804862] ehci_hcd 0000:00:0b.1: command 10035 cmd reg 10035 io watchdog 1 async count 10 [ 803.804868] ehci_hcd 0000:00:0b.1: async list: [ 803.804876] ehci_hcd 0000:00:0b.1: qh ffff880149fe7800 hw ffff8800af800000 dma af800000 next ffff880148305600 hw_next af800de2 [ 803.804884] ehci_hcd 0000:00:0b.1: qh ffff880148305600 hw ffff8800af800de0 dma af800de0 next ffff88013d09b200 hw_next af800d22 [ 803.804891] ehci_hcd 0000:00:0b.1: qh ffff88013d09b200 hw ffff8800af800d20 dma af800d20 next ffff8801498aca00 hw_next af800ae2 [ 803.804897] ehci_hcd 0000:00:0b.1: qh ffff8801498aca00 hw ffff8800af800ae0 dma af800ae0 next ffff880147a7cf00 hw_next af800c62 [ 803.804904] ehci_hcd 0000:00:0b.1: qh ffff880147a7cf00 hw ffff8800af800c60 dma af800c60 next ffff880147b28680 hw_next af800a22 [ 803.804911] ehci_hcd 0000:00:0b.1: qh ffff880147b28680 hw ffff8800af800a20 dma af800a20 next ffff88013d1f4c00 hw_next af800f02 [ 803.804917] ehci_hcd 0000:00:0b.1: qh ffff88013d1f4c00 hw ffff8800af800f00 dma af800f00 next ffff880147733100 hw_next af800ba2 [ 803.804924] ehci_hcd 0000:00:0b.1: qh ffff880147733100 hw ffff8800af800ba0 dma af800ba0 next ffff880147971100 hw_next af800782 [ 803.804930] ehci_hcd 0000:00:0b.1: qh ffff880147971100 hw ffff8800af800780 dma af800780 next ffff880147971e00 hw_next af8008a2 [ 803.804937] ehci_hcd 0000:00:0b.1: qh ffff880147971e00 hw ffff8800af8008a0 dma af8008a0 next ffff880147b24b80 hw_next af800962 [ 803.804944] ehci_hcd 0000:00:0b.1: qh ffff880147b24b80 hw ffff8800af800960 dma af800960 next (null) hw_next af800002 [ 803.804951] ehci_hcd 0000:00:0b.1: This qh link time 4295440580 enqueue time 4295440580 td token 1f8c80 ov token 0 [ 803.804959] ehci_hcd 0000:00:0b.1: qh ffff880148305600 naf800d22 info 42002215 40000000 qtd 96f91ae0 [ 803.804967] ehci_hcd 0000:00:0b.1: overlay td ffff8800af800df0 n96f910c0 00000001 t00000000 p0=af824d9f [ 803.804975] ehci_hcd 0000:00:0b.1: dma 96f910c0 td ffff880096f910c0 n96f91de0 00000001 t001f8c80 p0=af824d80 [ 803.804982] ehci_hcd 0000:00:0b.1: dummy 96f91de0 td ffff880096f91de0 n00000001 00000001 t00000040 p0=00000000 [ 803.816026] ehci_hcd 0000:00:0b.1: giveback urb ffff88014755e6c0 actual 0 [ 803.816034] ehci_hcd 0000:00:0b.1: alan end --- --- --- --- I updated the bug report too. One comment, I was using, apparently, kernel 3.7.0-rc4+ and it was quite difficult to reproduce the error. It happened only after I increased the CPU (and I/O) load doing a "make clean" in /usr/src/linux I do not know if this has any meaning, but better not to forget such details. Hope this helps, bye, -- piergiorgio -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
