From: Phil Oester <kernel@linuxace.com>
To: Andi Kleen <ak@suse.de>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
bevand_m@epita.fr, linux-kernel@vger.kernel.org,
discuss@x86-64.org
Subject: Re: NMI watchdog detected lockup
Date: Mon, 18 Oct 2004 11:37:07 -0700 [thread overview]
Message-ID: <20041018183707.GA11947@linuxace.com> (raw)
In-Reply-To: <20041018201654.58905384.ak@suse.de>
On Mon, Oct 18, 2004 at 08:16:54PM +0200, Andi Kleen wrote:
> On Mon, 18 Oct 2004 10:58:08 -0700
> "Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
> > > Something on your system creates bogus NMI interrupts. What chipset
> > > are you using exactly?
> > >
> > > Sometimes chipsets can be programmed to raise NMIs when an PCI bus
> > > error occurs.
> > >
> > > 21 is the normal state (PIT timer running, but no errors logged)
> > >
> > > If you have an AMD 8131 it could be in theory erratum 54, but then
> > > normally one of the error bits in reason should be set.
> >
> > Yes, it's an AMD-8111 / 8131 / 8151 / K8-northbridge machine.
>
> It's probably one of your IO cards. I would remove them one by one
> or possibly switch them to different slots (PCI vs PCI-X)
Not sure if it's related, but I've noticed this with numerous 440gx
boxes on 2.6.8.1. I get reasons 2d and 3d. If I reboot with
nmi_watchdog=1 on these boxes, the errors go away. This was not
a problem on 2.6.3 interestingly enough...
Phil
next prev parent reply other threads:[~2004-10-18 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-17 22:58 NMI watchdog detected lockup Randy.Dunlap
2004-10-18 0:00 ` Marc Bevand
2004-10-18 17:13 ` Randy.Dunlap
2004-10-18 18:00 ` Andi Kleen
2004-10-18 17:58 ` Randy.Dunlap
2004-10-18 18:16 ` Andi Kleen
2004-10-18 18:37 ` Phil Oester [this message]
2004-10-21 4:54 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2006-12-28 9:10 NMI Watchdog detected LOCKUP Jesper Juhl
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=20041018183707.GA11947@linuxace.com \
--to=kernel@linuxace.com \
--cc=ak@suse.de \
--cc=bevand_m@epita.fr \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.