All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Ed Tomlinson <edt@aei.ca>, Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.30-rc1 - nmi_watchdog broken?
Date: Tue, 14 Apr 2009 10:42:32 +0200	[thread overview]
Message-ID: <20090414084232.GG27003@elte.hu> (raw)
In-Reply-To: <200904140000.30155.edt@aei.ca>


* Ed Tomlinson <edt@aei.ca> wrote:

> Hi,
> 
> I've been having fun finding bugs in 30-rc1.  One of them is a 
> hard freeze.  I've not seen this type of problem on this hardware 
> before 30-rc1 - so I doubt if its hardware.  The best way I know 
> to debug a hard hang is with the nmi_watchdog.  I just cannot get 
> it to work.

[ Btw., have you tried CONFIG_PROVE_LOCKING=y - does it produce
  anything before or at the hard lockup point? ]

> The system is a 3 core amd cpu on a 790gx chipset.
> 
> If I boot the nmi_watchdog=1 it complains that lapci is not 
> available and the boot stops.  Same problem if I change the 
> clocksource to tsc, If I disable highres timers it panics.  If I 
> use nmi_watchdog=2 it panics. Am I doing something wrong or have I 
> hit a bug?
> 
> Logs of boots with and without highres timers inlined below.

hm, nmi_watchdog=1 acting funny is not unheard of. But 
nmi_watchdog=2 should really work. How does it panic, do
you have a capture of that?

	Ingo

  reply	other threads:[~2009-04-14  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-14  4:00 2.6.30-rc1 - nmi_watchdog broken? Ed Tomlinson
2009-04-14  8:42 ` Ingo Molnar [this message]
2009-04-14 12:29   ` Ed Tomlinson
2009-04-14 13:23     ` Ingo Molnar

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=20090414084232.GG27003@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=edt@aei.ca \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.