> The non-working dmesg is very odd, and I think it's a PCI hot plug or > ACPI issue. Around 1 second in, the Thunderbolt dock is found, but later > it is hot-removed, and the PCI drivers are not notified of removal. > Then the dock is hot-plugged again, and the PCI core attempts to > initialized the drivers again, which fails. Around 1 sec in, the dock was not attached yet. > >> [ 1.009781] ACPI: ACPI Dock Station Driver: 1 docks/bays found >> [ 1.009841] HEST: Table not found. >> [ 1.009898] PCI: Using host bridge windows from ACPI; if necessary, use > "pci=nocrs" and report a bug I believe this message just means that there were acpi calls found that suggest there is 1 bay port. I am certain the dock was not connected at that time. > The xHCI driver eventually loads for PCI device 0000:04:00.0: > >> [ 3.088620] xhci_hcd 0000:04:00.0: PCI INT A -> GSI 18 (level, low) > -> IRQ 18 >> [ 3.088727] xhci_hcd 0000:04:00.0: setting latency timer to 64 >> [ 3.088731] xhci_hcd 0000:04:00.0: xHCI Host Controller >> [ 3.088812] xhci_hcd 0000:04:00.0: new USB bus registered, assigned bus > number 3 > This is the NEC hub inside the laptop, the one in the docking station is at 1b:00.0 > Then your dock gets re-enumerated *again* without any sort of PCI > disconnect for the existing drivers: > >> [ 26.714909] ACPI: \_SB_.DOCK - docking >> [ 26.717134] pci 0000:08:00.0: [8086:151b] type 1 class 0x000604 >> [ 26.717227] pci 0000:08:00.0: supports D1 D2 This is when the dock was actually attached I believe. About 25 sec after boot sounds about right. [ 26.739334] pci 0000:1b:00.0: [1033:0194] type 0 class 0x000c03 [ 26.739405] pci 0000:1b:00.0: reg 10: [mem 0x00000000-0x00001fff 64bit] [ 26.739706] pci 0000:1b:00.0: PME# supported from D0 D3hot D3cold [ 26.739717] pci 0000:1b:00.0: PME# disabled And this is the first mention of the usb host in the dock >> [ 26.914976] xhci_hcd 0000:1b:00.0: PCI INT A -> GSI 16 (level, low) > -> IRQ 16 >> [ 26.916313] xhci_hcd 0000:1b:00.0: controller already in use >> [ 26.916351] xhci_hcd 0000:1b:00.0: PCI INT A disabled >> [ 26.917766] xhci_hcd 0000:1b:00.0: init 0000:1b:00.0 fail, -16 >> [ 26.919149] xhci_hcd: probe of 0000:1b:00.0 failed with error -16 Is it possible that because there are 2 identical hubs the driver gets confused? -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
