Bug 9049 - pci=assign-busses suggested when booting my system
Summary: pci=assign-busses suggested when booting my system
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-09-21 01:36 UTC by Pacho Ramos
Modified: 2023-10-11 09:00 UTC (History)
6 users (show)

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


Attachments

Description Pacho Ramos 2007-09-21 01:36:57 UTC
Most recent kernel where this bug did not occur: 2.6.22.6
Distribution: Gentoo Linux
Hardware Environment: lspci output:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express Memory Controller Hub (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 945GM/PM/GMS/940GML and 945GT Express PCI Express Root Port (rev 03)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 (rev 02)
00:1c.3 PCI bridge: Intel Corporation 82801G (ICH7 Family) PCI Express Port 4 (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #2 (rev 02)
00:1d.2 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #3 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801G (ICH7 Family) USB UHCI #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
01:00.0 VGA compatible controller: nVidia Corporation Quadro NVS 110M / GeForce Go 7300 (rev a1)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 8168 (rev 01)
03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
04:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3)
04:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 08)
04:01.2 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 17)
04:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 08)



Problem Description: I get the following message in dmesg:

ACPI: bus type pci registered
PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
PCI: Not using MMCONFIG.
PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=5
PCI: Using configuration type 1
Setting up standard PCI resources
ACPI: Interpreter enabled
ACPI: (supports S0 S1 S3 S4 S5)
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Probing PCI hardware (bus 00)
PCI quirk: region 0800-087f claimed by ICH6 ACPI/GPIO/TCO
PCI quirk: region 0480-04bf claimed by ICH6 GPIO
PCI: Transparent bridge - 0000:00:1e.0
PCI: Bus #05 (-#08) is hidden behind transparent bridge #04 (-#05) (try
'pci=assign-busses')
Please report the result to linux-kernel to fix this permanently


After adding pci=assign-busses it works ok

Thanks
Comment 1 Bernhard Kaindl 2007-10-16 06:27:51 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 ***
Comment 2 Pacho Ramos 2007-10-16 07:26:59 UTC
Thanks a lot

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