From owner-freebsd-current Mon Nov 29 12:30:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 63BAB154EE for ; Mon, 29 Nov 1999 12:30:38 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id VAA23007; Mon, 29 Nov 1999 21:29:38 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Manfred Antar Cc: Mike Smith , current@FreeBSD.ORG Subject: Re: New vfs_conf.c panic In-reply-to: Your message of "Mon, 29 Nov 1999 12:17:26 PST." <4.2.2.19991129115621.00aa5d10@pozo.com> Date: Mon, 29 Nov 1999 21:29:38 +0100 Message-ID: <23005.943907378@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Manfred, Could you send the 10 lines surrounding the address 0xc014a79a from the output of "nm -n /this_kernel" ? In message <4.2.2.19991129115621.00aa5d10@pozo.com>, Manfred Antar writes: >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 >instruction pointer = 0x8:0xc014a79a >stack pointer = 0x10:0xc0311f34 >frame pointer = 0x10:0xc0311f34 >code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 >processor eflags = interrupt enabled, resume, IOPL = 0 >current process = 0 (swapper) >interrupt mask = none <- SMP: XXX >trap number = 12 >panic: page fault >mp_lock = 01000002; cpuid = 1; lapic.id = 0c000000 >boot() callled on cpu#1 > >syncing disks ...... >===================== >|| 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 > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message