Bug 497508

Summary:	testing NMI watchdog ... CPU#0: NMI appears to be stuck (16)!
Product:	Red Hat Enterprise Linux 4	Reporter:	Qian Cai <qcai>
Component:	kernel	Assignee:	Red Hat Kernel Manager <kernel-mgr>
Status:	CLOSED NOTABUG	QA Contact:	Red Hat Kernel QE team <kernel-qe>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.8
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-04-24 13:30:29 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Qian Cai 2009-04-24 11:53:36 UTC

Description of problem:
If we added nmi_watchdog=1 to the kernel, the we have seen the following messages on a RHTS HP DL580G5 server.

Total of 16 processors activated (76799.30 BogoMIPS).
activating NMI Watchdog ... done.
Using local APIC timer interrupts.
Detected 16.667 MHz APIC timer.
checking TSC synchronization across 16 CPUs: passed.
Brought up 16 CPUs
time.c: Using HPET/TSC based timekeeping.
testing NMI watchdog ... CPU#0: NMI appears to be stuck (16)!
NMI watchdog: disabling NMI delivery on LINT0 for all CPUs

Version-Release number of selected component (if applicable):
kernel-smp-2.6.9-89.EL
kernel-smp-2.6.9-78.0.21.EL

How reproducible:
always

Comment 1 Qian Cai 2009-04-24 13:30:29 UTC

aris> caiqian, not all machines work with both NMI watchdog modes
<caiqian> aris, without nmi_watchdog it works. Should I close it?
<aris> yes
<aris> x86_64 will select automatically the method