From owner-freebsd-current@FreeBSD.ORG Sat Apr 19 12:03:00 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7DD337B401 for ; Sat, 19 Apr 2003 12:03:00 -0700 (PDT) Received: from bluejay.mail.pas.earthlink.net (bluejay.mail.pas.earthlink.net [207.217.120.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1001143FA3 for ; Sat, 19 Apr 2003 12:03:00 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0234.cvx22-bradley.dialup.earthlink.net ([209.179.198.234] helo=mindspring.com) by bluejay.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 196xby-0006iE-00; Sat, 19 Apr 2003 12:02:55 -0700 Message-ID: <3EA19D10.20257A13@mindspring.com> Date: Sat, 19 Apr 2003 12:01:36 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Bruce Cran References: <20030419081519.GA495@fourtytwo.brucec.backnet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4732d032f43f88947d9756c1d7593be67a8438e0f32a48e08350badd9bab72f9c350badd9bab72f9c cc: current@freebsd.org Subject: Re: panic after unloading nfsserver module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 Apr 2003 19:03:00 -0000 Bruce Cran wrote: > I've just been trying to get NFS exports working between a -current box > and 4.7-release computer. Even when following the intructions in the > handbook but running rpcbind instead of portmap, I always get a message > 'RPCPROG_MNT: nfs timeout' on the server. While trying to fix it and > restart nfs, I unloaded the nfsserver module. The next command appears > to always crash the computer, with the following: > > panic: blockable sleep lock (sleep mutex) Giant @ > /usr/src/sys/vm/vm_fault.c:206 You probably forgot to stop the daemons before you unloaded the module. This includes both the "standard" ones, and the lock daemons. > Are there known issues with NFS on -current? Yes. Not this one, though. -- Terry