Most recent kernel where this bug did not occur: ?
Software Environment: PXE-booted kernel, with some custom initrd
--- Problem Description:
Kernel doesn't boot, unless "acpi=off" or "pci=conf1" is given.
"acpi=force", "acpi=strict", "acpi=ht", "acpi=noirq", "pci=noacpi",
"noapic hda=noprobe hdc=noprobe" don't help.
--- Last messages (typed, are abbreviated):
ACPI: bus type pci registered
PCI: using MMConfig
Setting up standard PCI resources
evgpeblk-0952  ev_create_gpe_block: GPE00 to 1F [_GPE] 4 regs on int 0x9
evgpeblk-1048  ev_initialize_gpe_block: Found 9 Wake, Enabled 1 Runtime GPEs in this block
Completing Region/Field/Buffer/Package init.: .....
Init. 27/29 Regions 0/0 Fields 57/57 Buffers 14/23 Packages (729 nodes)
Init Dev./Proc/Thermal Objects by exec. _INI methods:..
Exec. 2 _INI methods require 0 _STA exec. (examined 58 obj)
ACPI: interpreter enabled
ACPI: (supports S0 S3 S4 S5)
ACPI: Using IOAPIC for int. rout.
ACPI: PCI Root Bridge [PCI0] (0000:00)
--- Steps to reproduce: Boot kernel.
--- Dumps get attached.
Created attachment 12218 [details]
could you please try "pci=nommconf"?
Created attachment 12219 [details]
dmesg with acpi=off
Created attachment 12220 [details]
lspci with acpi=off
(In reply to comment #2)
> could you please try "pci=nommconf"?
This may be the same problem,
would you please have a look at it?
This basically is a BIOS bug. MCFG base should be written to MCH register in intel chipset, so please give the lspci -xxx output, and we can check if MCH register value matches with MCFG table.
Here you are ...
Created attachment 12802 [details]
Created attachment 12810 [details]
Fourunately we have a similar system here. After debugging, we found there is a conflict between memory access when detecting PCI mem BAR and MCFG memory access. Attached workaround patch should fix the issue. I'll send out a fix to LKML later.
Short test indicates that it seems to work - Having 10 minutes uptime, copying a gigabyte of data from the network to the harddisk.
This is an incorrect patch; it will cause some machines to hang (as it
disables access from the CPU to RAM ...). The patch which is likely to
be merged can be found at http://marc.info/?l=linux-kernel&m=118809338631160&w=2
moving to Drivers/PCI
*** Bug 9127 has been marked as a duplicate of this bug. ***
*** Bug 8308 has been marked as a duplicate of this bug. ***
One of the fixes for this problem made it upstream, so we can probably close this one.
184.108.40.206 is still fucked without pci=nommconfig.
i can confirm that it is fixed on 2.6.25-r5-git3.
This bug was fixed.