This morning I put 2.4.22-rc2-ac3 on a mail server. About 5 mins ago
the box blew up and we got this in a remote syslog:
Aug 23 22:04:08 mailserver1 kernel: Do you have a strange power sav ing mode enabled?
Aug 23 22:04:08 mailserver1 kernel: Uhhuh. NMI received for unknown reason 21.
Aug 23 22:04:08 mailserver1 kernel: Dazed and confused, but trying to continue
ACPI and AMP are NOT enabled. I can attach the .config tomorrow if
someone wants it once the box is back up. It's a 4way P3-550 with
16Gigs of RAM. Himem and 64Gig were the compiled options as well as it
was compiled for P3. Due to the way it locked up there wasn't anything
else we could get debug wise. This is a production box so we had to
roll it back to the previous kernel and no-real debugging options are
available. We do have a machine which is identicle except it is 4Gigs
of ram and instead of a raid0 of 4 disks totalling 200Gigs of space the
other machine has a single disk of 400GB.
Thoughts?
Robert
:wq!
---------------------------------------------------------------------------
Robert L. Harris | GPG Key ID: E344DA3B
@ x-hkp://pgp.mit.edu
DISCLAIMER:
These are MY OPINIONS ALONE. I speak for no-one else.
Life is not a destination, it's a journey.
Microsoft produces 15 car pileups on the highway.
Don't stop traffic to stand and gawk at the tragedy.
On Sun, 2003-08-24 at 03:52, Robert L. Harris wrote:
>
> This morning I put 2.4.22-rc2-ac3 on a mail server. About 5 mins ago
> the box blew up and we got this in a remote syslog:
>
> Aug 23 22:04:08 mailserver1 kernel: Do you have a strange power sav ing mode enabled?
> Aug 23 22:04:08 mailserver1 kernel: Uhhuh. NMI received for unknown reason 21.
> Aug 23 22:04:08 mailserver1 kernel: Dazed and confused, but trying to continue
>
> ACPI and AMP are NOT enabled. I can attach the .config tomorrow if
> someone wants it once the box is back up. It's a 4way P3-550 with
> 16Gigs of RAM. Himem and 64Gig were the compiled options as well as it
> was compiled for P3. Due to the way it locked up there wasn't anything
> else we could get debug wise. This is a production box so we had to
> roll it back to the previous kernel and no-real debugging options are
> available. We do have a machine which is identicle except it is 4Gigs
> of ram and instead of a raid0 of 4 disks totalling 200Gigs of space the
> other machine has a single disk of 400GB.
Have you got ECC errors set to NMI?
Justin