From: Laurent GUERBY <laurent@guerby.net>
To: linux-kernel@vger.kernel.org
Cc: Peter Oruba <peter.oruba@amd.com>
Subject: Re: BUG: soft lockup detected on Phenom with Debian 2.6.24-4
Date: Sat, 12 Apr 2008 09:28:24 +0200 [thread overview]
Message-ID: <1207985304.15628.415.camel@localhost> (raw)
In-Reply-To: <1206123836.15075.699.camel@localhost>
Hi,
FYI with Peter off-list help we found a way to make the ASUS M2A-VM with
1604 BIOS stable under my stress test: we just needed nmi_watchdog=1 in
the kernel boot options (no other boot option necessary).
With nmi_watchdog=1 we see in kern.log "APIC error" but
the machine stayed stable during 3 days of stress testing:
...
Apr 7 22:41:43 gcc04 kernel: APIC error on CPU2: 00(40)
Apr 7 22:41:43 gcc04 kernel: APIC error on CPU1: 00(40)
Apr 7 22:41:43 gcc04 kernel: APIC error on CPU3: 00(40)
Apr 7 22:41:43 gcc04 kernel: APIC error on CPU0: 00(40)
Apr 7 22:53:01 gcc04 kernel: APIC error on CPU3: 40(40)
Apr 7 22:53:01 gcc04 kernel: APIC error on CPU0: 40(40)
Apr 7 22:53:01 gcc04 kernel: APIC error on CPU1: 40(40)
...
guerby@gcc04:~$ cat /proc/cmdline
root=/dev/sda1 ro nmi_watchdog=1
We are now stress testing the 1705 BIOS version which was released by
ASUS on 20080331, with and without nmi_watchdog=1. Then we'll go
back to testing the ASUS M3A32-MVP Deluxe/WiFi-AP with the newer 1002
BIOS also released on 20080331.
Note: for msr decoding xxd should be used since hexdump doesn't work:
xxd -s 0xc0010015 -l 8 /dev/cpu/0/msr
So people having stability problems with Phenom 9x00 with Linux should
try nmi_watchdog=1 as boot option.
Sincerely,
Laurent
next prev parent reply other threads:[~2008-04-12 7:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-08 22:00 BUG: soft lockup detected on Phenom with Debian 2.6.24-4 Laurent GUERBY
2008-03-16 14:43 ` Laurent GUERBY
2008-03-20 12:20 ` Laurent GUERBY
2008-03-20 13:45 ` Peter Oruba
2008-03-21 18:23 ` Laurent GUERBY
2008-04-12 7:28 ` Laurent GUERBY [this message]
2008-04-13 14:37 ` Thomas Gleixner
2008-04-14 10:23 ` Laurent GUERBY
2008-04-03 1:04 ` Schmielau, Tim
2008-04-02 19:15 ` Tim Schmielau
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=1207985304.15628.415.camel@localhost \
--to=laurent@guerby.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.oruba@amd.com \
/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;
as well as URLs for NNTP newsgroup(s).