Bug 167257

Summary: NMI watchdog lockup while attempting to rejoin cluster
Product: Red Hat Enterprise Linux 4 Reporter: Henry Harris <henry.harris>
Component: kernelAssignee: Lon Hohberger <lhh>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Cluster QE <mspqa-list>
Severity: high Docs Contact:
Priority: medium    
Version: 4.0CC: bmarzins, jbrassow, kanderso
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-19 20:51:04 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:
Bug Depends On: 166701    
Bug Blocks:    
Attachments:
Description Flags
KDB info from failed node including dmesg, ps,sr t, etc. none

Description Henry Harris 2005-08-31 23:22:44 UTC 
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
3.
  
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 23:22:45 UTC 
Created attachment 118323 [details]
KDB info from failed node including dmesg, ps,sr t, etc.
Comment 2 Ben Marzinski 2005-09-14 18:04:00 UTC 
Let me know if this issue shows up again, while running the U2 gfs code.
Comment 3 Benjamin Kahn 2006-05-16 15:17:32 UTC 
Doesn't actually block RHEL4NFSFailover