From owner-freebsd-current@FreeBSD.ORG Wed Nov 19 06:54:46 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 5F20116A4CE for ; Wed, 19 Nov 2003 06:54:46 -0800 (PST) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E05A4400B for ; Wed, 19 Nov 2003 06:54:45 -0800 (PST) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9p2/8.12.9) with ESMTP id hAJEqaMg007352; Wed, 19 Nov 2003 09:52:36 -0500 (EST) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)hAJEqacA007349; Wed, 19 Nov 2003 09:52:36 -0500 (EST) (envelope-from robert@fledge.watson.org) Date: Wed, 19 Nov 2003 09:52:36 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org To: "Bjoern A. Zeeb" In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: another trap 12 while in kernel mode 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: Wed, 19 Nov 2003 14:54:46 -0000 On Wed, 19 Nov 2003, Bjoern A. Zeeb wrote: > I am regularly getting those but unfortunately I neither have DDB in > that kernel nor can get a crash dump nor do I have built wie DEBUG=-g. > > Is there anything more I can do apart from rebuilding kernel with > support of all the missing debugging flags (which is in progress) ? You should still be able to turn the bad instruction pointer into at least a function name using nm on your compiled kernel. Run nm on the kernel binary, and search through it until you find the symbols just before (lower) and just after (higher) than the value listed for the instruction pointer below. That would at least tell us what function the fault is occuring in. I suspect to get anywhere useful, we'll need the full debugging results, but it's probably a useful start, and it will allow us to be sure the panics you might get after you have debugging support compiled in are the same failure mode. Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories > > I am logged in via serial console on this machine btw but I am not > sure if this is the killing criteria for this panic. According to the > log I write there had been no output for a long time before. > > > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x6c2f6e81 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc055a00a > stack pointer = 0x10:0xc9b4acac > frame pointer = 0x10:0xc9b4acac > 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 = 26 (swi8: tty:sio clock) > trap number = 12 > panic: page fault > > syncing disks, buffers remaining... 426 426 426 426 426 426 426 426 426 426 426 426 426 426 426 426 426 426 426 426 > giving up on 349 buffers > Uptime: 6h46m27s > pfs_vncache_unload(): 1 entries remaining > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > > -- > Bjoern A. Zeeb bzeeb at Zabbadoz dot NeT > 56 69 73 69 74 http://www.zabbadoz.net/ > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >