RE: [Xen-devel] memory error?

[James Harper <JamesH@xxxxxxxxxxxxxxxx>]

Funnily enough, the error goes away again if I disable the 3rd network card module (natsemi). Maybe those two devices don't like sharing the same bus... i think they do share an irq.

 

bah. too confusing.

 

james

---

From: James Harper
Sent: Tue 3/08/2004 1:16 PM
To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: RE: [Xen-devel] memory error?

Further investigation reveals that i'm not the only one having this problem, and I just checked another Proliant 1600 I have running linux and it has reported that error at least once , so it appears to be a fault in the TLAN driver. doh. The TLAN driver also has another fault in it to do with promisc mode so i'll remove that driver and put another network adapter in it.

 

I'm guessing then that xen reboots the system if it gets an NMI.

 

Hopefully this ends my list of errors with xen!

 

James

---

From: James Harper
Sent: Tue 3/08/2004 11:50 AM
To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] memory error?

I have just noticed this message in my kernel logs, reporting the possibility of an error with my memory. This would go a long way towards explaining the problems i've been having. This particular error is occuring when i'm not running xen so is obviously not something brought on by xen itself.

 

The strange thing is that the NMI error is always followed by the TLAN: eth0: Adaptor Error = 0x180002, which says to me that either there is something wrong with my network card which is triggering an NMI, or that the NMI triggers an error in that network adapter. The memory itself is ECC memory in a Compaq Proliant 1600, maybe i can access the memory logs...

 

Either way, what would xen do upon receiving an NMI? Would it spontaneously reboot?

 

I'm running memtest now, and will run memtest86 once I am back in the office.

 

James

 

eth2: Promiscuous mode enabled.
eth2: Promiscuous mode enabled.
br2: port 1(eth2) entering learning state
br2: port 1(eth2) entering forwarding state
br2: topology change detected, propagating
Uhhuh. NMI received. Dazed and confused, but trying to continue
You probably have a hardware problem with your RAM chips
TLAN:  eth0: Adaptor Error = 0x180002
TLAN: eth0: Starting autonegotiation.
TLAN: eth0: Autonegotiation complete.
TLAN: eth0: Link active with AutoNegotiation enabled, at 100Mbps Full-Duplex
TLAN: Partner capability: 10BaseT-HD 10BaseT-FD 100baseTx-HD 100baseTx-FD
TLAN:  eth0: Adaptor Error = 0x180002
TLAN: eth0: Starting autonegotiation.
TLAN: eth0: Autonegotiation complete.
TLAN: eth0: Link active with AutoNegotiation enabled, at 100Mbps Full-Duplex
TLAN: Partner capability: 10BaseT-HD 10BaseT-FD 100baseTx-HD 100baseTx-FD