Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 167257 - NMI watchdog lockup while attempting to rejoin cluster
NMI watchdog lockup while attempting to rejoin cluster
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
Depends On: 166701
  Show dependency treegraph
Reported: 2005-08-31 19:22 EDT by Henry Harris
Modified: 2007-11-30 17:07 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-09-19 16:51:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
KDB info from failed node including dmesg, ps,sr t, etc. (280.00 KB, text/plain)
2005-08-31 19:22 EDT, Henry Harris
no flags Details

  None (edit)
Description Henry Harris 2005-08-31 19:22:44 EDT
Description of problem: On a two node cluster, one of the nodes was removed 
from the cluster.  When it attempted to rejoin the cluster, the kernel paniced 
due to an NMI watchdog lockup.

Version-Release number of selected component (if applicable):

How reproducible:
First time this problem has been seen.

Steps to Reproduce:
1. Remove one node from two node cluster
2. Rejoin node to cluster
Actual results: Kernel panic

Expected results: Normal operation

Additional info:  This problem may be related to bug #166701 as it occurred in 
low memory and a spinlock was involved.
Comment 1 Henry Harris 2005-08-31 19:22:45 EDT
Created attachment 118323 [details]
KDB info from failed node including dmesg, ps,sr t, etc.
Comment 2 Ben Marzinski 2005-09-14 14:04:00 EDT
Let me know if this issue shows up again, while running the U2 gfs code.
Comment 3 Benjamin Kahn 2006-05-16 11:17:32 EDT
Doesn't actually block RHEL4NFSFailover

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