WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] memory error?

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] memory error?
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 03 Aug 2004 09:15:32 +0100
Cc: James Harper <JamesH@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 03 Aug 2004 09:17:27 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 03 Aug 2004 07:42:55 BST." <E1Brt0k-0002Sq-00@xxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > 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?
> 
> Hmm, given that it's not something we've ever been able to test,
> 'spontaneous reboot' sounds quite possible...

Just tested it and, yes, the NMI error path was broken. I've checked
in a fix now, but this would explain the hangs that you were seeing.

 -- Keir


-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

<Prev in Thread] Current Thread [Next in Thread>