Messages in this thread | | | Date | Tue, 31 Jan 2012 16:27:06 -0800 | Subject | Re: [PATCH -v3 0/14] PCI: allocate pci bus num range for unassigned bridge busn | From | Yinghai Lu <> |
| |
On Tue, Jan 31, 2012 at 3:30 PM, Bjorn Helgaas <bhelgaas@google.com> wrote: > Thanks. I tried this, and it blew up as soon as I did a rescan. More > complete console log attached. > > # echo 1 > /sys/bus/pci/rescan > [ 140.237870] pci_bus 0000:00: scanning bus pass 0 > [ 140.242551] pci 0000:00:01.0: scanning [bus 01-01] behind bridge, pass 0 > [ 140.249249] pci 0000:00:01.0: check if busn 01-01 is in busn_res: [bus 00-7e] > [ 140.256377] pci 0000:00:01.0: bus configuration invalid, reconfiguring > [ 140.262912] pci 0000:00:01.1: scanning [bus 02-02] behind bridge, pass 0 > [ 140.269593] pci 0000:00:01.1: check if busn 02-02 is in busn_res: [bus 00-7e] > [ 140.276721] pci 0000:00:01.1: bus configuration invalid, reconfiguring
did not try this test case.
will check that .
Thanks
Yinghai -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |