public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Carrigan <dave@rudedog.org>
To: linux-kernel@vger.kernel.org
Subject: Kernel crash with knfsd
Date: 26 Dec 2001 09:35:38 -0800	[thread overview]
Message-ID: <87heqdanpx.fsf@pdaverticals.com> (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.

-- 
Dave Carrigan (dave@rudedog.org)            | 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/                     | 

             reply	other threads:[~2001-12-26 17:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-26 17:35 Dave Carrigan [this message]
2001-12-26 18:52 ` Kernel crash with knfsd Alan Cox
2001-12-26 20:19 ` Neil Brown
2001-12-27 16:50   ` Peter Wächtler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87heqdanpx.fsf@pdaverticals.com \
    --to=dave@rudedog.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox