On Fri, Dec 13, 2013 at 02:31:47PM +0000, Chris Clayton wrote: > Hi, Hi Chris, Thanks for the bug report! > Firstly, I'm not subscribed, so please cc me on any replies. > > I see the problem I describe below on 3.12.[0..5] and on the current 3.13 development kernel, including a kernel pulled > from Linus' tree just a few minutes ago. The diagnostics below and the config file attached are from 3.12.5. I can > easily repeat on 3.13 if that would be more useful. > > My Fujitsu Lifebook AH531 laptop has an expresscard slot and I bought an expresscard USB3.0 card. Has this expresscard worked on any older kernels? Or did you only try the new card on 3.12 and 3.13? > When I insert the card, two new usb devices are added to the output of lsusb: > > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > and the related new output from dmesg is: > > [ 3139.294483] pci 0000:02:00.0: [1b73:1100] type 00 class 0x0c0330 > [ 3139.294582] pci 0000:02:00.0: reg 0x10: [mem 0x00000000-0x0000ffff 64bit] > [ 3139.294656] pci 0000:02:00.0: reg 0x18: [mem 0x00000000-0x00000fff 64bit] > [ 3139.294729] pci 0000:02:00.0: reg 0x20: [mem 0x00000000-0x00000fff 64bit] > [ 3139.294955] pci 0000:02:00.0: supports D1 > [ 3139.294958] pci 0000:02:00.0: PME# supported from D0 D1 D3hot > [ 3139.295098] pci 0000:02:00.0: System wakeup disabled by ACPI > [ 3139.302185] pci 0000:02:00.0: BAR 0: assigned [mem 0xf0d00000-0xf0d0ffff 64bit] > [ 3139.302243] pci 0000:02:00.0: BAR 2: assigned [mem 0xf0d10000-0xf0d10fff 64bit] > [ 3139.302294] pci 0000:02:00.0: BAR 4: assigned [mem 0xf0d11000-0xf0d11fff 64bit] > [ 3139.302374] pci 0000:02:00.0: no hotplug settings from platform > [ 3139.302415] pcieport 0000:00:1c.3: driver skip pci_set_master, fix it! > [ 3139.302431] pci 0000:02:00.0: enabling device (0000 -> 0002) > [ 3139.315124] xhci_hcd 0000:02:00.0: xHCI Host Controller > [ 3139.315139] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3 > [ 3139.316242] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 > [ 3139.316250] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > [ 3139.316254] usb usb3: Product: xHCI Host Controller > [ 3139.316258] usb usb3: Manufacturer: Linux 3.12.5 xhci_hcd > [ 3139.316261] usb usb3: SerialNumber: 0000:02:00.0 > [ 3139.316548] hub 3-0:1.0: USB hub found > [ 3139.316738] hub 3-0:1.0: 4 ports detected > [ 3139.317301] xhci_hcd 0000:02:00.0: xHCI Host Controller > [ 3139.317309] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 4 > [ 3139.317631] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003 > [ 3139.317637] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > [ 3139.317641] usb usb4: Product: xHCI Host Controller > [ 3139.317644] usb usb4: Manufacturer: Linux 3.12.5 xhci_hcd > [ 3139.317647] usb usb4: SerialNumber: 0000:02:00.0 > [ 3139.317896] hub 4-0:1.0: USB hub found > [ 3139.318049] hub 4-0:1.0: 4 ports detected [snip] > If I plug a USB2 device into the card, everything works fine. If however, I plug a USB3 HDD into the card, the drive > appears not to be recognised. Is this your only USB 3.0 device? It would be useful to know if this is a device-specific issue, so if you have any other USB 3.0 devices, please try them as well. > lsusb does not show the device at all and the only additions to the output from dmesg is > one or more instances of: > > [ 3704.319656] xhci_hcd 0000:02:00.0: no hotplug settings from platform Hmm, I think that message only appears when the PCI device is hot-plugged. It's odd that it would appear when you plug something into the USB 3.0 port. Are you sure you didn't bump the expresscard and cause a hot-remove? (Bumping the expresscard should have no impact on whether the USB 3.0 device is recognized or not.) > The HDD works fine if plugged into a USB2 port. > > Let me know If I can provide any additional diagnostics, test patches, etc. Can you turn on CONFIG_USB_DEBUG on 3.13 (if it's not already enabled), and also run these two commands as root: cd /sys/kernel/debug/dynamic_debug echo -n 'module xhci_hcd =p' > control That should enable xHCI driver debugging. Then hot-plug your expresscard, plug in your USB 3.0 device into the USB 3.0 port, and send me the resulting dmesg, starting from xHCI driver initialization. That will allow me to figure out whether the xHCI driver is receiving a port status change event for the USB 3.0 device hot-plug. Sarah Sharp -- 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
