[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-smp
Subject:    APIC error after noapic
From:       Tim Kay <timk () advfn ! com>
Date:       2001-11-13 11:48:12
[Download RAW message or body]

Hi,

I'm experiencing a lot of trouble using an SMP Dell PowerEdge box and a 
kernel 2.4 build getting  

Nov 13 11:12:38 proxy14 kernel: APIC error on CPU0: 02(02)
Nov 13 11:12:38 proxy14 kernel: APIC error on CPU1: 01(01)
Nov 13 11:37:52 proxy14 kernel: APIC error on CPU1: 01(02)
Nov 13 11:37:52 proxy14 kernel: APIC error on CPU0: 02(01)
Nov 13 11:48:42 proxy14 kernel: APIC error on CPU1: 02(02)
Nov 13 11:48:42 proxy14 kernel: APIC error on CPU0: 01(01)
Nov 13 11:53:22 proxy14 kernel: APIC error on CPU0: 01(02)


I understand that this means the BIOS is buggy so I turned off apic for the 
machine. /proc/interrupts says that everything is using old XT style 
interrupt IO and that nothing is using CPU1 for IRQ I/O:

---dmesg
Kernel command line: auto BOOT_IMAGE=2.4.14 ro root=805 
BOOT_FILE=/boot/vmlinuz-2.4.14 nmi_watchdog=1 noapic

enabled ExtINT on CPU#0
masked ExtINT on CPU#1
---
           CPU0       CPU1
  0:   35568211          0          XT-PIC  timer
  1:       1121          0          XT-PIC  keyboard
  2:          0          0          XT-PIC  cascade
  3:    1087558          0          XT-PIC  aic7xxx
  4:        622          0          XT-PIC  serial
  5:  107573912          0          XT-PIC  e100
 11:         16          0          XT-PIC  aic7xxx
 14:          3          0          XT-PIC  ide0
NMI:          0          0
LOC:   35566957   35566914
ERR:        201
MIS:          0
 
but I'm still getting the damn error. Should I take this up with Dell, Server 
Works who make the motherboard (an OSB4) or you kernel folks for what seems 
to be an erroneous error message. ( I wouldn't care about the error but 
eventually the machine the machines dies with a non responsive con and I lose 
the box, I suspect that it stops answering interrupt requests from the NIC, 
but this only holds as a possibility if the error is in some way correct.) 
Any info on this anyone 

Tim Kay

timk@advfn.com
-
To unsubscribe from this list: send the line "unsubscribe linux-smp" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[prev in list] [next in list] [prev in thread] [next in thread]