Hi, Finally, I was able to test another USB3 key (Sandisk 64Gb instead of the previous Goodram 8Gb) : Bus 002 Device 002: ID 0781:5590 SanDisk Corp. ... and unloading xhci_pci / xhci_hcd while letting the USB3 key plugged then reloading xhci_pci / xhci_hcd is working fine. (Sorry, this is a test I should have done before) I send a email to Goodram to tell them the problem with their usb key in the warm boot case. Still searching for a magic xhci quirk parameter that could fake the "unplug" operation. On 09/04/2016 09:52 AM, kulamfm wrote: > Hi, > > Finally, I was able to test on v4.8-rc4 > > [ +0.018224] xhci_hcd 0000:00:14.0: xHCI Host Controller > [ +0.000016] xhci_hcd 0000:00:14.0: new USB bus registered, assigned > bus number 2 > [ +0.000091] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 > [ +0.000005] usb usb2: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ +0.000003] usb usb2: Product: xHCI Host Controller > [ +0.000002] usb usb2: Manufacturer: Linux 4.8.0-rc4--initrd+ xhci-hcd > [ +0.000002] usb usb2: SerialNumber: 0000:00:14.0 > [ +0.000399] hub 2-0:1.0: USB hub found > [ +0.000022] hub 2-0:1.0: 4 ports detected > [ +5.459877] xhci_hcd 0000:00:14.0: Timeout while waiting for setup > device command > [ +5.376072] xhci_hcd 0000:00:14.0: Timeout while waiting for setup > device command > [ +0.207956] usb 2-1: device not accepting address 2, error -62 > [ +5.936238] xhci_hcd 0000:00:14.0: Timeout while waiting for setup > device command > [ +5.376202] xhci_hcd 0000:00:14.0: Timeout while waiting for setup > device command > [ +0.207973] usb 2-1: device not accepting address 3, error -62 > [ +0.807489] usb 2-1: Device not responding to setup address. > [ +0.208012] usb 2-1: Device not responding to setup address. > [ +0.204544] usb 2-1: device not accepting address 4, error -71 > [ +0.807466] usb 2-1: Device not responding to setup address. > [ +0.208016] usb 2-1: Device not responding to setup address. > [ +0.204580] usb 2-1: device not accepting address 5, error -71 > [ +0.000137] usb usb2-port1: unable to enumerate USB device > [ +12.826671] xhci_hcd 0000:00:14.0: remove, state 4 > [ +0.000015] usb usb2: USB disconnect, device number 1 > [ +0.001399] xhci_hcd 0000:00:14.0: USB bus 2 deregistered > [ +0.000020] xhci_hcd 0000:00:14.0: remove, state 4 > [ +0.000013] usb usb1: USB disconnect, device number 1 > [ +0.000460] xhci_hcd 0000:00:14.0: USB bus 1 deregistered > > and sometimes : > > [ +6.984093] xhci_hcd 0000:00:14.0: xHCI Host Controller > [ +0.000014] xhci_hcd 0000:00:14.0: new USB bus registered, assigned > bus number 1 > [ +0.001113] xhci_hcd 0000:00:14.0: hcc params 0x20007181 hci version > 0x100 quirks 0x0000b930 > [ +0.000008] xhci_hcd 0000:00:14.0: cache line size of 64 is not supported > [ +0.000156] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 > [ +0.000004] usb usb1: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ +0.000002] usb usb1: Product: xHCI Host Controller > [ +0.000003] usb usb1: Manufacturer: Linux 4.8.0-rc4--initrd+ xhci-hcd > [ +0.000002] usb usb1: SerialNumber: 0000:00:14.0 > [ +0.000284] hub 1-0:1.0: USB hub found > [ +0.000025] hub 1-0:1.0: 4 ports detected > [ +0.014238] xhci_hcd 0000:00:14.0: xHCI Host Controller > [ +0.000014] xhci_hcd 0000:00:14.0: new USB bus registered, assigned > bus number 2 > [ +0.000068] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003 > [ +0.000003] usb usb2: New USB device strings: Mfr=3, Product=2, > SerialNumber=1 > [ +0.000003] usb usb2: Product: xHCI Host Controller > [ +0.000002] usb usb2: Manufacturer: Linux 4.8.0-rc4--initrd+ xhci-hcd > [ +0.000002] usb usb2: SerialNumber: 0000:00:14.0 > [ +0.000686] hub 2-0:1.0: USB hub found > [ +0.000025] hub 2-0:1.0: 4 ports detected > [ +0.330691] usb 2-1: Device not responding to setup address. > [ +0.207985] usb 2-1: Device not responding to setup address. > [ +0.204544] usb 2-1: device not accepting address 2, error -71 > [ +0.807514] usb 2-1: Device not responding to setup address. > [ +0.207984] usb 2-1: Device not responding to setup address. > [ +0.204578] usb 2-1: device not accepting address 3, error -71 > [ +0.807466] usb 2-1: Device not responding to setup address. > [ +0.207879] usb 2-1: Device not responding to setup address. > [ +0.204681] usb 2-1: device not accepting address 4, error -71 > [ +0.807442] usb 2-1: Device not responding to setup address. > [ +0.207965] usb 2-1: Device not responding to setup address. > [ +0.204654] usb 2-1: device not accepting address 5, error -71 > [ +0.000125] usb usb2-port1: unable to enumerate USB device > > > On 09/03/2016 11:36 PM, kulamfm wrote: >> Hi, >> >> Thanks for your idea but unfortunately no... it did not change anything. >> >> It seems to me that the problem is more "power related" (see my comment >> on the laptop booting correctly on cold boot but ignoring the USB3 key >> and going directly to Grub Menu when reboot) >> >> Is there any parameter of the kernel that can put down the power of USB3 >> completely when xhci is unloading and that way, fake a "deplug" of the >> USB3 key ? >> >> >> >> On 09/03/2016 09:13 PM, Greg KH wrote: >>> On Sat, Sep 03, 2016 at 06:48:27PM +0200, kulamfm wrote: >>>> Hi, >>>> >>>> I can boot on Debian-Live installed on a USB2 key. >>>> I can't boot on Debian-Live installed on a USB3 key unless I wait a bit >>>> and with the good timing, deplug and replug the USB3 key. >>>> I have no idea if it is a BIOS problem, a USB3 key problem, a USB3 >>>> controller problem or a pci/xhci Linux kernel problem or just a missing >>>> parameter for xhci ? >>> Try using the 'rootwait' boot parameter, that is what it is there for. >>> >>> hope this helps, >>> >>> 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
