Re: [PATCH -v3 0/14] PCI: allocate pci bus num range for unassigned bridge busn

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jan 31, 2012 at 3:30 PM, Bjorn Helgaas <bhelgaas@xxxxxxxxxx> 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-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux