From owner-freebsd-current Mon Nov 29 12:27: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 18AB915340 for ; Mon, 29 Nov 1999 12:27:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA08731; Mon, 29 Nov 1999 12:26:59 -0800 (PST) (envelope-from dillon) Date: Mon, 29 Nov 1999 12:26:59 -0800 (PST) From: Matthew Dillon Message-Id: <199911292026.MAA08731@apollo.backplane.com> To: Manfred Antar Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: New vfs_conf.c panic References: <4.2.2.19991129115621.00aa5d10@pozo.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Mike :I get a panic on current smp-kernel with the new version :of vfs_conf.c . :The system is current as of this morning :If I back out to version 1.44 it boots fine. :It seems to panic at the swapon part of the boot process. :I get : :Fatal trap 12: page fault while in kernel mode :mp_lock = 01000002; cpuid = 1; lapic.id = 0c000000 :fault virtual address = 0x2b :fault code = supervisor read, page not present Is the panic occuring with version 1.45 of vfs_conf.c or 1.46? I just committed 1.46 a moment ago along with i386/i386/autoconf.c which fixes BOOTP boots. Prior to that BOOTP boots would panic. A 'trace' would be helpful if you have DDB enabled or, if you are using BOOTP, the problem should now be fixed once the commit propogates. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message