Re: apic errors and looping with 2.4, none with 2.2 (supermicro/serverworksLE chipset)
From: Chris Stromsoe
Date: Thu Mar 25 2004 - 20:21:44 EST
On Thu, 25 Mar 2004, Maciej W. Rozycki wrote:
> On Wed, 24 Mar 2004, Marcelo Tosatti wrote:
> > Maybe Maciej or Mikael have more clue of what might be happening.
> > On Wed, Mar 24, 2004 at 02:50:32AM -0800, Chris Stromsoe wrote:
> > > I've rebooted with noapic and nolapic and the machine seemed to be
> > > stable for a while. Then I got:
> > >
> > > Mar 24 00:27:08 dahlia kernel: APIC error on CPU1: 00(02)
> > > Mar 24 00:27:08 dahlia kernel: APIC error on CPU0: 00(02)
> > > Mar 24 00:27:08 dahlia kernel: spurious APIC interrupt on CPU#0, should never happen.
> > > Mar 24 00:27:13 dahlia kernel: APIC error on CPU1: 02(08)
> > > Mar 24 00:27:13 dahlia kernel: APIC error on CPU0: 02(08)
> > > I added nosmp to the lilo append line and rebooted.
> > >
> > > noapic, nolapic, and nosmp seems to be stable. I haven't had
> > > anything logged in the last 2 hours. Are there known APIC or SMP
> > > problems with serverworks LE chipsets or supermicro motherboards and
> > > 2.4? What are the steps to troubleshooting an APIC problem?
> As long as you boot more than a single CPU, local APIC units are used
> at least to send IPIs. The error messages you see report receive
> checksum and receive acceptance errors. The latters result from the
> formers and all of them, including the spurious APIC interrupt are
> results of signal errors (noise?) during a transmission over the
> inter-APIC serial bus. This is a hardware problem. I'd start by
> checking the power supply first.
The only way that I've been able to boot and stay up is with nosmp,
noapic, and nolapic. I'll try replacing the power supply and see if that
helps things out. It's going to take me a few days to get a replacement
-- is there anything else that I should check while I'm waiting?
> + Maciej W. Rozycki, Technical University of Gdansk, Poland +
> + e-mail: macro@xxxxxxxxxxxxx, PGP key available +
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/