Re: kernel 2.2.15 - Uhhuh NMI Received

From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Tue May 23 2000 - 09:17:27 EDT

Next message: Guus Sliepen: "Re: [RFC] Linux Kernel Benchmark Suite"

Previous message: Richard B. Johnson: "Re: 8259 initialization with AMD SC520 chip (586)"
In reply to: Sammy Lau: "kernel 2.2.15 - Uhhuh NMI Received"
Next in thread: Andrey Savochkin: "Re: kernel 2.2.15 - Uhhuh NMI Received"
Reply: Andrey Savochkin: "Re: kernel 2.2.15 - Uhhuh NMI Received"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> the message I've got is from a function called mem_parity_error
> (arch/i386/kernel/trap.c). As the RAM chip I'm using doesn't have parity
> check, I assume mem_parity_error should not be called in any

Some bus faults also report NMI

> Is there any way for me to gather more information to make sure it is a
> faulty memory problem or it is already a known bug? I'm trying to
> provide more info in this mail. Sorry for this bulky e-mail and please
> excuse me for any bogus points I've given above.

Does it happen if you run 2.2.15 with the 2.2.14 eepro100 driver ?

Alan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

Next message: Guus Sliepen: "Re: [RFC] Linux Kernel Benchmark Suite"
Previous message: Richard B. Johnson: "Re: 8259 initialization with AMD SC520 chip (586)"
In reply to: Sammy Lau: "kernel 2.2.15 - Uhhuh NMI Received"
Next in thread: Andrey Savochkin: "Re: kernel 2.2.15 - Uhhuh NMI Received"
Reply: Andrey Savochkin: "Re: kernel 2.2.15 - Uhhuh NMI Received"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue May 23 2000 - 09:21:56 EDT