Distribution: Gentoo Hardware Environment: Acer Travelmate 4002WLMI Problem Description: PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) Dmesg told me to report a bug report, so I did.
Created attachment 10518 [details] Dmesg without pci=assign-busses
Created attachment 10519 [details] dmesg with pci=assign-busses
Created attachment 10520 [details] lspci -v (and pci=assign-busses)
For Greg and others: This is a similiar text as I used in bug 8591, (only a bit improved) so you do not have to read it again. Many thanks for the report, I reviewed it and have this result: The message PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) indicates that a PCI busses are not reachable by your system, but it is very likely that if these bus is CardBus slots, then yenta-socket fixes this in current kernels, and lets you see your cardbus cards, so when they are, there is no issue at all and you'll see your CardBus cards in lspci and they should be picked up by the drivers which are loaded also. Unless you have PCI hardware (such as CardBus cards, not old PCMCIA cards) connected to your machine which is not shown by lspci after loading all neccessary drivers (eg. yenta_socket), we can close this bug: I'd then go forward and simply propose to either delete this warning check or to change it it a PCI-internal warning message and refine it a bit (so that it only is triggered in cases which are not addressed by yenta-socket) Not that if a secific driver is not working, then this is not in relation to this bug report, this bug report is only about PCI devices which may potentially not show up in lspci and for which the driver also will never see. Unless the PCI device is not shown in PCI, open a new bug if you have an issue with a driver. Again many thanks for the report and if I hear nothing new regarding this bug report, I'll close it when the 'bus hidden behind bridge' message is fixed.
Continuing from the last comment on this bug, which has all other relevant information I'm adding the following closing comment: The message is has been disabled in the latest upstream kernel release (2.6.22 stable series as well as 2.6.23), it's now a debug message which is not shown when not debugging.
*** Bug 8591 has been marked as a duplicate of this bug. ***
*** Bug 7664 has been marked as a duplicate of this bug. ***