On Tue, Jan 3, 2017 at 2:28 AM, Oliver Neukum <oneukum@xxxxxxxx> wrote: > On Mon, 2017-01-02 at 14:45 -0700, Chris Murphy wrote: >> I see these lines in the problem case, which don't occur in the >> working case. >> >> [ 0.561046] pci_bus 0000:37: busn_res: [bus 37-ff] end is updated >> to 37 >> [ 0.561047] pci_bus 0000:37: busn_res: can not insert [bus 37] >> under domain [bus 00-ff] (conflicts with (null) [bus 00-fe]) >> >> [ 0.579446] pci 0000:37:00.0: can't claim BAR 0 [mem >> 0xb0000000-0xb000ffff]: address conflict with PCI Bus 0000:00 [mem >> 0x40000000-0xdfffffff window] >> >> [ 0.602277] pci 0000:37:00.0: can't derive routing for PCI INT A >> [ 0.602280] pci 0000:37:00.0: PCI INT A: not connected >> [ 0.612304] pci 0000:37:00.0: xHCI HW not ready after 5 sec (HC >> bug?) status = 0xffffffff > > Have you tried "pci=realloc"? No effect. Attached that dmesg to the bug report anyway though. -- Chris Murphy -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
