View Issue Details

IDProjectCategoryView StatusLast Update
0005781CentOS-6kernelpublic2012-06-18 04:19
Reporterclubbing80s 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Platformx64 on Hyper-VOSCentOSOS Version6.0 Final
Product Version6.0 
Target VersionFixed in Version 
Summary0005781: WARNING: CPU#1: NMI appears to be stuck (0->0)!
DescriptionWhile investigating the crash of 3 CentOS 6 servers on the same Hyper-V host , I found the following:

Total of 4 processors activated (18005.16 BogoMIPS).
Testing NMI watchdog ...
WARNING: CPU#0: NMI appears to be stuck (0->0)!
Please report this to bugzilla.kernel.org,
and attach the output of the 'dmesg' command.

WARNING: CPU#1: NMI appears to be stuck (0->0)!
Please report this to bugzilla.kernel.org,
and attach the output of the 'dmesg' command.

WARNING: CPU#2: NMI appears to be stuck (0->0)!
Please report this to bugzilla.kernel.org,
and attach the output of the 'dmesg' command.

WARNING: CPU#3: NMI appears to be stuck (0->0)!
Please report this to bugzilla.kernel.org,
and attach the output of the 'dmesg' command.
Steps To ReproduceThese errors are present on all 3 of the CentOS guest machines on Hyper-V.
Additional InformationI have attached the dmesg output for all 3 servers.
TagsNo tags attached.

Activities

clubbing80s

clubbing80s

2012-06-18 04:19

reporter  

dmesg-from-servers.zip (23,953 bytes)

Issue History

Date Modified Username Field Change
2012-06-18 04:19 clubbing80s New Issue
2012-06-18 04:19 clubbing80s File Added: dmesg-from-servers.zip