Bug 497508 - testing NMI watchdog ... CPU#0: NMI appears to be stuck (16)!
testing NMI watchdog ... CPU#0: NMI appears to be stuck (16)!
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.8
All Linux
high Severity high
: rc
: ---
Assigned To: Red Hat Kernel Manager
Red Hat Kernel QE team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-04-24 07:53 EDT by CAI Qian
Modified: 2009-04-24 09:30 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-04-24 09:30:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description CAI Qian 2009-04-24 07:53:36 EDT
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 CAI Qian 2009-04-24 09:30:29 EDT
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

Note You need to log in before you can comment on or make changes to this bug.