Bug 7575
| Summary: | Bus #03 (-#06) is hidden behind transparent bridge #01 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Khashayar Naderehvandi (khashayar.lists) |
| Component: | PCI | Assignee: | Bernhard Kaindl (bk) |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | bunk, greg |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.19-rc6 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
dmesg output
lspci output lspci output lspci output cat /proc/interrupts dmidecode output |
||
|
Description
Khashayar Naderehvandi
2006-11-23 04:35:33 UTC
Created attachment 9602 [details]
dmesg output
Created attachment 9604 [details]
lspci output
Created attachment 9605 [details]
lspci output
Created attachment 9606 [details]
lspci output
Created attachment 9607 [details]
cat /proc/interrupts
Created attachment 9608 [details]
dmidecode output
I thought this one might be good too; the output of the dmidecode utility.
Woops, I seem to have attached lspci output three times. I have a somewhat flaky connection right now that confuses me. Sorry about that. The attachments are identical... I'll tag two of them obsolete.. *** Bug 7573 has been marked as a duplicate of this bug. *** For Greg and others: This the same text as I used in bug 7831, so you do not have to read it again. Many thanks for the report, I reviewed it and have this result: The message Bus #03 (-#06) is hidden behind transparent bridge #01 (-#03) indicates that some PCI busses may 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. With your laptop, there would only be an issue if you connect an external PCI enclosure which itself has further internal PCI busses thru your cardbus slot to your laptop, but that case is also adressed by yenta-socket in current kernels. 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. Is this just a warning which I left in to be sure that the reason for it is properly dealt with, but we removed it from the normal user's sight now because we found * that the PCI misconfiguration which is being indicated in this message only seems to be an issue with CardBus. * that the CardBus fixup code which we have in place since 2.6.18 with appears to be sufficient. Thus, I submitted a patch which was merged mainline with 2.6.22.6 and 2.6.23 that turns it into a message which is only enabled when debugging PCI, so in practical users terms, the warning is gone. *** This bug has been marked as a duplicate of bug 7531 *** |