Re: MUSB regression in linux next at least for pandboard
Hi, On 02/07/2013 04:10 PM, Grazvydas Ignotas wrote: On Thu, Feb 7, 2013 at 11:16 AM, Roger Quadros rog...@ti.com wrote: snip It seems the beagleboard problem is related to OMAP silicon errata [1]. Apparently, remote wakeup as well as host issued wakeup break omap-ehci and have nothing to do with the hub or it's driver. I'll work on this issue after I'm done with device tree migration. Looking forward to this, mainline has been suffering from this since almost forever.. Unfortunately, there is another errata [2] that makes it impossible to support suspend/resume on the beagleboard. cheers, -roger [2] Advisory 3.1.1.195 HSUSB Interoperability Issue With SMSC USB3320 PHY http://www.ti.com/general/docs/lit/getliterature.tsp?literatureNumber=sprz278ffileType=pdf -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MUSB regression in linux next at least for pandboard
On 02/06/2013 05:43 PM, Alan Stern wrote:
On Wed, 6 Feb 2013, Felipe Balbi wrote:
I can't reproduce the problem on Panda, but I can on Beagle with a slightly
different behaviour.
1) connecting/disconnecting device directly to the beagleboard's USB port
works fine.
2) If I connect a USB Hub to the port and connect a device to it after the
hub has
autosuspended, the device is never detected.
doing lsusb after that triggers the detection and produces a lot of
transaction errors.
Beagle log is below, before and after 'lsusb'
I suppose this doesn't affect Panda because it has a hub connected
immediately below the
root hub that never suspends (as ethernet is hardwired to it).
Roger, try changing hub's autosuspend delay to something greater than
30ms and see if it helps. There was a discussion lately about that.
There also were some patches to address this problem recently merged by
Greg KH (they are in Linus's current git, added after 3.8-rc6 was
released):
da0aa7169b97d90f4af39a9dc84d58bbe19d7e78 USB: add
usb_hcd_{start,end}_port_resume
f292e7f9fb0e4bec68bbd83443407d6bb7922d36 USB: EHCI: notify usbcore about port
resumes
ee74290b7853db9d5fd64db70e5c175241c59fba USB: EHCI: fix timer bug affecting
port resume
Alan, thanks for the hints.
It seems the beagleboard problem is related to OMAP silicon errata [1].
Apparently, remote wakeup as well as host issued wakeup break omap-ehci and have
nothing to do with the hub or it's driver.
I'll work on this issue after I'm done with device tree migration.
cheers,
-roger
[1] - Advisory 3.1.1.157 EHCI Controller- Issue in Suspend Resume Protocol
http://www.ti.com/general/docs/lit/getliterature.tsp?literatureNumber=sprz278ffileType=pdf
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MUSB regression in linux next at least for pandboard
On Thu, Feb 7, 2013 at 11:16 AM, Roger Quadros rog...@ti.com wrote: snip It seems the beagleboard problem is related to OMAP silicon errata [1]. Apparently, remote wakeup as well as host issued wakeup break omap-ehci and have nothing to do with the hub or it's driver. I'll work on this issue after I'm done with device tree migration. Looking forward to this, mainline has been suffering from this since almost forever.. -- GraÅžvydas -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MUSB regression in linux next at least for pandboard
On Wed, 6 Feb 2013, Alan Stern wrote: Is this issue fixed ? Actually we too are getting very similar issue with samsung exynos5250 hardware. With latest 'usb-next' kernel and supporting arch patches, when i use following test scenerio: Connect a USB 2.0 external hub to USB 2.0 port, and connect mice or keyboard enumeration and functionality is fine but once disconnecting the HID we get to see the error log: hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 When i tried to enable CONFIG_USB_DEBUG, get the following log: looks like it's not OMAP-specific. Alan any tips ? It could be a problem with the hub the keyboard is plugged into. Or something going on with the hub driver. I'll try doing the same thing on my system. I tried it. This is on an Intel system, not OMAP or anything like that. The result was as expected; there were a few can't reset device error messages but they stopped after a few hundred ms. If they persist for several minutes then something else is wrong. On the other hand, we could change the priority of those log messages. They don't have to be errors or warnings. Alan Stern -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MUSB regression in linux next at least for pandboard
Hi Tony, On Fri, Oct 5, 2012 at 9:57 PM, Tony Lindgren t...@atomide.com wrote: * Tony Lindgren t...@atomide.com [121004 18:41]: Also on the EHCI port, I've seen issues where unplugging the cable hangs kernel with an infinite loop. But that happens only occasionally, sorry does not seem to happen right now so no output to paste here. Or maybe this issue has already been fixed? Looks like the system eventually recovers from the EHCI issue after about fivew minutes or so of spamming the logs. It seems the ehci-omap errors are: [62934.201538] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 31 [62934.201660] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62934.201873] ehci-omap ehci-omap.0: reused qh ea5632c0 schedule More data below. Is this issue fixed ? Actually we too are getting very similar issue with samsung exynos5250 hardware. With latest 'usb-next' kernel and supporting arch patches, when i use following test scenerio: Connect a USB 2.0 external hub to USB 2.0 port, and connect mice or keyboard enumeration and functionality is fine but once disconnecting the HID we get to see the error log: hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 When i tried to enable CONFIG_USB_DEBUG, get the following log: hub 1-1:1.0: state 7 ports 7 chg evt 0008 hub 1-1:1.0: port 3, status 0301, change 0001, 1.5 Mb/s hub 1-1:1.0: debounce: port 3: total 100ms stable 100ms status 0x301 usb 1-1.3: new low-speed USB device number 5 using s5p-ehci usb 1-1.3: skipped 1 descriptor after interface usb 1-1.3: default language 0x0409 usb 1-1.3: udev 5, busnum 1, minor = 4 usb 1-1.3: New USB device found, idVendor=04b3, idProduct=3025 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3: Product: USB NetVista Full Width Keyboard usb 1-1.3: Manufacturer: CHICONY usb 1-1.3: usb_probe_device usb 1-1.3: configuration #1 chosen from 1 choice usb 1-1.3: adding 1-1.3:1.0 (config #1, interface 0) usbhid 1-1.3:1.0: usb_probe_interface usbhid 1-1.3:1.0: usb_probe_interface - got id input: CHICONY USB NetVista Full Width Keyboard as /devices/s5p-ehci/usb1/1-1/1-1.3/1-1.3:1.0/input/input1 usb 1-1.3: link qh8-0e01/c193f140 start 2 [1/2 us] hid-generic 0003:04B3:3025.0002: input: USB HID v1.10 Keyboard [CHICONY USB NetVista Full Width Keyboard] on usb-s5p-ehci-1.3/input0 hub 1-1:1.0: state 7 ports 7 chg evt 0008 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 1 usb 1-1.3: unlink qh8-0e01/c193f140 start 2 [1/2 us] s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 1 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 2 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 3 hub 1-1:1.0: state 7 ports 7 chg evt 0008 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 4 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 5 hub 1-1:1.0: port 3, status 0100, change 0001, 12 Mb/s s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 6 usb 1-1.3: USB disconnect, device number 5 usb 1-1.3: unregistering device usb 1-1.3: unregistering interface 1-1.3:1.0 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 7 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 8 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 9 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 10 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 11 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 12 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 13 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 14 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 15 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 16 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 17 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 18 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 19 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 20 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 21 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 22 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 23 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 24 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 25 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 26 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 27 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 28 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 29 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 30 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 31 s5p-ehci s5p-ehci: devpath 1.3 ep0out 3strikes usb 1-1: clear tt buffer port 3, a5 ep0 t00080248 hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 Similar log as you get on ehci-omap ;-) Sorry i might have missed some information to put here. Your help will be very much useful. Thanks in advance :-) ... [62927.200012] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 19 [62927.215606] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 25 [62927.220092] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 22 [62927.225738] ehci-omap ehci-omap.0:
Re: MUSB regression in linux next at least for pandboard
Hi, On Wed, Feb 06, 2013 at 05:27:52PM +0530, Vivek Gautam wrote: Hi Tony, On Fri, Oct 5, 2012 at 9:57 PM, Tony Lindgren t...@atomide.com wrote: * Tony Lindgren t...@atomide.com [121004 18:41]: Also on the EHCI port, I've seen issues where unplugging the cable hangs kernel with an infinite loop. But that happens only occasionally, sorry does not seem to happen right now so no output to paste here. Or maybe this issue has already been fixed? Looks like the system eventually recovers from the EHCI issue after about fivew minutes or so of spamming the logs. It seems the ehci-omap errors are: [62934.201538] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 31 [62934.201660] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62934.201873] ehci-omap ehci-omap.0: reused qh ea5632c0 schedule More data below. Is this issue fixed ? Actually we too are getting very similar issue with samsung exynos5250 hardware. With latest 'usb-next' kernel and supporting arch patches, when i use following test scenerio: Connect a USB 2.0 external hub to USB 2.0 port, and connect mice or keyboard enumeration and functionality is fine but once disconnecting the HID we get to see the error log: hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 When i tried to enable CONFIG_USB_DEBUG, get the following log: looks like it's not OMAP-specific. Alan any tips ? (keeping logs below) hub 1-1:1.0: state 7 ports 7 chg evt 0008 hub 1-1:1.0: port 3, status 0301, change 0001, 1.5 Mb/s hub 1-1:1.0: debounce: port 3: total 100ms stable 100ms status 0x301 usb 1-1.3: new low-speed USB device number 5 using s5p-ehci usb 1-1.3: skipped 1 descriptor after interface usb 1-1.3: default language 0x0409 usb 1-1.3: udev 5, busnum 1, minor = 4 usb 1-1.3: New USB device found, idVendor=04b3, idProduct=3025 usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 1-1.3: Product: USB NetVista Full Width Keyboard usb 1-1.3: Manufacturer: CHICONY usb 1-1.3: usb_probe_device usb 1-1.3: configuration #1 chosen from 1 choice usb 1-1.3: adding 1-1.3:1.0 (config #1, interface 0) usbhid 1-1.3:1.0: usb_probe_interface usbhid 1-1.3:1.0: usb_probe_interface - got id input: CHICONY USB NetVista Full Width Keyboard as /devices/s5p-ehci/usb1/1-1/1-1.3/1-1.3:1.0/input/input1 usb 1-1.3: link qh8-0e01/c193f140 start 2 [1/2 us] hid-generic 0003:04B3:3025.0002: input: USB HID v1.10 Keyboard [CHICONY USB NetVista Full Width Keyboard] on usb-s5p-ehci-1.3/input0 hub 1-1:1.0: state 7 ports 7 chg evt 0008 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 1 usb 1-1.3: unlink qh8-0e01/c193f140 start 2 [1/2 us] s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 1 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 2 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 3 hub 1-1:1.0: state 7 ports 7 chg evt 0008 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 4 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 5 hub 1-1:1.0: port 3, status 0100, change 0001, 12 Mb/s s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 6 usb 1-1.3: USB disconnect, device number 5 usb 1-1.3: unregistering device usb 1-1.3: unregistering interface 1-1.3:1.0 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 7 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 8 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 9 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 10 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 11 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 12 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 13 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 14 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 15 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 16 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 17 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 18 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 19 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 20 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 21 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 22 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 23 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 24 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 25 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 26 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 27 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 28 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 29 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 30 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 31 s5p-ehci s5p-ehci: devpath 1.3 ep0out 3strikes usb 1-1: clear tt buffer port 3, a5 ep0 t00080248 hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 Similar log as you get on ehci-omap ;-) Sorry i might have missed some information to put here. Your help will be very much useful. Thanks in advance :-) ...
Re: MUSB regression in linux next at least for pandboard
On 02/06/2013 03:51 PM, Felipe Balbi wrote: Hi, On Wed, Feb 06, 2013 at 05:27:52PM +0530, Vivek Gautam wrote: Hi Tony, On Fri, Oct 5, 2012 at 9:57 PM, Tony Lindgren t...@atomide.com wrote: * Tony Lindgren t...@atomide.com [121004 18:41]: Also on the EHCI port, I've seen issues where unplugging the cable hangs kernel with an infinite loop. But that happens only occasionally, sorry does not seem to happen right now so no output to paste here. Or maybe this issue has already been fixed? Looks like the system eventually recovers from the EHCI issue after about fivew minutes or so of spamming the logs. It seems the ehci-omap errors are: [62934.201538] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 31 [62934.201660] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62934.201873] ehci-omap ehci-omap.0: reused qh ea5632c0 schedule More data below. Is this issue fixed ? Actually we too are getting very similar issue with samsung exynos5250 hardware. With latest 'usb-next' kernel and supporting arch patches, when i use following test scenerio: Connect a USB 2.0 external hub to USB 2.0 port, and connect mice or keyboard enumeration and functionality is fine but once disconnecting the HID we get to see the error log: hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 When i tried to enable CONFIG_USB_DEBUG, get the following log: looks like it's not OMAP-specific. Alan any tips ? I can't reproduce the problem on Panda, but I can on Beagle with a slightly different behaviour. 1) connecting/disconnecting device directly to the beagleboard's USB port works fine. 2) If I connect a USB Hub to the port and connect a device to it after the hub has autosuspended, the device is never detected. doing lsusb after that triggers the detection and produces a lot of transaction errors. Beagle log is below, before and after 'lsusb' I suppose this doesn't affect Panda because it has a hub connected immediately below the root hub that never suspends (as ethernet is hardwired to it). So there must be some problem in the hub drivers. cheers, -roger root@beagleboard:~# [ 62.666595] usb usb1: usb wakeup-resume [ 62.670684] usb usb1: usb auto-resume [ 62.674591] ehci-omap ehci-omap.0: resume root hub [ 62.679687] hub 1-0:1.0: hub_resume [ 62.683471] ehci-omap ehci-omap.0: GetStatus port:2 status 001803 0 ACK POWER sig=j CSC CONNECT [ 62.692779] hub 1-0:1.0: port 2: status 0501 change 0001 [ 62.772460] hub 1-0:1.0: state 7 ports 3 chg 0004 evt [ 62.778533] hub 1-0:1.0: port 2, status 0501, change , 480 Mb/s [ 62.849182] ehci-omap ehci-omap.0: port 2 reset complete, port enabled [ 62.856109] ehci-omap ehci-omap.0: GetStatus port:2 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 62.929931] usb 1-2: new high-speed USB device number 4 using ehci-omap [ 62.998352] ehci-omap ehci-omap.0: port 2 reset complete, port enabled [ 63.005279] ehci-omap ehci-omap.0: GetStatus port:2 status 001005 0 ACK POWER sig=se0 PE CONNECT [ 63.107635] usb 1-2: udev 4, busnum 1, minor = 3 [ 63.112548] usb 1-2: New USB device found, idVendor=0409, idProduct=005a [ 63.119720] usb 1-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 63.128936] usb 1-2: usb_probe_device [ 63.132812] usb 1-2: configuration #1 chosen from 1 choice [ 63.139160] usb 1-2: adding 1-2:1.0 (config #1, interface 0) [ 63.145629] hub 1-2:1.0: usb_probe_interface [ 63.150146] hub 1-2:1.0: usb_probe_interface - got id [ 63.155578] hub 1-2:1.0: USB hub found [ 63.200195] hub 1-2:1.0: 4 ports detected [ 63.204467] hub 1-2:1.0: standalone hub [ 63.208679] hub 1-2:1.0: ganged power switching [ 63.213470] hub 1-2:1.0: global over-current protection [ 63.219055] hub 1-2:1.0: Single TT [ 63.222747] hub 1-2:1.0: TT requires at most 16 FS bit times (1332 ns) [ 63.229644] hub 1-2:1.0: Port indicators are supported [ 63.235137] hub 1-2:1.0: power on to power good time: 0ms [ 63.242584] hub 1-2:1.0: local power source is good [ 63.247955] hub 1-2:1.0: no over-current condition exists [ 63.254852] hub 1-2:1.0: enabling power on all ports [ 63.357482] usb 1-2: link qh256-0001/cf68f6c0 start 1 [1/0 us] [ 63.364044] hub 1-2:1.0: state 7 ports 4 chg evt [ 63.370086] hub 1-2:1.0: hub_suspend [ 63.374023] usb 1-2: unlink qh256-0001/cf68f6c0 start 1 [1/0 us] [ 63.384948] usb 1-2: usb auto-suspend, wakeup 1 [ 63.410217] hub 1-0:1.0: hub_suspend [ 63.414062] usb usb1: bus auto-suspend, wakeup 1 [ 63.419036] ehci-omap ehci-omap.0: suspend root hub root@beagleboard:~# root@beagleboard:~# lsusb [ 80.925262] usb usb1: usb auto-resume [ 80.929351] ehci-omap ehci-omap.0: resume root hub [ 80.934539] hub 1-0:1.0: hub_resume [ 80.938323] hub 1-0:1.0: port 2: status 0507 change [ 80.945373] hub 1-0:1.0: state 7 ports 3 chg evt [ 80.952026] hub 1-0:1.0: hub_suspend [ 80.956024] usb
Re: MUSB regression in linux next at least for pandboard
Hi, On Wed, Feb 06, 2013 at 05:03:36PM +0200, Roger Quadros wrote: On 02/06/2013 03:51 PM, Felipe Balbi wrote: Hi, On Wed, Feb 06, 2013 at 05:27:52PM +0530, Vivek Gautam wrote: Hi Tony, On Fri, Oct 5, 2012 at 9:57 PM, Tony Lindgren t...@atomide.com wrote: * Tony Lindgren t...@atomide.com [121004 18:41]: Also on the EHCI port, I've seen issues where unplugging the cable hangs kernel with an infinite loop. But that happens only occasionally, sorry does not seem to happen right now so no output to paste here. Or maybe this issue has already been fixed? Looks like the system eventually recovers from the EHCI issue after about fivew minutes or so of spamming the logs. It seems the ehci-omap errors are: [62934.201538] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 31 [62934.201660] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62934.201873] ehci-omap ehci-omap.0: reused qh ea5632c0 schedule More data below. Is this issue fixed ? Actually we too are getting very similar issue with samsung exynos5250 hardware. With latest 'usb-next' kernel and supporting arch patches, when i use following test scenerio: Connect a USB 2.0 external hub to USB 2.0 port, and connect mice or keyboard enumeration and functionality is fine but once disconnecting the HID we get to see the error log: hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 When i tried to enable CONFIG_USB_DEBUG, get the following log: looks like it's not OMAP-specific. Alan any tips ? I can't reproduce the problem on Panda, but I can on Beagle with a slightly different behaviour. 1) connecting/disconnecting device directly to the beagleboard's USB port works fine. 2) If I connect a USB Hub to the port and connect a device to it after the hub has autosuspended, the device is never detected. doing lsusb after that triggers the detection and produces a lot of transaction errors. Beagle log is below, before and after 'lsusb' I suppose this doesn't affect Panda because it has a hub connected immediately below the root hub that never suspends (as ethernet is hardwired to it). Roger, try changing hub's autosuspend delay to something greater than 30ms and see if it helps. There was a discussion lately about that. -- balbi signature.asc Description: Digital signature
Re: MUSB regression in linux next at least for pandboard
On Wed, 6 Feb 2013, Felipe Balbi wrote:
I can't reproduce the problem on Panda, but I can on Beagle with a slightly
different behaviour.
1) connecting/disconnecting device directly to the beagleboard's USB port
works fine.
2) If I connect a USB Hub to the port and connect a device to it after the
hub has
autosuspended, the device is never detected.
doing lsusb after that triggers the detection and produces a lot of
transaction errors.
Beagle log is below, before and after 'lsusb'
I suppose this doesn't affect Panda because it has a hub connected
immediately below the
root hub that never suspends (as ethernet is hardwired to it).
Roger, try changing hub's autosuspend delay to something greater than
30ms and see if it helps. There was a discussion lately about that.
There also were some patches to address this problem recently merged by
Greg KH (they are in Linus's current git, added after 3.8-rc6 was
released):
da0aa7169b97d90f4af39a9dc84d58bbe19d7e78 USB: add
usb_hcd_{start,end}_port_resume
f292e7f9fb0e4bec68bbd83443407d6bb7922d36 USB: EHCI: notify usbcore about port
resumes
ee74290b7853db9d5fd64db70e5c175241c59fba USB: EHCI: fix timer bug affecting
port resume
Alan Stern
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MUSB regression in linux next at least for pandboard
On Wed, 6 Feb 2013, Felipe Balbi wrote: Hi, On Wed, Feb 06, 2013 at 05:27:52PM +0530, Vivek Gautam wrote: Hi Tony, On Fri, Oct 5, 2012 at 9:57 PM, Tony Lindgren t...@atomide.com wrote: * Tony Lindgren t...@atomide.com [121004 18:41]: Also on the EHCI port, I've seen issues where unplugging the cable hangs kernel with an infinite loop. But that happens only occasionally, sorry does not seem to happen right now so no output to paste here. Or maybe this issue has already been fixed? Looks like the system eventually recovers from the EHCI issue after about fivew minutes or so of spamming the logs. It seems the ehci-omap errors are: [62934.201538] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 31 [62934.201660] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62934.201873] ehci-omap ehci-omap.0: reused qh ea5632c0 schedule More data below. Is this issue fixed ? Actually we too are getting very similar issue with samsung exynos5250 hardware. With latest 'usb-next' kernel and supporting arch patches, when i use following test scenerio: Connect a USB 2.0 external hub to USB 2.0 port, and connect mice or keyboard enumeration and functionality is fine but once disconnecting the HID we get to see the error log: hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 When i tried to enable CONFIG_USB_DEBUG, get the following log: looks like it's not OMAP-specific. Alan any tips ? It could be a problem with the hub the keyboard is plugged into. Or something going on with the hub driver. I'll try doing the same thing on my system. (keeping logs below) ... s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 1 usb 1-1.3: unlink qh8-0e01/c193f140 start 2 [1/2 us] s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 1 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 2 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 3 hub 1-1:1.0: state 7 ports 7 chg evt 0008 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 4 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 5 hub 1-1:1.0: port 3, status 0100, change 0001, 12 Mb/s s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 6 usb 1-1.3: USB disconnect, device number 5 usb 1-1.3: unregistering device usb 1-1.3: unregistering interface 1-1.3:1.0 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 7 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 8 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 9 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 10 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 11 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 12 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 13 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 14 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 15 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 16 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 17 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 18 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 19 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 20 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 21 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 22 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 23 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 24 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 25 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 26 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 27 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 28 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 29 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 30 s5p-ehci s5p-ehci: detected XactErr len 0/8 retry 31 s5p-ehci s5p-ehci: devpath 1.3 ep0out 3strikes usb 1-1: clear tt buffer port 3, a5 ep0 t00080248 hid-generic 0003:04B3:3025.0002: can't reset device, s5p-ehci-1.3/input0, status -71 Note that most of these are debug messages, so they wouldn't normally appear. (BTW: timestamps would be nice -- CONFIG_PRINTK_TIME.) Similar log as you get on ehci-omap ;-) Sorry i might have missed some information to put here. Your help will be very much useful. Thanks in advance :-) ... [62927.200012] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 19 [62927.215606] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 25 [62927.220092] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 22 [62927.225738] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes A certain amount of this is normal when an HID device is unplugged. It should stop after 250 ms, however, when the hub notifies the host that a cable has been unplugged. (Unless the hub driver is busy doing something else at the time...) ... After waiting for several minutes, it stops, and dmesg shows: # dmesg | grep -i omap This grep will drop the important information. Alan Stern -- To unsubscribe from
Re: MUSB regression in linux next at least for pandboard
Hi, On Friday 05 October 2012 07:09 AM, Tony Lindgren wrote: * Felipe Balbi ba...@ti.com [121004 11:04]: Hi, On Thu, Oct 04, 2012 at 10:31:08AM -0700, Tony Lindgren wrote: Hi Felipe Kishon, Looks like musb is broken at least on pandaboard es in current linux next while it works with v3.6: [1.933074] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) [1.939422] unable to find transceiver of type USB2 PHYrouping on. Total pages: 251648 [1.945190] HS USB OTG: no transceiver configured [1.950134] musb-hdrc musb-hdrc.0: musb_init_controller failed with status -19 [1.958160] couldn't find an available UDC I do have CONFIG_OMAP_USB2 set. Note that we won't be able to flip omap4 over to be device tree only probably until v3.9 because of the bindings we're still missing from usability point of view. So this regression should be fixed. I see. Kishon, can you cook a patch adding platform_data until we actually move to DT-only for OMAP4 ? Sure. Thanks Kishon -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: MUSB regression in linux next at least for pandboard
* Tony Lindgren t...@atomide.com [121004 18:41]: Also on the EHCI port, I've seen issues where unplugging the cable hangs kernel with an infinite loop. But that happens only occasionally, sorry does not seem to happen right now so no output to paste here. Or maybe this issue has already been fixed? Looks like the system eventually recovers from the EHCI issue after about fivew minutes or so of spamming the logs. It seems the ehci-omap errors are: [62934.201538] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 31 [62934.201660] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62934.201873] ehci-omap ehci-omap.0: reused qh ea5632c0 schedule More data below. Regards, Tony ... [62927.200012] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 19 [62927.215606] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 25 [62927.220092] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 22 [62927.225738] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62927.232238] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 17 [62927.236633] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 18 [62927.241119] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 3 [62927.251098] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 18 [62927.258605] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 12 [62927.264343] usb 1-1.3.7.5: link qh8-0e01/ea5632c0 start 6 [1/2 us] [62927.274353] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 17 [62927.276092] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 24 [62927.280700] usb 1-1.3.7: clear tt 4 (0120) error -71 [62927.289245] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 2 [62927.292633] usb 1-1.3.7: clear tt buffer port 4, a18 ep0 t00080248 [62927.296356] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 26 [62927.302368] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 6 [62927.307098] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 24 [62927.308258] hid-generic 0003:047D:1020.000C: can't reset device, ehci-omap.0-1.3.7.4/input0, status -1 [62927.317230] usb 1-1.3.7: clear tt buffer port 5, a26 ep0 t00080248 [62927.322357] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 18 [62927.324981] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 5 [62927.330718] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 9 [62927.336364] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 20 [62927.348114] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 31 [62927.349090] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 5 [62927.356475] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 26 [62927.368469] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 2 [62927.372253] usb 1-1.3.7: clear tt buffer port 4, a18 ep0 t00080248 [62926.616607] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 29 [62926.622863] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 10 [62926.627746] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 29 [62926.628112] ehci-omap ehci-omap.0: devpath 1.3.7.4 ep0out 3strikes [62926.639404] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 14 [62926.643737] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 29 [62926.651123] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 15 [62926.655609] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 18 [62926.660125] usb 1-1.3.7: clear tt buffer port 4, a18 ep0 t00080248 [62926.667480] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 15 [62926.669982] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 1 [62926.680603] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 3 [62926.686126] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 14 [62926.693237] usb 1-1.3.7: clear tt buffer port 5, a26 ep0 t00080248 [62926.694091] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 4 [62926.706359] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 2 [62926.709350] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 7 [62926.712554] usb 1-1.3.7: clear tt 4 (0120) error -71 [62926.714599] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 16 [62926.720855] ehci-omap ehci-omap.0: devpath 1.3.7.5 ep0out 3strikes [62926.729248] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 2 [62926.732238] usb 1-1.3.7: clear tt buffer port 4, a18 ep0 t00080248 [62926.736358] ehci-omap ehci-omap.0: devpath 1.3.7 ep0out 3strikes [62926.742736] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 9 [62926.755615] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 27 [62926.756744] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 2 [62926.763610] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 19 [62926.769226] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 29 [62926.780609] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 2 [62926.782745] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 19 [62926.789978] ehci-omap ehci-omap.0: detected XactErr len 0/8 retry 3
Re: MUSB regression in linux next at least for pandboard
* Felipe Balbi ba...@ti.com [121004 11:04]: Hi, On Thu, Oct 04, 2012 at 10:31:08AM -0700, Tony Lindgren wrote: Hi Felipe Kishon, Looks like musb is broken at least on pandaboard es in current linux next while it works with v3.6: [1.933074] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host) [1.939422] unable to find transceiver of type USB2 PHYrouping on. Total pages: 251648 [1.945190] HS USB OTG: no transceiver configured [1.950134] musb-hdrc musb-hdrc.0: musb_init_controller failed with status -19 [1.958160] couldn't find an available UDC I do have CONFIG_OMAP_USB2 set. Note that we won't be able to flip omap4 over to be device tree only probably until v3.9 because of the bindings we're still missing from usability point of view. So this regression should be fixed. I see. Kishon, can you cook a patch adding platform_data until we actually move to DT-only for OMAP4 ? Also on the EHCI port, I've seen issues where unplugging the cable hangs kernel with an infinite loop. But that happens only occasionally, sorry does not seem to happen right now so no output to paste here. Or maybe this issue has already been fixed? Keshava, would you have time to look into this for this -rc cycle ? Also, can you guys also please do a patch to move plat/usb.h to include/linux/platform_data/usb-omap.h that only contains platform data? The init functions should be in local usb.h under arch/arm/*omap*/*. Then also please remove the cpu_is_omap usage from drivers/mfd/omap-usb-host.c if not done already. These are needed to make plat/cpu.h local to mach-omap* for the ARM common zImage support. Thanks, Tony -- To unsubscribe from this list: send the line unsubscribe linux-omap in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
