[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080815123610.GU7154@redhat.com>
Date: Fri, 15 Aug 2008 08:36:14 -0400
From: Aristeu Rozanski <arozansk@...hat.com>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org, jvillalo@...hat.com
Subject: [PATCH] NMI: fix watchdog failure message
> it just won't work at boot time - the second logic unit will be stuck:
>
> Booting processor 1/2 APIC 0x1
> Initializing CPU#1
> Calibrating delay using timer specific routine.. 5586.12 BogoMIPS (lpj=2793063)
> CPU: Trace cache: 12K uops, L1 D cache: 16K
> CPU: L2 cache: 1024K
> CPU: Physical Processor ID: 0
> CPU: Processor Core ID: 1
> CPU1: Thermal monitoring enabled (TM1)
> Intel(R) Pentium(R) D CPU 2.80GHz stepping 04
> Brought up 2 CPUs
> testing NMI watchdog ... <4>WARNING: CPU#1: NMI appears to be stuck (0->0)!
while at it...
Signed-off-by: Aristeu Rozanski <aris@...hat.com>
---
arch/x86/kernel/nmi.c | 4 ++++
1 file changed, 4 insertions(+)
--- linus-2.6.orig/arch/x86/kernel/nmi.c 2008-08-12 11:13:35.000000000 -0400
+++ linus-2.6/arch/x86/kernel/nmi.c 2008-08-15 08:33:57.000000000 -0400
@@ -142,11 +142,15 @@ int __init check_nmi_watchdog(void)
if (!per_cpu(wd_enabled, cpu))
continue;
if (get_nmi_count(cpu) - prev_nmi_count[cpu] <= 5) {
+ printk("\n");
printk(KERN_WARNING "WARNING: CPU#%d: NMI "
"appears to be stuck (%d->%d)!\n",
cpu,
prev_nmi_count[cpu],
get_nmi_count(cpu));
+ printk(KERN_WARNING "Please report this to "
+ "linux-kernel@...r.kernel.org and attach "
+ "the output of 'dmesg' command.\n");
per_cpu(wd_enabled, cpu) = 0;
atomic_dec(&nmi_active);
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists