public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Carsten Menke" <bootsy52@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Panic:  NMI Watchdog detected LOCKUP on CPU
Date: Thu, 27 Nov 2008 01:19:55 +0100	[thread overview]
Message-ID: <20081127001955.5860@gmx.net> (raw)
In-Reply-To: <492DE30B.4080300@shaw.ca>


-------- 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

      reply	other threads:[~2008-11-27  0:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 23:12 Panic: NMI Watchdog detected LOCKUP on CPU Carsten Menke
2008-11-27  0:00 ` Robert Hancock
2008-11-27  0:19   ` Carsten Menke [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20081127001955.5860@gmx.net \
    --to=bootsy52@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox