Bug 6038

Created attachment 7278 [details]
output of 2.6.6-rc2-mm1 without hda attached

Created attachment 7279 [details]
output of 2.6.6-rc2-mm1 without hda attached2

Created attachment 7280 [details]
output of 2.6.6-rc2-mm1 with hda attached

Created attachment 7281 [details]
acpidump from 2.6.13.5

Created attachment 7282 [details]
/proc/interrupts from 2.6.13.5

Created attachment 7283 [details]
lspci -vv from 2.6.13.5

so after i found out where to up the attachments... here they are^^

a short version of boot:

normal boot dmesg (2.6.13.5):
...
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE-CK804: 0000:00:06.0 (rev f2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: IC35L180AVV207-1, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: ASUS CRW-4012A, ATAPI CD/DVD-ROM drive
hdd: _NEC DVD_RW ND-1300A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
PDC20265: IDE controller at PCI slot 0000:05:08.0
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
ACPI: PCI Interrupt 0000:05:08.0[A] -> Link [APC3] -> GSI 18 (level,
low) -> IRQ 18
PDC20265: chipset revision 2
PDC20265: ROM enabled at 0x60000000
PDC20265: 100% native mode on irq 18
PDC20265: (U)DMA Burst Bit DISABLED Primary PCI Mode Secondary PCI Mode.
PDC20265: FORCING BURST BIT 0x00->0x01 ACTIVE
    ide2: BM-DMA at 0x9400-0x9407, BIOS settings: hde:pio, hdf:pio
    ide3: BM-DMA at 0x9408-0x940f, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: ST380021A, ATA DISK drive
ide2 at 0x8400-0x8407,0x8802 on irq 18
Probing IDE interface ide3...
hda: max request size: 1024KiB
hda: 361882080 sectors (185283 MB) w/7965KiB Cache, CHS=22526/255/63,
UDMA(100)
hda: cache flushes supported
 hda: hda1 < hda5 hda6 hda7 hda8 >
...

boot dmesg from 2.6.16-rc2-mm1:
NFORCE-CK804: IDE controller at PCI slot 0000:00:06.0
NFORCE-CK804: chipset revision 242
NFORCE-CK804: not 100% native mode: will probe irqs later
NFORCE-CK804: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE-CK804: 0000:00:06.0 (rev f2) UDMA133 controller
    ide0: BM-DMA at 0xf000-0xf007, BIOS settings: hda:DMA, hdb:DMA
NFORCE-CK804: simplex device: DMA disabled
ide1: NFORCE-CK804 Bus-Master DMA disabled (BIOS)
hda: IC35L180AVV207-1, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hdc: ASUS CRW-4012A, ATAPI CD/DVD-ROM drive
hdd: _NEC DVD_RW ND-1300A, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
PDC20265: IDE controller at PCI slot 0000:05:08.0
ACPI: PCI Interrupt Link [APC3] BIOS reported IRQ 5, using IRQ 18
ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
GSI 16 sharing vector 0xB1 and IRQ 16
ACPI: PCI Interrupt 0000:05:08.0[A] -> Link [APC3] -> GSI 18 (level,
low) -> IRQ 16
PDC20265: chipset revision 2
PDC20265: 100% native mode on irq 16
PDC20265: port 0x01f0 already claimed by ide0
PDC20265: port 0x0170 already claimed by ide1
PDC20265: neither IDE port enabled (BIOS)
hda: max request size: 512KiB
hda: 361882080 sectors (185283 MB) w/7965KiB Cache, CHS=22526/255/63,
UDMA(100)
hda: cache flushes supported
 hda: <4>hda: dma_timer_expiry: dma status == 0xff
hda: dma_timer_expiry: dma status == 0xff
hda: dma_timer_expiry: dma status == 0xff
...
... and so on, never ending...

>ACPI: PCI Interrupt Link [APC3] BIOS reported IRQ 5, using IRQ 18
>ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
Can you have a full dmesg in the failure case? such as get from serial console.

Created attachment 7287 [details]
dmesg from 2.6.13.5

oh i forgot full dmesg of 2.6.13.5...

i will try to get dmesg from 2.6.16-rc2-mm1 if i could get it...

hm, question... the serial console would show the same as on my jpeg's or? (ok
I've not compiled the networksetup into the kernel of 2.6.16 but the important
parts of the ide controllers are included, so I think the jpegs should show you
the output of dmesg... (please correct me if i'm wrong))

You could get the full dmesg from serial console (in another PC). please refer 
to kernel source/Documentation/serial-console.txt.

Please boot the latest kernel with "acpi=off",
attach the complete output from "dmesg -s64000"
and paste a copy of /proc/interrupts.

You mentioned that booting with "noapic" failed also.
Please boot with "noapic" and "debug" and attach
the complete serial console log.

Created attachment 7328 [details]
Serial-Console-2.6.13.5

ok here comes the serial console output...

Created attachment 7329 [details]
Serial-Console-2.6.16-normal (with acpi....)

Created attachment 7330 [details]
2.6.16-normal(with acpi)-and-debug

Created attachment 7331 [details]
2.6.16-acpi=off and bios setting apic=disabled

Created attachment 7332 [details]
2.6.16-acpi=off and debug and bios apic=enabled

Created attachment 7333 [details]
2.6.16 noapic and debug and bios apic enabled

Created attachment 7334 [details]
2.6.16 noapic and debug and bios apic=disabled

Created attachment 7335 [details]
2.6.16 /proc/interrupts with acpi=off

so, i hope everything is up now...

f.y.i, today tested with 2.6.16-rc4-mm1, output still the same...

so... after many testcompiles i found out that the bug was introduced by
2.6.14-rc1 (2.6.13-git12 runs fine)...

as workaround for booting the kernel, i've added the folliwing lines:

in arch/x86_64/pci/mmconfig.c line 155
        /* Kludge for now. Don't use mmconfig on AMD systems because
           those have some busses where mmconfig doesn't work,
           and we don't parse ACPI MCFG well enough to handle that.
           Remove when proper handling is added. */
        if (boot_cpu_data.x86_vendor == X86_VENDOR_AMD)
                return 0;


so i think there is still something buggy in ACPI MCFG^^

(testet with 2.6.15)

tested 2.6.16 => no change

Hi, Patrick, MCFG handling has been changed in recent kernel. Would you please kindly retest to see if this bug still exist? thanks.

Hi Michael,

i'll test it this weekend and post the results...

still the same with 2.6.23.8...

do you need the output?

Hi, Patrick
Will you please attach the dmesg output? It will be  great if you can enable the debug of ACPI and PCI in kernel configuration.
Thanks.

Hi, Patrick
Will you please try to boot the system with the option of pci=nommconf and attach the output of dmesg?
Thanks.

Hi,

i've just tested the pci=nommconf option and the system boots fine.
I'll post the dmesg output in the next few days.

Created attachment 14435 [details]
output of 2.6.23.8 without pci=nommconf

Created attachment 14436 [details]
output of 2.6.23.8 with pci=nommconf

Patrick, this code changed quite a bit in 2.6.24 and 2.6.25, does the problem still occur for you there?

Hi Jesse,

the problem ist fixed!!! (testet with 2.6.24.4)

thanks to all who worked on it!

Thanks for this update.