Date: Fri, 11 Feb 2000 18:03:16 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: "David E. Cross" <crossd@cs.rpi.edu> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: hard lock under 3.4-STABLE Message-ID: <200002120203.SAA85496@apollo.backplane.com> References: <200002120016.TAA82907@cs.rpi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
:I am seeing a situation where a 3.4 system hard-locks while running 3.4
:(hard lock being that it does not respond to its serial console, nor is
:it pingable). I believe (perhaps) that it may be NFS related, with a
:program running on an NFS client when the executable itself is deleted
:from the server (although I haven't seen that style of panic in quite
:some time, and it is usually has a couple of lines earlier in the output
:to the effect that it lost its backing store.
:
:I realize that information is sparse in this, but that is because the
:information that I have is equally sparse... I have no kernel messages,
:I cannot drop into the kernel debugger, and no crashdump is ever created
:(I need to hit the reset button to recover.)
:
:I am trying to reproduce a test case, but it is difficult not knowing what
:has caused the problems in the first place.
:
:--
:David Cross | email: crossd@cs.rpi.edu
:Acting Lab Director | NYSLP: FREEBSD
I presume its the client that is locking up? If you remove the
server binary and the client takes a page fault on the binary,
and does not have the page in the cache, what is supposed to happen
is that the program is supposed to seg fault when the NFS read fails.
It's quite possible that there is a bug in dealing with this situation
and if you can get it repeatable we can probably fix it fairly easily.
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200002120203.SAA85496>