Re: How to diagnose...

Mikael Pettersson (mikpe@csd.uu.se)
Tue, 29 Oct 2002 16:42:45 +0100

Robert L. Harris writes:
> was scrolling so fast I couldn't even read it. It looked like it was
> reporting ACIC errors on a CPU but couldn't quite be sure. It required
> a hard reset as it was unresponsive to c-a-d and sysreq commands.

If it says "APIC error on CPU blah" then you have a problem.
First, upgrade to something a bit more trustworthy, like 2.4.20-pre11
or RedHat's 2.4.18-17.7.x kernel. If that doesn't help, try booting
with "noapic" as parameter to the kernel.

/Mikael
-
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/