From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Andi Kleen <ak@suse.de>
Cc: bevand_m@epita.fr, linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: NMI watchdog detected lockup
Date: Mon, 18 Oct 2004 10:58:08 -0700 [thread overview]
Message-ID: <41740430.30604@osdl.org> (raw)
In-Reply-To: <20041018200017.0098710d.ak@suse.de>
Andi Kleen wrote:
> On Mon, 18 Oct 2004 10:13:11 -0700
> "Randy.Dunlap" <rddunlap@osdl.org> wrote:
>
>
>>Marc Bevand wrote:
>>
>>>On 2004-10-17, Randy.Dunlap <rddunlap@osdl.org> wrote:
>>>|
>>>| I'm seeing this often during a kernel build on AIC79xx.
>>>| I did one kernel build on SATA without seeing this.
>>>| This is on a dual-Opteron IBM Workstation A with
>>>| 2 GB RAM, SATA, & SCSI.
>>>| [...]
>>>| NMI Watchdog detected LOCKUP on CPU0, registers:
>>>| [...]
>>>
>>>You are not the first one to observe frequent watchdog timeout
>>>lockup on dual Opteron systems during intense I/O operations,
>>>see this thread:
>>>
>>> http://thread.gmane.org/gmane.linux.ide/1933
>>>
>>>Note: this does *not* seem to be SATA-related.
>>
>>Hi,
>>
>>Zwane suspected NMI spikes and advised me to disable nmi_watchdog
>>(nmi_watchdog=0). After doing that, a kernel build completes
>>successfully, although with many messages like these:
>>
>>Uhhuh. NMI received for unknown reason 21.
>
>
> 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.
--
~Randy
next prev parent reply other threads:[~2004-10-18 18:10 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 [this message]
2004-10-18 18:16 ` Andi Kleen
2004-10-18 18:37 ` Phil Oester
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=41740430.30604@osdl.org \
--to=rddunlap@osdl.org \
--cc=ak@suse.de \
--cc=bevand_m@epita.fr \
--cc=discuss@x86-64.org \
--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