I had a machine deadlock just now and the only thing on the serial console was CPU0: local APIC error 0x40 CPU1: local APIC error 0x40 prior to it hanging. Anyone know what that error is ? Googling didnt really show much definitive. Someone suggested bad hardware ? Is there a way to narrow that down ? Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Xeon(R) CPU 3050 @ 2.13GHz (2128.01-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Family = 6 Model = f Stepping = 6 Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE> Features2=0xe3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM> AMD Features=0x20100000<NX,LM> AMD Features2=0x1<LAHF> TSC: P-state invariant real memory = 4294967296 (4096 MB) avail memory = 3676545024 (3506 MB) ACPI APIC Table: <PTLTD APIC > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 ioapic0 <Version 2.0> irqs 0-23 on motherboard ioapic1 <Version 2.0> irqs 24-47 on motherboard kbd1 at kbdmux0 acpi0: <PTLTD RSDT> on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0 cpu0: <ACPI CPU> on acpi0 cpu1: <ACPI CPU> on acpi0 pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0 pci0: <ACPI PCI bus> on pcib0 pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0 pci1: <ACPI PCI bus> on pcib1 pcib2: <ACPI PCI-PCI bridge> irq 17 at device 28.0 on pci0 pci9: <ACPI PCI bus> on pcib2 pcib3: <ACPI PCI-PCI bridge> at device 0.0 on pci9 pci10: <ACPI PCI bus> on pcib3 em0: <Intel(R) PRO/1000 Legacy Network Connection 1.0.3> port 0x4000-0x403f mem 0xe0240000-0xe025ffff,0xe0200000-0xe023ffff irq 24 at device 1.0 on pci10 em0: [FILTER] em0: Ethernet address: 00:1b:21:08:32:a8 em1: <Intel(R) PRO/1000 Legacy Network Connection 1.0.3> port 0x4040-0x407f mem 0xe0260000-0xe027ffff,0xe0280000-0xe02bffff irq 25 at device 1.1 on pci10 em1: [FILTER] em1: Ethernet address: 00:1b:21:08:32:a9 pcib4: <ACPI PCI-PCI bridge> irq 17 at device 28.4 on pci0 pci13: <ACPI PCI bus> on pcib4 ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/
Jeremy Chadwick
2011-Mar-02 02:04 UTC
CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
On Tue, Mar 01, 2011 at 08:50:17PM -0500, Mike Tancsa wrote:> I had a machine deadlock just now and the only thing on the serial > console was > > CPU0: local APIC error 0x40 > CPU1: local APIC error 0x40 > > prior to it hanging. Anyone know what that error is ? Googling didnt > really show much definitive. Someone suggested bad hardware ? Is there > a way to narrow that down ?The error in question I'm not familiar with, but the code in src/sys/x86/x86/local_apic.c indicates that 0x40 is the contents of the LAPIC ESR (error status register). Please provide full output from a verbose boot. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB |
John Baldwin
2011-Mar-02 16:48 UTC
CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
On Wednesday, March 02, 2011 8:07:59 am Mike Tancsa wrote:> On 3/2/2011 7:55 AM, John Baldwin wrote: > > > > Hmm, the interrupt pins on the each lapic look fine (they all either have a > > legal vector, are using NMI delivery, or are masked). > > > > All of the places that send IPIs have the interrupt vectors hard-coded as > > constant values in the code. > > > > Unfortunately there is no register that tells us which illegal vector was > > posted. > > > > Were you doing anything related to changing the state of device interrupts > > (cpuset -x, kldload, kldunload, etc.) when this happened? > > Hi, > No, nothing at all. I checked the logs again and nothing unusual > leading up to it, nor was anything recorded on the serial console other > than that error. Do you think its just a hardware issue?No, was trying to think if there was a scenario where an I/O APIC pin or MSI message could specify an illegal vector. Can you reproduce this at all? -- John Baldwin
On 3/2/2011 10:18 AM, John Baldwin wrote:>> >> Hi, >> No, nothing at all. I checked the logs again and nothing unusual >> leading up to it, nor was anything recorded on the serial console other >> than that error. Do you think its just a hardware issue? > > No, was trying to think if there was a scenario where an I/O APIC pin or MSI > message could specify an illegal vector. > > Can you reproduce this at all?Not sure. Its the first time I have ever seen this error. In the past, the box would be crashing for other reasons after 2-5 days. However, with the fixes from glebius and mlaier all seemed to have been fixed. The box was up 11 days when it hung with that error. I could not even break into the debugger. Hence, I was thinking perhaps the hardware is all of a sudden showing an issue. The two active NICs are using the legacy interrupts interrupt total rate irq1: atkbd0 3 0 irq4: uart0 29974 0 irq6: fdc0 5 0 irq14: ata0 125592 2 irq15: ata1 48 0 irq24: em0 93380742 1529 irq25: em1 96506206 1580 cpu0: timer 117681138 1927 cpu1: timer 117682130 1927 Total 425405838 6967 ---Mike>-- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/
On Tue, Mar 1, 2011 at 5:50 PM, Mike Tancsa <mike@sentex.net> wrote:> I had a machine deadlock just now and the only thing on the serial > console was > > CPU0: local APIC error 0x40 > CPU1: local APIC error 0x40 > > prior to it hanging. ?Anyone know what that error is ? Googling didnt > really show much definitive. ?Someone suggested bad hardware ? Is there > a way to narrow that down ?I too get this error all the time on my AMD 6400+ Dual Core with an ASUS motherboard. I'll post some feedback when it happens again. Problem is everytime it happens, the system completely locks up and a power cycle is needed.
`CPU0: local APIC error 0x40" I get this error on my ThinkPad R400(Intel Core2 T6570). -- Best regards, Yanhui
Nikolay Denev
2011-Mar-03 08:08 UTC
CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
On 3 Mar, 2011, at 02:39 , Yanhui Shen wrote:> `CPU0: local APIC error 0x40" > > I get this error on my ThinkPad R400(Intel Core2 T6570). > > > -- > Best regards, > Yanhui > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"I saw this error too a few days ago, it was wen I plugged a USB keyboard to a HP EX470 machine.
John Baldwin
2011-Mar-03 15:16 UTC
CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
On Wednesday, March 02, 2011 7:39:56 pm Yanhui Shen wrote:> `CPU0: local APIC error 0x40" > > I get this error on my ThinkPad R400(Intel Core2 T6570).Do you get a hang or does the machine keep working fine? -- John Baldwin