From owner-freebsd-current@FreeBSD.ORG Sat Apr 19 01:15:40 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 3248437B401 for ; Sat, 19 Apr 2003 01:15:40 -0700 (PDT) Received: from grassmarket.ucs.ed.ac.uk (grassmarket.ucs.ed.ac.uk [129.215.166.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id D792F43FBF for ; Sat, 19 Apr 2003 01:15:23 -0700 (PDT) (envelope-from s9905155@sms.ed.ac.uk) Received: from fourtytwo.brucec.backnet (12266209.resnet.ed.ac.uk [10.6.0.100] (may be forged))h3J8FL606936 for ; Sat, 19 Apr 2003 09:15:21 +0100 (BST) Received: from fourtytwo.brucec.backnet (localhost.fourtytwo.brucec.backnet [127.0.0.1])h3J8FJKA000578 for ; Sat, 19 Apr 2003 09:15:19 +0100 (BST) (envelope-from bruce@fourtytwo.brucec.backnet) Received: (from bruce@localhost) by fourtytwo.brucec.backnet (8.12.9/8.12.9/Submit) id h3J8FJqd000577 for current@freebsd.org; Sat, 19 Apr 2003 09:15:19 +0100 (BST) Date: Sat, 19 Apr 2003 09:15:19 +0100 From: Bruce Cran To: current@freebsd.org Message-ID: <20030419081519.GA495@fourtytwo.brucec.backnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i Subject: 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 08:15:40 -0000 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 a backtrace gives the following: panic witness_lock _mtx_lock_flags vm_fault trap_pfault trap calltrap --- trap 0xc, eip = 0xc01db4f8, ebp = 0xd7c478a8 --- strlcpy kill_kinfo_proc sysctl_kern_proc sysctl_root userland_sysctl __syscall syscall Xint0x80_syscall --- syscall (202, FreeBSD ELF32, __syscall), eip = 0x804fc67, esp = 0xfbffee7c, ebp = 0xbfbfeea8 --- I cvsupped and rebuilt the world a couple of weeks ago, and it's a Athlon-XP system I'm using. Are there known issues with NFS on -current? -- Bruce Cran