From owner-freebsd-current Mon Nov 29 13: 0:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id C209514BE2 for ; Mon, 29 Nov 1999 13:00:16 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id NAA00258; Mon, 29 Nov 1999 13:00:03 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.19991129125927.00a9ad70@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 29 Nov 1999 13:00:04 -0800 To: Matthew Dillon From: Manfred Antar Subject: Re: New vfs_conf.c panic Cc: Mike Smith , current@FreeBSD.ORG, Poul-Henning Kamp In-Reply-To: <199911292026.MAA08731@apollo.backplane.com> References: <4.2.2.19991129115621.00aa5d10@pozo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:26 PM 11/29/99 -0800, Matthew Dillon wrote: >: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 > Version 1.46 works fine Thanks Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message