From: Steven Rostedt <rostedt@goodmis.org>
To: Jochen Heuer <jogi-kernel@planetzork.ping.de>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
nathans@sgi.com, xfs@oss.sgi.com
Subject: Re: BUG: soft lockup detected on CPU#1!
Date: Mon, 24 Jul 2006 09:20:32 -0400 [thread overview]
Message-ID: <1153747232.4002.81.camel@localhost.localdomain> (raw)
In-Reply-To: <20060721225304.GA12184@planetzork.ping.de>
On Sat, 2006-07-22 at 00:53 +0200, Jochen Heuer wrote:
>
> Is there anything I can test? Disable irq balancing? Disabling preemption did
> not help. Disabling IO-APIC? What can I do to help isolate the problem because
> it really is annoying and I don't like pushing the reset button. Because if the
> system locks up *really* nothing works. The screen is frozen, no mouse, no
> keyboard, no sys-rq, no network ... nothing.
Jochen, have you tried to enable NMI? Make sure you have Local APIC
enabled (you should since it's SMP), and on your kernel command line (in
Grub) add "lapic nmi_watchdog=2". (lapic isn't really needed, but I
always add it so I don't forget to when working on UP machines).
Run it again, and if it locks up hard, which probably means its spinning
somewhere with interrupts disabled, the NMI will trigger and should give
you another dump of where it's locked up.
-- Steve
next prev parent reply other threads:[~2006-07-24 13:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-17 12:52 BUG: soft lockup detected on CPU#1! Jochen Heuer
2006-07-17 14:30 ` Steven Rostedt
2006-07-17 14:48 ` Jochen Heuer
2006-07-21 22:53 ` Jochen Heuer
2006-07-24 13:20 ` Steven Rostedt [this message]
2006-07-21 22:58 ` Jochen Heuer
-- strict thread matches above, loose matches on Subject: below --
2007-05-02 16:17 brendan powers
2009-02-11 7:16 raksac
2009-02-11 9:21 ` Justin Piszcz
2009-02-11 23:33 ` raksac
2009-02-11 23:36 ` Justin Piszcz
2009-02-12 9:22 ` raksac
2009-02-12 21:55 ` Dave Chinner
2009-02-12 21:59 ` raksac
2009-02-12 22:10 ` Eric Sandeen
2009-02-12 22:16 ` raksac
2009-02-13 4:56 ` Eric Sandeen
2009-02-19 8:04 ` raksac
2009-02-13 9:32 ` Michael Monnerie
2009-02-11 23:34 ` raksac
2009-02-12 21:49 ` Dave Chinner
2009-02-12 21:55 ` raksac
2009-02-11 7:57 Rakesh
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=1153747232.4002.81.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=jogi-kernel@planetzork.ping.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nathans@sgi.com \
--cc=xfs@oss.sgi.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 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.