public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent GUERBY <laurent@guerby.net>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Peter Oruba <peter.oruba@amd.com>
Subject: Re: BUG: soft lockup detected on Phenom with Debian 2.6.24-4
Date: Mon, 14 Apr 2008 12:23:47 +0200	[thread overview]
Message-ID: <1208168627.15628.462.camel@localhost> (raw)
In-Reply-To: <alpine.LFD.1.10.0804131635500.3261@apollo.tec.linutronix.de>

In fact BIOS 1705 without any boot option seems
to provide a stable machine (51 hours of stress
test without failure). Plus BIOS 1705 has
an explicit TLB fix auto/enable/disable
that the previous BIOS didn't have (even
if TLB fix was on).

So probably it was probably a BIOS bug, we're continuing
the stress testing.

Laurent


On Sun, 2008-04-13 at 16:37 +0200, Thomas Gleixner wrote:
> On Sat, 12 Apr 2008, Laurent GUERBY wrote:
> > 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).
> 
> hmm, nmi_watchdog=1 disables the local apic timer. Can you add
> "noapictimer" to the kernel command line instead ?
> 
> Thanks,
> 	tglx
> 


  reply	other threads:[~2008-04-14 10:24 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
2008-04-13 14:37           ` Thomas Gleixner
2008-04-14 10:23             ` Laurent GUERBY [this message]
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=1208168627.15628.462.camel@localhost \
    --to=laurent@guerby.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.oruba@amd.com \
    --cc=tglx@linutronix.de \
    /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