On Wed, Oct 16, 2013 at 08:49:34AM -0700, Sarah Sharp wrote: > On Fri, Oct 04, 2013 at 11:39:47AM -0500, Drew Von Spreecken wrote: > > Sarah, I've enabled debugging for the module if it helps... Log attached. > > Hi Drew, > > > On 09/30/2013 06:19 PM, Sarah Sharp wrote: > > >Hi Drew! > > > > > >I'm the xHCI driver maintainer, and it helps to Cc me on issues with USB > > >devices under xHCI hosts. > > > > > >On Sun, Sep 29, 2013 at 11:14:47AM -0500, Drew Von Spreecken wrote: > > >>I have an Elan touchscreen that is causing USB resets and errors at > > >>boot and intermittently during use. The touchscreen works as > > >>expected but messages are still being logged to kern.log. > > >> > > >>It appears to get detected correctly: > > >> > > >>Bus 001 Device 002: ID 8087:8000 Intel Corp. > > >>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > >>Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > >>Bus 002 Device 013: ID 04f3:0089 Elan Microelectronics Corp. > > >>Bus 002 Device 004: ID 2232:1049 > > >>Bus 002 Device 003: ID 8087:07dc Intel Corp. > > >>Bus 002 Device 017: ID 18d1:4ee2 Google Inc. Nexus 4 (debug) > > >>Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > >> > > >>The recurring output of dmesg: > > >>[ 523.082262] usb 2-7: new full-speed USB device number 9 using xhci_hcd > > >>[ 525.186961] usb 2-7: unable to read config index 0 descriptor/start: -71 > > >>[ 525.186972] usb 2-7: can't read configurations, error -71 > > These errors look interesting: > > > Oct 3 21:37:46 8bit kernel: [ 3.861123] usb 1-7: unable to read config index 0 descriptor/start: -71 > > Oct 3 21:37:46 8bit kernel: [ 3.861129] usb 1-7: can't read configurations, error -71 > > Oct 3 21:37:46 8bit kernel: [ 4.026929] usb 1-7: new full-speed USB device number 5 using xhci_hcd > > Oct 3 21:37:46 8bit kernel: [ 6.060326] usb 1-7: unable to read config index 0 descriptor/start: -71 > > Oct 3 21:37:46 8bit kernel: [ 6.060331] usb 1-7: can't read configurations, error -71 > > Oct 3 21:37:46 8bit kernel: [ 6.225707] usb 1-7: new full-speed USB device number 6 using xhci_hcd > > Oct 3 21:37:46 8bit kernel: [ 8.259088] usb 1-7: unable to read config index 0 descriptor/start: -71 > > Oct 3 21:37:46 8bit kernel: [ 8.259092] usb 1-7: can't read configurations, error -71 > > Oct 3 21:37:46 8bit kernel: [ 8.424415] usb 1-7: new full-speed USB device number 7 using xhci_hcd > > Oct 3 21:37:46 8bit kernel: [ 8.586659] bio: create slab <bio-1> at 1 > > Oct 3 21:37:46 8bit kernel: [ 10.457602] usb 1-7: unable to read config index 0 descriptor/start: -71 > > Oct 3 21:37:46 8bit kernel: [ 10.457607] usb 1-7: can't read configurations, error -71 > > Oct 3 21:37:46 8bit kernel: [ 10.457625] hub 1-0:1.0: unable to enumerate USB device on port 7 > > The device isn't responding to the request for the device descriptors. > It may be that it needs to use the "Windows" enumeration scheme. Can > you test the following patch and see if it helps? > > http://marc.info/?l=linux-usb&m=138119329715367&w=2 > > At this point, I'm not even sure if the usb device 1-7 is the Elan > touchscreen. It doesn't look like it from the lsusb output you provided > (xHCI is on bus 2 and 3 in that output), but the bus numbers may have > changed after you rebooted. But try the patch anyway, and see if it > helps. Digging up a really old thread here. But I can duplicate this on a new laptop that I just got myself. No, it's not broken. Yes, it works fine with windows (until I deleted windows from the hard disk). It works fine with the BIOS so that's proof the hardware is working. And it's a pain. Sometimes it works and connects, most of the time it does not and just fills up my logs with the exact same error messages as above (same 1-7 device number as well.) Dan's patch went into 3.14-rc1, and I'm testing 3.15-rc7+ right now (i.e. Linus's tree) and still have this issue. Any ideas of what I can do? I guess a usbmon dump is in order, right? thanks, greg k-h -- 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
