From: Andi Kleen <ak@suse.de>
To: dwalker@mvista.com, patches@x86-64.org,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: [PATCH for 2.6.23] [3/3] i386: fix a hang on stuck nmi watchdog
Date: Thu, 6 Sep 2007 16:59:54 +0200 (CEST) [thread overview]
Message-ID: <20070906145954.1E47514EE9@wotan.suse.de> (raw)
In-Reply-To: <20070906459.839970000@suse.de>
From: Daniel Walker <dwalker@mvista.com>
In the case when an nmi gets stucks the endflag stays equal to zero. This
causes the busy looping on other cpus to continue, even tho the nmi test
is done.
On my machine with out the change below the system would hang right after
check_nmi_watchdog(). The change below just sets endflag prior to checking
if the test was successful or not.
Signed-off-by: Daniel Walker <dwalker@mvista.com>
Signed-off-by: Andi Kleen <ak@suse.de>
---
arch/i386/kernel/nmi.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux/arch/i386/kernel/nmi.c
===================================================================
--- linux.orig/arch/i386/kernel/nmi.c
+++ linux/arch/i386/kernel/nmi.c
@@ -115,12 +115,12 @@ static int __init check_nmi_watchdog(voi
atomic_dec(&nmi_active);
}
}
+ endflag = 1;
if (!atomic_read(&nmi_active)) {
kfree(prev_nmi_count);
atomic_set(&nmi_active, -1);
return -1;
}
- endflag = 1;
printk("OK.\n");
/* now that we know it works we can reduce NMI frequency to
prev parent reply other threads:[~2007-09-06 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 14:59 [PATCH for 2.6.23] [0/3] Last minute x86 bug fixes for 2.6.23 Andi Kleen
2007-09-06 14:59 ` [PATCH for 2.6.23] [1/3] i386: Fix perfctr watchdog on core duo Andi Kleen
2007-09-06 14:59 ` [PATCH for 2.6.23] [2/3] x86_64: Remove CLFLUSH in text_poke() Andi Kleen
2007-09-06 14:59 ` Andi Kleen [this message]
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=20070906145954.1E47514EE9@wotan.suse.de \
--to=ak@suse.de \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@x86-64.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®