Distribution: Debian 4.0 r0 Hardware Environment: notebook Samsung X11 C001 Problem Description: kernel reports PCI: Bus #0a (-#0d) is hidden behind transparent bridge #09 (-#09) (try 'pci=assign-busses') Please report the result to linux-kernel to fix this permanently
Created attachment 11504 [details] dmesg
Created attachment 11505 [details] dmesg with "pci=assign-busses"
Created attachment 11506 [details] lspci -v with "pci=assign-busses"
Hi all, I have this as well with an Acer TravelMate 4002WLMi. Don't get me wrong, everything seems to work just fine no matter if I use assign-busses or not. Regards Sebastian
Created attachment 11546 [details] dmesg.out On an Acer TravelMate 4002WLMi without pci=assign-busses
Created attachment 11547 [details] dmesg-assign-busses.out On an Acer TravelMate 4002WLMi with pci=assign-busses
Created attachment 11548 [details] lspci.out On an Acer TravelMate 4002WLMi without pci=assign-busses
Created attachment 11549 [details] lspci-assign-busses.out On an Acer TravelMate 4002WLMi with pci=assign-busses
I have a compal EL80 with the same issues: PCI: Transparent bridge - 0000:00:1e.0 PCI: Bus #07 (-#0a) is hidden behind transparent bridge #06 (-#07) (try 'pci=assign-busses') Please report the result to linux-kernel to fix this permanently Unless I use the assign busses the ENE 712/4 flash card reader will not work
Created attachment 11580 [details] dmesg with no assign
Created attachment 11581 [details] dmesg with assign
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 ***