From: "Jan Beulich" <JBeulich@novell.com>
To: <linux-kernel@vger.kernel.org>
Subject: [PATCH] prevent nested panic from soft lockup detection
Date: Mon, 30 Jan 2006 10:08:33 +0100 [thread overview]
Message-ID: <43DDE5A1.76F0.0078.0@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
From: Jan Beulich <jbeulich@novell.com>
Suppress triggering a nested panic due to soft lockup detection.
Signed-Off-By: Jan Beulich <jbeulich@novell.com>
[-- Attachment #2: linux-2.6.16-rc1-panic-softlockup.patch --]
[-- Type: text/plain, Size: 900 bytes --]
From: Jan Beulich <jbeulich@novell.com>
Suppress triggering a nested panic due to soft lockup detection.
Signed-Off-By: Jan Beulich <jbeulich@novell.com>
diff -Npru /home/jbeulich/tmp/linux-2.6.16-rc1/kernel/panic.c 2.6.16-rc1-panic-softlockup/kernel/panic.c
--- /home/jbeulich/tmp/linux-2.6.16-rc1/kernel/panic.c 2006-01-27 15:10:49.000000000 +0100
+++ 2.6.16-rc1-panic-softlockup/kernel/panic.c 2006-01-25 09:55:53.000000000 +0100
@@ -107,6 +107,7 @@ NORET_TYPE void panic(const char * fmt,
printk(KERN_EMERG "Rebooting in %d seconds..",panic_timeout);
for (i = 0; i < panic_timeout*1000; ) {
touch_nmi_watchdog();
+ touch_softlockup_watchdog();
i += panic_blink(i);
mdelay(1);
i++;
@@ -130,6 +131,7 @@ NORET_TYPE void panic(const char * fmt,
#endif
local_irq_enable();
for (i = 0;;) {
+ touch_softlockup_watchdog();
i += panic_blink(i);
mdelay(1);
i++;
next reply other threads:[~2006-01-30 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 9:08 Jan Beulich [this message]
2006-01-30 14:58 ` [PATCH] prevent nested panic from soft lockup detection Dave Jones
[not found] <43DDE5A1.76F0.0078.0@novell.com.suse.lists.linux.kernel>
[not found] ` <20060130145850.GB9752@redhat.com.suse.lists.linux.kernel>
2006-01-31 12:35 ` Andi Kleen
2006-01-31 13:46 ` Jan Beulich
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=43DDE5A1.76F0.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).