https://bugzilla.novell.com/show_bug.cgi?id=579932
https://bugzilla.novell.com/show_bug.cgi?id=579932#c24
--- Comment #24 from Andreas Nordal 2010-09-04 18:38:37 UTC ---
The newest kernel, 2.6.35.4, is also affected. Its changelog lists 2 changes
about "apic".
Here is something I found in dmesg after booting 2.6.35.4 (the start of every
line, which is "[ 0.000000] ", is omitted for brevity):
ACPI: RSDP 00000000000f7b40 00024 (v02 Compal)
ACPI: XSDT 000000007fed7c40 00094 (v01 Compal CRESTLNE 06040000 LTP 00000000)
ACPI: FACP 000000007fedfbd2 000F4 (v03 INTEL CRESTLNE 06040000 ALAN 00000001)
ACPI: DSDT 000000007fed9b51 0600D (v02 Compal CRESTLNE 06040000 INTL 20061109)
ACPI: FACS 000000007fee2fc0 00040
ACPI: APIC 000000007fedfcc6 00068 (v01 INTEL CRESTLNE 06040000 LOHR 0000005A)
ACPI: HPET 000000007fedfd2e 00038 (v01 Compal CRESTLNE 06040000 LOHR 0000005A)
ACPI: MCFG 000000007fedfd66 0003C (v01 INTEL CRESTLNE 06040000 LOHR 0000005A)
ACPI: TCPA 000000007fedfda2 00032 (v01 Intel CRESTLNE 06040000 LOHR 0000005A)
ACPI: TMOR 000000007fedfdd4 00026 (v01 PTLTD 06040000 PTL 00000003)
ACPI: SLIC 000000007fedfdfa 00176 (v01 Compal CRESTLNE 06040000 TBD 00000001)
ACPI: APIC 000000007fedff70 00068 (v01 PTLTD ? APIC 06040000 LTP 00000000)
ACPI: BOOT 000000007fedffd8 00028 (v01 PTLTD $SBFTBL$ 06040000 LTP 00000001)
ACPI: SSDT 000000007fed9502 0064F (v01 SataRe SataPri 00001000 INTL 20050624)
ACPI: SSDT 000000007fed8e70 00692 (v01 SataRe SataSec 00001000 INTL 20050624)
ACPI: SSDT 000000007fed8260 0025F (v01 PmRef Cpu0Tst 00003000 INTL 20050624)
ACPI: SSDT 000000007fed81ba 000A6 (v01 PmRef Cpu1Tst 00003000 INTL 20050624)
ACPI: SSDT 000000007fed7cd4 004E6 (v01 PmRef CpuPm 00003000 INTL 20050624)
ACPI: BIOS bug: multiple APIC/MADT found, using 2
ACPI: If "acpi_apic_instance=0" works better, notify linux-acpi@vger.kernel.org
ACPI: Local APIC address 0xfee00000
Faking a node at 0000000000000000-000000007fed0000
Initmem setup node 0 0000000000000000-000000007fed0000 NODE_DATA
[0000000001c531c0 - 0000000001c581bf]
[ffffea0000000000-ffffea0001bfffff] PMD -> [ffff880002600000-ffff8800041fffff]
on node 0
Zone PFN ranges:
DMA 0x00000010 -> 0x00001000
DMA32 0x00001000 -> 0x00100000
Normal empty
Movable zone start PFN for each node
early_node_map[2] active PFN ranges
0: 0x00000010 -> 0x0000009f
0: 0x00000100 -> 0x0007fed0
On node 0 totalpages: 523871
DMA zone: 56 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 3927 pages, LIFO batch:0
DMA32 zone: 7108 pages used for memmap
DMA32 zone: 512780 pages, LIFO batch:31
ACPI: PM-Timer IO Port: 0x1008
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
ACPI: IRQ0 used by override.
ACPI: IRQ2 used by override.
ACPI: IRQ9 used by override.
Using ACPI (MADT) for SMP configuration information
ACPI: HPET id: 0x8086a201 base: 0xfed00000
Note the "BIOS bug", where it uses apic 2 and suggests 0. Normally, it uses 0
and suggests 2, but I booted with acpi_apic_instance=2 this time, which didn't
work any better or worse. 2.6.35.3 also suggests 2, but i have not tried the
suggestion there. I have a Phoenix BIOS.
I just wonder how this bug could be overlooked. It has been in the kernel since
around 2.6.33, is probably not specific to OpenSUSE, and it causes lousy
desktop experience, to say the least.
@Elmar: Do you see any hardware we have in common?
@Jiri : Are kernel developers informed, or will they be?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.