Bug 8903 - PCI: Bus #06 (-#09) is hidden behind transparent bridge #05 (-#05) (try 'pci=assign-busses')
Summary: PCI: Bus #06 (-#09) is hidden behind transparent bridge #05 (-#05) (try 'pci=...
Status: RESOLVED DUPLICATE of bug 7531
Alias: None
Product: Drivers
Classification: Unclassified
Component: PCI (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Bernhard Kaindl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-18 04:11 UTC by Neil Wilson
Modified: 2007-10-16 06:29 UTC (History)
2 users (show)

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

Attachments
Dmesg for kernel log error *with* assign-busses (47 bytes, text/plain)
2007-08-18 04:12 UTC, Neil Wilson 		Details
dmesg log *without* assing-busses (29.98 KB, text/x-log)
2007-08-18 04:18 UTC, Neil Wilson 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Neil Wilson 2007-08-18 04:11:39 UTC 
Most recent kernel where this bug did not occur:
Distribution: Ubuntu Gutsy Tribe 4
Hardware Environment: Lenovo 3000 N100 T5300 Intel Processor 

Get 

PCI: Bus #06 (-#09)
is hidden behind transparent bridge #05 (-#05) (try 'pci=assign-busses')
Comment 1 Neil Wilson 2007-08-18 04:12:33 UTC 
Created attachment 12436 [details]
Dmesg for kernel log error *with* assign-busses
Comment 2 Neil Wilson 2007-08-18 04:18:43 UTC 
Created attachment 12437 [details]
dmesg log *without* assing-busses
Comment 3 Bernhard Kaindl 2007-10-16 06:29:39 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 and
* 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.