Messages in this thread | | | Date | Thu, 27 Dec 2001 17:50:45 +0100 | From | Peter Wächtler <> | Subject | Re: Kernel crash with knfsd |
| |
Neil Brown schrieb: > > On December 26, dave@rudedog.org 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 > > > 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 > > > > > The server is running 2.4.16 with XFS patches. The nfs-exported > > directories are both xfs and rieserfs. The laptop runs kernel autofs, > > 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |