Skip to contentSkip to conversation

Kernel crash with knfsd

DISCUSSION Dave Carrigan 3 participants 3 messages Dec 26, 2001 – Dec 27, 2001

lore
Share & tools
lore
#0 lore raw

(I am not subscribed, so please CC any response to me)

I am having the following problem:

Sometimes, when my wife's laptop comes out of suspend mode, it causes my nfs server to lock up hard -- I have to hit the reset button. Even after I reset the server, it will just lock up again a few seconds after knfsd starts, as long as the laptop is still on the net. If I suspend the laptop, then start the server, it will start fine, and I can usually unsuspend the laptop after that without problems. Up until yesterday, there was never anything in the logs.

Yesterday, after the laptop unsuspended, the nfs service died. This time however, the server itself didn't lock up, and this was in the kernel log:

 Dec 25 14:51:35 pern kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
 Dec 25 14:51:35 pern kernel:  printing eip:
 Dec 25 14:51:35 pern kernel: 00000000
 Dec 25 14:51:35 pern kernel: *pde = 00000000
 Dec 25 14:51:35 pern kernel: Oops: 0000
 Dec 25 14:51:35 pern kernel: CPU:    0
 Dec 25 14:51:35 pern kernel: EIP:    0010:[<00000000>]    Tainted: P 
 Dec 25 14:51:35 pern kernel: EFLAGS: 00010286
 Dec 25 14:51:35 pern kernel: eax: 00000000   ebx: cf3aad20   ecx: cf3aa8fc   edx: c033c800
 Dec 25 14:51:35 pern kernel: esi: cf3aa8a0   edi: cf3aad20   ebp: 11270000   esp: cc753e90
 Dec 25 14:51:35 pern kernel: ds: 0018   es: 0018   ss: 0018
 Dec 25 14:51:35 pern kernel: Process nfsd (pid: 668, stackpage=cc753000)
 Dec 25 14:51:35 pern kernel: Stack: c016c820 ccc61820 cf3aa8a0 cfcc05f0 cf3aad20 c016cc96 cf3aad20 cc796404 
 Dec 25 14:51:35 pern kernel:        00000002 cc647000 11270000 cfcc05f0 cf3aad20 c016cf98 cfcc0400 cc796414 
 Dec 25 14:51:35 pern kernel:        00000002 00000001 00000001 cc796404 cc796690 cc796404 0000000e c0113c4a 
 Dec 25 14:51:35 pern kernel: Call Trace: [nfsd_findparent+52/256] [find_fh_dentry+558/820] [fh_verify+508/988] [reschedule_idle+98/540] [nfsd_lookup+114/1016] 
 Dec 25 14:51:35 pern kernel:    [nfsd3_proc_lookup+212/224] [nfsd_dispatch+211/416] [svc_process+653/1240] [nfsd+503/808] [kernel_thread+40/56] 
 Dec 25 14:51:35 pern kernel: 
 Dec 25 14:51:35 pern kernel: Code:  Bad EIP value.

I couldn't restart nfsd and had to reboot the server, and of course it locked up hard during reboot, and I had to suspend the laptop before I could bring the server up.

The server is running 2.4.16 with XFS patches. The nfs-exported directories are both xfs and rieserfs. The laptop runs kernel autofs, and probably would have both of the server's xfs and reiserfs filesystems mounted at suspend time, because Nautilus tends to keep some filesystems permanently mounted.

The laptop is also running 2.4.16. Both systems are using the tulip.o driver from 2.4.14, but the same problem was occurring when I had the 2.4.16 tulip driver on each system.

I'm fairly certain that I saw this problem with 2.4.14 on the server as well, but I don't recall for sure. The laptop's only been running linux for a couple of weeks, so I can't say if this affected any older kernels.

I will be happy to provide more information or do any special troubleshooting for anyone who wants it.

Signature · 4 lines
Dave Carrigan ([email protected])            | Yow! Just imagine you're
UNIX-Apache-Perl-Linux-Firewalls-LDAP-C-DNS | entering a state-of-the-art CAR
Seattle, WA, USA                            | WASH!!
http://www.rudedog.org/                     | 
#1 lore raw
Quoted 5 lines

The server is running 2.4.16 with XFS patches. The nfs-exported directories are both xfs and rieserfs. The laptop runs kernel autofs, and probably would have both of the server's xfs and reiserfs filesystems mounted at suspend time, because Nautilus tends to keep some filesystems permanently mounted.

Can you duplicate the problem with a base kernel not an XFS hacked one ? Thats important info to know whether its an XFS patch bug or a core kernel bug you are somehow tripping

#2 lore raw
In reply to Dave Carrigan
Quoted 27 lines · Neil Brown
Quoted 11 lines · On December 26, [email protected] wrote:

(I am not subscribed, so please CC any response to me)

I am having the following problem:

Sometimes, when my wife's laptop comes out of suspend mode, it causes my nfs server to lock up hard -- I have to hit the reset button. Even after I reset the server, it will just lock up again a few seconds after knfsd starts, as long as the laptop is still on the net. If I suspend the laptop, then start the server, it will start fine, and I can usually unsuspend the laptop after that without problems. Up until yesterday, there was never anything in the logs.

snip

Quoted 4 lines
 Dec 25 14:51:35 pern kernel: Call Trace: [nfsd_findparent+52/256] [find_fh_dentry+558/820] [fh_verify+508/988] [reschedule_idle+98/540] [nfsd_lookup+114/1016]
 Dec 25 14:51:35 pern kernel:    [nfsd3_proc_lookup+212/224] [nfsd_dispatch+211/416] [svc_process+653/1240] [nfsd+503/808] [kernel_thread+40/56]
 Dec 25 14:51:35 pern kernel:
 Dec 25 14:51:35 pern kernel: Code:  Bad EIP value.

snip

Quoted 3 lines

The server is running 2.4.16 with XFS patches. The nfs-exported directories are both xfs and rieserfs. The laptop runs kernel autofs,

Quoted 7 lines

I have had several reports of XFS triggering an oops early in nfsd_findparent. I thought that the problem has been fixed by 2.4.16....

Can you send me a copy of nfsd_findparent out of fs/nfsd/nfsfh.c in the source tree that you are using?

There was a fix in 2.4.3 for lookup("..") failing.

This oops seems to me the one I am waiting to happen again for 4 weeks now :-(

The i_node->op->something is NULL, I guess.