* Re: APIC error on CPU0 (UP APIC kernel)
2001-03-02 2:05 APIC error on CPU0 (UP APIC kernel) Chaskiel M Grundman
@ 2001-03-02 0:32 ` Arnaldo Carvalho de Melo
2001-03-02 17:25 ` Pozsar Balazs
2001-03-02 19:48 ` Chaskiel M Grundman
2 siblings, 0 replies; 4+ messages in thread
From: Arnaldo Carvalho de Melo @ 2001-03-02 0:32 UTC (permalink / raw)
To: Chaskiel M Grundman; +Cc: linux-kernel
Em Thu, Mar 01, 2001 at 09:05:00PM -0500, Chaskiel M Grundman escreveu:
> 2.4 SMP kernels seem to work fine, but using a 2.4.1 or 2.4.2 UP kernel
can you try 2.4.2-ac8 and tell us the results?
> with CONFIG_X86_UP_IOAPIC does not. At some point before the real root
> filesystem is mounted, the system begins spewing
- Arnaldo
^ permalink raw reply [flat|nested] 4+ messages in thread
* APIC error on CPU0 (UP APIC kernel)
@ 2001-03-02 2:05 Chaskiel M Grundman
2001-03-02 0:32 ` Arnaldo Carvalho de Melo
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Chaskiel M Grundman @ 2001-03-02 2:05 UTC (permalink / raw)
To: linux-kernel
I have some single-processr Dell Poweredge 2450 servers that I'm trying
to move to 2.4. They have been running 2.2 SMP kernels for a while with
no problem (to take advantage of the supposed benefit of using the
ioapic).
2.4 SMP kernels seem to work fine, but using a 2.4.1 or 2.4.2 UP kernel
with CONFIG_X86_UP_IOAPIC does not. At some point before the real root
filesystem is mounted, the system begins spewing
APIC error on CPU0: 08(08)
at a high rate and eventually either locks up, or is killed by the
watchdog nmi (at which point control-alt-delete _works_)
2450's use a serverworks chipset. I don't know what other information
might be useful...
Here's an excerpt of the SMP 2.4.2 dmesg output, in case it's of any use:
ENABLING IO-APIC IRQs
...changing IO-APIC physical APIC ID to 1 ... ok.
...changing IO-APIC physical APIC ID to 2 ... ok.
Synchronizing Arb IDs.
init IO_APIC IRQs
IO-APIC (apicid-pin) 1-0, 1-2, 1-3, 1-5, 1-10, 1-11, 1-13, 2-3, 2-8,
2-9, 2-10,
2-11, 2-12, 2-13 not connected.
..TIMER: vector=49 pin1=-1 pin2=0
...trying to set up timer (IRQ0) through the 8259..... (found pin 0) ...works.
activating NMI Watchdog ... done.
number of MP IRQ sources: 27.
number of IO-APIC #1 registers: 16.
number of IO-APIC #2 registers: 16.
testing the IO APIC.......................
IO APIC #1......
.... register #00: 01000000
....... : physical APIC id: 01
.... register #01: 000F0011
....... : max redirection entries: 000F
....... : IO APIC version: 0011
.... register #02: 00000000
....... : arbitration: 00
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 001 01 0 0 0 0 0 1 1 31
01 001 01 0 0 0 0 0 1 1 39
02 000 00 1 0 0 0 0 0 0 00
03 000 00 1 0 0 0 0 0 0 00
04 001 01 0 0 0 0 0 1 1 41
05 000 00 1 0 0 0 0 0 0 00
06 001 01 0 0 0 0 0 1 1 49
07 001 01 0 0 0 0 0 1 1 51
08 001 01 0 0 0 0 0 1 1 59
09 001 01 0 0 0 0 0 1 1 61
0a 000 00 1 0 0 0 0 0 0 00
0b 000 00 1 0 0 0 0 0 0 00
0c 001 01 0 0 0 0 0 1 1 69
0d 000 00 1 0 0 0 0 0 0 00
0e 001 01 0 0 0 0 0 1 1 71
0f 001 01 0 0 0 0 0 1 1 79
IO APIC #2......
.... register #00: 02000000
....... : physical APIC id: 02
.... register #01: 000F0011
....... : max redirection entries: 000F
....... : IO APIC version: 0011
.... register #02: 02000000
....... : arbitration: 02
.... IRQ redirection table:
NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
00 001 01 1 1 0 1 0 1 1 81
01 001 01 1 1 0 1 0 1 1 89
02 001 01 1 1 0 1 0 1 1 91
03 000 00 1 0 0 0 0 0 0 00
04 001 01 1 1 0 1 0 1 1 99
05 001 01 1 1 0 1 0 1 1 A1
06 001 01 1 1 0 1 0 1 1 A9
07 001 01 1 1 0 1 0 1 1 B1
08 000 00 1 0 0 0 0 0 0 00
09 000 00 1 0 0 0 0 0 0 00
0a 000 00 1 0 0 0 0 0 0 00
0b 000 00 1 0 0 0 0 0 0 00
0c 000 00 1 0 0 0 0 0 0 00
0d 000 00 1 0 0 0 0 0 0 00
0e 001 01 1 1 0 1 0 1 1 B9
0f 001 01 1 1 0 1 0 1 1 C1
IRQ to pin mappings:
IRQ1 -> 1
IRQ4 -> 4
IRQ6 -> 6
IRQ7 -> 7
IRQ8 -> 8
IRQ9 -> 9
IRQ12 -> 12
IRQ14 -> 14
IRQ15 -> 15
IRQ16 -> 0
IRQ17 -> 1
IRQ18 -> 2
IRQ20 -> 4
IRQ21 -> 5
IRQ22 -> 6
IRQ23 -> 7
IRQ30 -> 14
IRQ31 -> 15
.................................... done.
calibrating APIC timer ...
..... CPU clock speed is 731.0440 MHz.
..... host bus clock speed is 132.9169 MHz.
cpu: 0, clocks: 1329169, slice: 664584
CPU0<T0:1329168,T1:664576,D:8,S:664584,C:1329169>
Setting commenced=1, go go go
PCI: PCI BIOS revision 2.10 entry at 0xfc79e, last bus=3
PCI: Using configuration type 1
PCI: Probing PCI hardware
PCI: ServerWorks host bridge: last bus ff
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
Unknown bridge resource 0: assuming transparent
Unknown bridge resource 1: assuming transparent
Unknown bridge resource 2: assuming transparent
PCI: Discovered primary peer bus 02 [IRQ]
PCI: Using IRQ router ServerWorks [1166/0200] at 00:0f.0
PCI->APIC IRQ transform: (B0,I2,P0) -> 20
PCI->APIC IRQ transform: (B0,I8,P0) -> 22
PCI->APIC IRQ transform: (B2,I8,P0) -> 16
[...]
ServerWorks OSB4: IDE controller on PCI bus 00 dev 79
ServerWorks OSB4: chipset revision 0
ServerWorks OSB4: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x08b0-0x08b7, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x08b8-0x08bf, BIOS settings: hdc:pio, hdd:pio
hda: TOSHIBA CD-ROM XM-7002B, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
[...]
VFS: Mounted root (ext2 filesystem).
SCSI subsystem driver Revision: 1.00
kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
megaraid: v107 (December 22, 1999)
megaraid: found 0x8086:0x1960: in 00:02.1
scsi0 : Found a MegaRAID controller at 0xf8820000, IRQ: 20
megaraid: [1.01:1p00] detected 1 logical drives
[..]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: APIC error on CPU0 (UP APIC kernel)
2001-03-02 2:05 APIC error on CPU0 (UP APIC kernel) Chaskiel M Grundman
2001-03-02 0:32 ` Arnaldo Carvalho de Melo
@ 2001-03-02 17:25 ` Pozsar Balazs
2001-03-02 19:48 ` Chaskiel M Grundman
2 siblings, 0 replies; 4+ messages in thread
From: Pozsar Balazs @ 2001-03-02 17:25 UTC (permalink / raw)
To: Chaskiel M Grundman; +Cc: linux-kernel
I'm having similar messages, about 2-3 per day.
So far I saw these variants:
APIC error on CPU0: 00(04)
APIC error on CPU0: 00(02)
APIC error on CPU0: 02(02)
APIC error on CPU0: 02(04)
APIC error on CPU0: 04(02)
This is a Abit VP6, with 1 Celeron 433(66).
(machine passes memtest).
What does this mean?
Note that everything seems to go on fine, no hangups etc.
Balazs Pozsar.
On Thu, 1 Mar 2001, Chaskiel M Grundman wrote:
> I have some single-processr Dell Poweredge 2450 servers that I'm trying
> to move to 2.4. They have been running 2.2 SMP kernels for a while with
> no problem (to take advantage of the supposed benefit of using the
> ioapic).
>
> 2.4 SMP kernels seem to work fine, but using a 2.4.1 or 2.4.2 UP kernel
> with CONFIG_X86_UP_IOAPIC does not. At some point before the real root
> filesystem is mounted, the system begins spewing
>
> APIC error on CPU0: 08(08)
>
> at a high rate and eventually either locks up, or is killed by the
> watchdog nmi (at which point control-alt-delete _works_)
>
> 2450's use a serverworks chipset. I don't know what other information
> might be useful...
>
> Here's an excerpt of the SMP 2.4.2 dmesg output, in case it's of any use:
>
> ENABLING IO-APIC IRQs
> ...changing IO-APIC physical APIC ID to 1 ... ok.
> ...changing IO-APIC physical APIC ID to 2 ... ok.
> Synchronizing Arb IDs.
> init IO_APIC IRQs
> IO-APIC (apicid-pin) 1-0, 1-2, 1-3, 1-5, 1-10, 1-11, 1-13, 2-3, 2-8,
> 2-9, 2-10,
> 2-11, 2-12, 2-13 not connected.
> ..TIMER: vector=49 pin1=-1 pin2=0
> ...trying to set up timer (IRQ0) through the 8259..... (found pin 0) ...works.
> activating NMI Watchdog ... done.
> number of MP IRQ sources: 27.
> number of IO-APIC #1 registers: 16.
> number of IO-APIC #2 registers: 16.
> testing the IO APIC.......................
>
> IO APIC #1......
> .... register #00: 01000000
> ....... : physical APIC id: 01
> .... register #01: 000F0011
> ....... : max redirection entries: 000F
> ....... : IO APIC version: 0011
> .... register #02: 00000000
> ....... : arbitration: 00
> .... IRQ redirection table:
> NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> 00 001 01 0 0 0 0 0 1 1 31
> 01 001 01 0 0 0 0 0 1 1 39
> 02 000 00 1 0 0 0 0 0 0 00
> 03 000 00 1 0 0 0 0 0 0 00
> 04 001 01 0 0 0 0 0 1 1 41
> 05 000 00 1 0 0 0 0 0 0 00
> 06 001 01 0 0 0 0 0 1 1 49
> 07 001 01 0 0 0 0 0 1 1 51
> 08 001 01 0 0 0 0 0 1 1 59
> 09 001 01 0 0 0 0 0 1 1 61
> 0a 000 00 1 0 0 0 0 0 0 00
> 0b 000 00 1 0 0 0 0 0 0 00
> 0c 001 01 0 0 0 0 0 1 1 69
> 0d 000 00 1 0 0 0 0 0 0 00
> 0e 001 01 0 0 0 0 0 1 1 71
> 0f 001 01 0 0 0 0 0 1 1 79
> IO APIC #2......
> .... register #00: 02000000
> ....... : physical APIC id: 02
> .... register #01: 000F0011
> ....... : max redirection entries: 000F
> ....... : IO APIC version: 0011
> .... register #02: 02000000
> ....... : arbitration: 02
> .... IRQ redirection table:
> NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect:
> 00 001 01 1 1 0 1 0 1 1 81
> 01 001 01 1 1 0 1 0 1 1 89
> 02 001 01 1 1 0 1 0 1 1 91
> 03 000 00 1 0 0 0 0 0 0 00
> 04 001 01 1 1 0 1 0 1 1 99
> 05 001 01 1 1 0 1 0 1 1 A1
> 06 001 01 1 1 0 1 0 1 1 A9
> 07 001 01 1 1 0 1 0 1 1 B1
> 08 000 00 1 0 0 0 0 0 0 00
> 09 000 00 1 0 0 0 0 0 0 00
> 0a 000 00 1 0 0 0 0 0 0 00
> 0b 000 00 1 0 0 0 0 0 0 00
> 0c 000 00 1 0 0 0 0 0 0 00
> 0d 000 00 1 0 0 0 0 0 0 00
> 0e 001 01 1 1 0 1 0 1 1 B9
> 0f 001 01 1 1 0 1 0 1 1 C1
> IRQ to pin mappings:
> IRQ1 -> 1
> IRQ4 -> 4
> IRQ6 -> 6
> IRQ7 -> 7
> IRQ8 -> 8
> IRQ9 -> 9
> IRQ12 -> 12
> IRQ14 -> 14
> IRQ15 -> 15
> IRQ16 -> 0
> IRQ17 -> 1
> IRQ18 -> 2
> IRQ20 -> 4
> IRQ21 -> 5
> IRQ22 -> 6
> IRQ23 -> 7
> IRQ30 -> 14
> IRQ31 -> 15
> .................................... done.
> calibrating APIC timer ...
> ..... CPU clock speed is 731.0440 MHz.
> ..... host bus clock speed is 132.9169 MHz.
> cpu: 0, clocks: 1329169, slice: 664584
> CPU0<T0:1329168,T1:664576,D:8,S:664584,C:1329169>
> Setting commenced=1, go go go
> PCI: PCI BIOS revision 2.10 entry at 0xfc79e, last bus=3
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> PCI: ServerWorks host bridge: last bus ff
> Unknown bridge resource 0: assuming transparent
> Unknown bridge resource 1: assuming transparent
> Unknown bridge resource 2: assuming transparent
> Unknown bridge resource 0: assuming transparent
> Unknown bridge resource 1: assuming transparent
> Unknown bridge resource 2: assuming transparent
> PCI: Discovered primary peer bus 02 [IRQ]
> PCI: Using IRQ router ServerWorks [1166/0200] at 00:0f.0
> PCI->APIC IRQ transform: (B0,I2,P0) -> 20
> PCI->APIC IRQ transform: (B0,I8,P0) -> 22
> PCI->APIC IRQ transform: (B2,I8,P0) -> 16
> [...]
> ServerWorks OSB4: IDE controller on PCI bus 00 dev 79
> ServerWorks OSB4: chipset revision 0
> ServerWorks OSB4: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0x08b0-0x08b7, BIOS settings: hda:DMA, hdb:pio
> ide1: BM-DMA at 0x08b8-0x08bf, BIOS settings: hdc:pio, hdd:pio
> hda: TOSHIBA CD-ROM XM-7002B, ATAPI CD/DVD-ROM drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> [...]
> VFS: Mounted root (ext2 filesystem).
> SCSI subsystem driver Revision: 1.00
> kmod: failed to exec /sbin/modprobe -s -k scsi_hostadapter, errno = 2
> megaraid: v107 (December 22, 1999)
> megaraid: found 0x8086:0x1960: in 00:02.1
> scsi0 : Found a MegaRAID controller at 0xf8820000, IRQ: 20
> megaraid: [1.01:1p00] detected 1 logical drives
> [..]
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: APIC error on CPU0 (UP APIC kernel)
2001-03-02 2:05 APIC error on CPU0 (UP APIC kernel) Chaskiel M Grundman
2001-03-02 0:32 ` Arnaldo Carvalho de Melo
2001-03-02 17:25 ` Pozsar Balazs
@ 2001-03-02 19:48 ` Chaskiel M Grundman
2 siblings, 0 replies; 4+ messages in thread
From: Chaskiel M Grundman @ 2001-03-02 19:48 UTC (permalink / raw)
To: Arnaldo Carvalho de Melo; +Cc: linux-kernel, Mark Hahn
Excerpts from mail: 1-Mar-101 Re: APIC error on CPU0 (UP .. by Arnaldo
C. de Melo@conec
> can you try 2.4.2-ac8 and tell us the results?
No change (I used 2.4.2-ac9, since that was available...). (The watchdog
doesn't trip and display output, but eventually the errors stop and
rebooting is possible)
> can you run 2.4.2 with noapic?
No change, either on 2.4.2 or 2.4.2-ac9
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2001-03-02 19:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-03-02 2:05 APIC error on CPU0 (UP APIC kernel) Chaskiel M Grundman
2001-03-02 0:32 ` Arnaldo Carvalho de Melo
2001-03-02 17:25 ` Pozsar Balazs
2001-03-02 19:48 ` Chaskiel M Grundman
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®