Bug 225672 - ICH4: Busses #02 (-#05) and #06 (-#09) are hidden behind transparent bridge #01 (-#01)
Summary: ICH4: Busses #02 (-#05) and #06 (-#09) are hidden behind transparent bridge #...
Status: RESOLVED NORESPONSE
Alias: None
Product: openSUSE 10.2
Classification: openSUSE
Component: Kernel (show other bugs)
Version: RC 1
Hardware: i586 Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Bernhard Kaindl
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-12-04 03:03 UTC by Berthold Degen
Modified: 2007-10-05 09:30 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Berthold Degen 2006-12-04 03:03:40 UTC 
<7>PCI: Probing PCI hardware (bus 00)
<7>Boot video device is 0000:00:02.0
<4>PCI quirk: region e400-e47f claimed by ICH4 ACPI/GPIO/TCO
<4>PCI quirk: region ec00-ec3f claimed by ICH4 GPIO
<6>PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
<6>PCI: Transparent bridge - 0000:00:1e.0
<4>PCI: Bus #02 (-#05) is hidden behind transparent bridge #01 (-#01) (try 'pci=assign-busses')
<4>Please report the result to linux-kernel to fix this permanently
<4>PCI: Bus #06 (-#09) is hidden behind transparent bridge #01 (-#01) (try 'pci=assign-busses')
<4>Please report the result to linux-kernel to fix this permanently
<7>ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
Comment 1 Bernhard Kaindl 2007-02-01 11:29:32 UTC 
Thanks, is this a boot log from an Intel-CPU Laptop with CardBus slots?

If so, Yenta incliuded in your kernel built should try to fix the issue
(the kernel messages which are printed when yenta is loaded should say so)
and if you insert a CardBus card, the PCI device of the card should show
up in lspci (or otherwise just work)

In this specific case, these messages are superflous and should be removed,
and I'll try to find the time to write a proper check to catch that.
Comment 2 Bernhard Kaindl 2007-02-01 13:14:31 UTC 
See comment #2 of 237229 for more information and
(if your really want, usually no) bug 146438 for in-depth information.
It's also tracked http://bugzilla.kernel.org/show_bug.cgi?id=2944
Comment 3 Stephan Kulow 2007-10-05 09:30:04 UTC 
closing old bug