public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Schafer <gschafer@zip.com.au>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	"James Puthukattukaran" <James.Puthukattukaran@Sun.COM>,
	"Michael Obster" <lkm@obster.org>,
	"S.Ça??lar Onur" <caglar@pardus.org.tr>
Subject: Re: 2.6.18 Nasty Lockup
Date: Wed, 27 Sep 2006 08:02:45 +1000	[thread overview]
Message-ID: <20060926220245.GA7883@tigers.local> (raw)
In-Reply-To: <1159301752.17071.0.camel@localhost>

[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]

On Tue, Sep 26, 2006 at 01:15:51PM -0700, john stultz wrote:
> On Tue, 2006-09-26 at 22:36 +1000, Greg Schafer wrote:
> > This is a _hard_ lockup. No oops, no magic sysrq, no nuthin, just a
> > completely dead machine with only option the reset button. Usually happens
> > within a couple of minutes of desktop use but is 100% reproducible. Problem
> > is still there in a fresh checkout of current Linus git tree (post 2.6.18).
> > 
> > Dual Athlon-MP 2200's on a Tyan S2466 Tiger MPX. Config attached.
> > 
> > I used git-bisect and arrived at the apparent culprit below. Anything else I
> > should do to gather more info?
> 
> Quick test: Does enabling CONFIG_ACPI change the behavior?

Yes. It doesn't lockup now, at least it hasn't yet. Should I always
configure with CONFIG_ACPI? I've usually avoided it.


On Tue, Sep 26, 2006 at 11:18:02AM -0700, john stultz wrote:
> Thanks for narrowing this down. Could you send me full dmesg output?

Sure, attached (non CONFIG_ACPI case).


On Tue, Sep 26, 2006 at 01:20:54PM -0400, James Puthukattukaran wrote:
> Did you try asserting an NMI via "nmi_watchdog" kernel boot argument?

I gave it a try on your advice (added nmi_watchdog=1 to boot args). No dice
I'm afraid (no oops data). But I did notice in the dmesg output something
possibly strange:

Testing NMI watchdog ... CPU#0: NMI appears to be stuck (0->0)!


On Tue, Sep 26, 2006 at 03:56:46PM +0200, Michael Obster wrote:
> what do you mean with desktop use? X11-System? Then please add also your
> used grafic card and the X11 driver. I see this behaviour with lots of
> binary only driver like from NVIDIA or ATI (perhaps they have problems
> with the new 2.6.18 kernel).

No binary-only drivers here. Matrox card. In fact, the lockup sometimes
happens before X is even loaded (I suspect ntpdate in my bootscripts).


Regards
Greg

[-- Attachment #2: dmesg.out.gz --]
[-- Type: application/x-gunzip, Size: 3579 bytes --]

  reply	other threads:[~2006-09-26 22:02 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 12:36 2.6.18 Nasty Lockup Greg Schafer
2006-09-26 13:56 ` Michael Obster
2006-09-26 15:41 ` Ben Duncan
2006-09-26 18:18 ` john stultz
2006-09-26 20:15 ` john stultz
2006-09-26 22:02   ` Greg Schafer [this message]
2006-09-26 22:58     ` john stultz
2006-09-26 21:15 ` S.Çağlar Onur
2006-09-26 22:50   ` john stultz
2006-09-27  9:45     ` S.Çağlar Onur
2006-09-27 19:14       ` john stultz
2006-09-27 20:55         ` Andi Kleen
2006-09-27 21:06           ` S.Çağlar Onur
2006-09-28 11:39         ` S.Çağlar Onur
2006-09-29  8:49           ` S.Çağlar Onur
2006-10-06 22:57             ` john stultz
2006-10-07 15:48               ` S.Çağlar Onur

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=20060926220245.GA7883@tigers.local \
    --to=gschafer@zip.com.au \
    --cc=James.Puthukattukaran@Sun.COM \
    --cc=caglar@pardus.org.tr \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkm@obster.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