Content-Type: text/plain; charset="iso-8859-1"
Date: Thu, 27 Nov 2008 01:19:55 +0100
From: "Carsten Menke" <bootsy52@gmx.net>
In-Reply-To: <492DE30B.4080300@shaw.ca>
Message-ID: <20081127001955.5860@gmx.net>
MIME-Version: 1.0
References: <20081126231213.271070@gmx.net> <492DE30B.4080300@shaw.ca>
Subject: Re: Panic:  NMI Watchdog detected LOCKUP on CPU
To: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1495
Lines: 26


-------- Original-Nachricht --------
> Datum: Wed, 26 Nov 2008 18:00:11 -0600
> Von: Robert Hancock <hancockr@shaw.ca>
> An: linux-kernel@vger.kernel.org
> Betreff: Re: Panic:  NMI Watchdog detected LOCKUP on CPU

> Normally server-class hardware doesn't cause these kinds of symptoms 
> from hardware problems, they usually spew NMIs, etc. but it's not 
> impossible. 2.6.15 is pretty ancient though. Can you try a newer kernel?
> 

Yes I will try that definitley, but I hoped that someone maybe knows if that was a particular problem of that
kernel (according to the panic log) version and chances are good they are fixed in later versions. The second problem is, that it can takes fairly long until I know if the problem is gone because sometimes it takes 2 months until a crash happens. So the second question is, how to prove if this is not hardware or how to prove it is definitley hardware. I have read the list and saw that NMI CPU Lockup messages can also be due to kernel bugs. 

Regards

Carsten
P.S. before the these problems happened the server was running well for a year, but I've also done the usual system upgrades
-- 
Psssst! Schon vom neuen GMX MultiMessenger geh?rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
--
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/