From owner-freebsd-current Thu Nov 6 19:54:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA06220 for current-outgoing; Thu, 6 Nov 1997 19:54:30 -0800 (PST) (envelope-from owner-freebsd-current) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA06209 for ; Thu, 6 Nov 1997 19:54:27 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 4921 invoked from network); 7 Nov 1997 03:54:18 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 7 Nov 1997 03:54:18 -0000 Received: from mordred (localhost [127.0.0.1]) by mordred.cs.ucla.edu (8.8.7/8.8.7) with ESMTP id TAA07772 for ; Thu, 6 Nov 1997 19:54:15 -0800 (PST) (envelope-from scottm@mordred.cs.ucla.edu) Message-Id: <199711070354.TAA07772@mordred.cs.ucla.edu> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-current@freebsd.org Subject: Latest kernel: panics with NFS LKM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Nov 1997 19:54:14 -0800 From: Scott Michel Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Given the latest kernel snapshot (from a cvsup this afternoon), the NFS LKM causes the kernel to panic - trap 12, page fault in kernel. Yes, I remembered to config the kernel before I rebuilt it. Configuring the kernel with NFS compiled in makes the panic go away. I doing a build world to see if there's some leftover spooge from some of the kernel source changes today. FWIW.... -scooter