Bug 8480 - Bus #0a (-#0d) is hidden behind transparent bridge #09 (-#09)
Summary: Bus #0a (-#0d) is hidden behind transparent bridge #09 (-#09)
Status: RESOLVED DUPLICATE of bug 7531
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCI (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Bernhard Kaindl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-15 00:20 UTC by Stanislav Mayantsev
Modified: 2007-10-16 06:25 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.21.1
Subsystem:
Regression: ---
Bisected commit-id:


Attachments
dmesg (22.83 KB, text/plain)
2007-05-15 00:22 UTC, Stanislav Mayantsev
Details
dmesg with "pci=assign-busses" (22.39 KB, text/plain)
2007-05-15 00:24 UTC, Stanislav Mayantsev
Details
lspci -v with "pci=assign-busses" (9.97 KB, text/plain)
2007-05-15 00:29 UTC, Stanislav Mayantsev
Details
dmesg.out (14.00 KB, text/plain)
2007-05-20 02:44 UTC, Sebastian Kemper
Details
dmesg-assign-busses.out (13.86 KB, text/plain)
2007-05-20 02:45 UTC, Sebastian Kemper
Details
lspci.out (12.04 KB, text/plain)
2007-05-20 02:45 UTC, Sebastian Kemper
Details
lspci-assign-busses.out (12.04 KB, text/plain)
2007-05-20 02:46 UTC, Sebastian Kemper
Details
dmesg with no assign (26.43 KB, text/plain)
2007-05-23 20:33 UTC, Joe Ceklosky
Details
dmesg with assign (23.35 KB, text/plain)
2007-05-23 20:34 UTC, Joe Ceklosky
Details

Description Stanislav Mayantsev 2007-05-15 00:20:48 UTC
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
Comment 1 Stanislav Mayantsev 2007-05-15 00:22:10 UTC
Created attachment 11504 [details]
dmesg
Comment 2 Stanislav Mayantsev 2007-05-15 00:24:48 UTC
Created attachment 11505 [details]
dmesg with "pci=assign-busses"
Comment 3 Stanislav Mayantsev 2007-05-15 00:29:19 UTC
Created attachment 11506 [details]
lspci -v with "pci=assign-busses"
Comment 4 Sebastian Kemper 2007-05-20 02:42:14 UTC
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
Comment 5 Sebastian Kemper 2007-05-20 02:44:03 UTC
Created attachment 11546 [details]
dmesg.out

On an Acer TravelMate 4002WLMi without pci=assign-busses
Comment 6 Sebastian Kemper 2007-05-20 02:45:15 UTC
Created attachment 11547 [details]
dmesg-assign-busses.out

On an Acer TravelMate 4002WLMi with pci=assign-busses
Comment 7 Sebastian Kemper 2007-05-20 02:45:57 UTC
Created attachment 11548 [details]
lspci.out

On an Acer TravelMate 4002WLMi without pci=assign-busses
Comment 8 Sebastian Kemper 2007-05-20 02:46:21 UTC
Created attachment 11549 [details]
lspci-assign-busses.out

On an Acer TravelMate 4002WLMi with pci=assign-busses
Comment 9 Joe Ceklosky 2007-05-23 20:31:27 UTC
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
Comment 10 Joe Ceklosky 2007-05-23 20:33:32 UTC
Created attachment 11580 [details]
dmesg with no assign
Comment 11 Joe Ceklosky 2007-05-23 20:34:19 UTC
Created attachment 11581 [details]
dmesg with assign
Comment 12 Bernhard Kaindl 2007-10-16 06:25:34 UTC
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 ***

Note You need to log in before you can comment on or make changes to this bug.