Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 230094

Summary: kernel panic with nfsd
Product: Red Hat Enterprise Linux 4 Reporter: jmccann
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 4.4CC: cschalle, jeffmacdonald
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-03-12 17:41:16 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:
Attachments:
Description Flags
kern syslog output
none
panic bt
none
script that has never failed to reproduce bug on redhat 4 nfs server
none
updated test case none

Description jmccann 2007-02-26 16:26:55 UTC 
Description of problem:
Was running 2.6.9-42.0.3.ELsmp.  Used up2date to install 
kernel-smp-2.6.9-42.0.8.EL.  Rebooted into new kernel.  kernel panic at about
the time it entered init 5 (at GDM screen).  Happened after every reboot with
the new kernel.  Was able to boot sucessfully into previous (2.6.9-42.0.3.ELsmp)
kernel.

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

How reproducible:
Every time.


Additional info:
I saw this before with 2.6.9-42.0.2.ELsmp but an update to 2.6.9-42.0.3.ELsmp
seemed to fix the problem.
Comment 1 jmccann 2007-02-26 16:26:56 UTC 
Created attachment 148807 [details]
kern syslog output
Comment 2 jmccann 2007-03-07 17:40:11 UTC 
Today the same crash occurred with:
2.6.9-42.0.2.ELsmp
2.6.9-42.0.3.ELsmp
2.6.9-42.0.10.ELsmp
Comment 3 jeff 2007-03-09 12:27:42 UTC 
Created attachment 149674 [details]
panic bt
Comment 4 jeff 2007-03-09 12:31:34 UTC 
Created attachment 149676 [details]
script that has never failed to reproduce bug on redhat 4 nfs server

run from solaris 8 or 9 nfs client
Comment 5 jeff 2007-03-09 12:34:50 UTC 
This looks like same bug im hitting.
do you have solaris clients will ?
I've reproduced it on demand by
forcing solaris a nfs client to use nfsv2.
Comment 6 jmccann 2007-03-09 16:22:19 UTC 
Created attachment 149695 [details]
updated test case

Updated the test case.	For me this reproduces the panic every time.  I didn't
even need to do a write but only a listing.
Comment 7 jmccann 2007-03-09 16:27:45 UTC 
Nice job Jeff with the test case!  Yes I have Solaris 9 clients.
Bumping the severity up a bit.

Kernel dudes, any tips on what else we can do to troubleshoot this?  Thanks.
Comment 8 jeff 2007-03-09 17:16:07 UTC 
/etc/sysconfig/nfs
RPCNFSDARGS="-N 2"

disables nfsv2 and I believe works around the bug.
Dont fall for MOUNTD_NFS_V2=no it does NOT disable nfsv2.

So why are some of your solaris clients using nfsv2?

For me, my network was dropping packets (bad switch)
so Im working on the theory that this caused a  mount
request v3 to fail, so solaris fell back to nfsv2.
Does your network drop packets ?  Or some solaris clients
configured to use nfsv2 ?
Comment 9 Jason Baron 2007-03-12 17:41:16 UTC 

*** This bug has been marked as a duplicate of 191831 ***