Date: Wed, 02 Mar 2011 14:25:34 -0500 From: Mike Tancsa <mike@sentex.net> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-stable@freebsd.org, Jeremy Chadwick <freebsd@jdc.parodius.com> Subject: Re: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40 Message-ID: <4D6E99AE.7080409@sentex.net> In-Reply-To: <201103021018.52403.jhb@freebsd.org> References: <4D6DA259.4050307@sentex.net> <201103020755.54147.jhb@freebsd.org> <4D6E412F.6080208@sentex.net> <201103021018.52403.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D6E99AE.7080409>