From owner-freebsd-bugs@FreeBSD.ORG Sun Oct 5 14:00:10 2008 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE2071065695 for ; Sun, 5 Oct 2008 14:00:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CBC768FC14 for ; Sun, 5 Oct 2008 14:00:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m95E0Aod094114 for ; Sun, 5 Oct 2008 14:00:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m95E0AOp094113; Sun, 5 Oct 2008 14:00:10 GMT (envelope-from gnats) Date: Sun, 5 Oct 2008 14:00:10 GMT Message-Id: <200810051400.m95E0AOp094113@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Volker Werth Cc: Subject: Re: kern/127699: [panic] Fatal trap 12: page fault while in kernel mode X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Volker Werth List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2008 14:00:11 -0000 The following reply was made to PR kern/127699; it has been noted by GNATS. From: Volker Werth To: Wouter Snels Cc: bug-followup@freebsd.org Subject: Re: kern/127699: [panic] Fatal trap 12: page fault while in kernel mode Date: Sun, 05 Oct 2008 15:57:21 +0200 This is a multi-part message in MIME format. --------------020602030903030602040709 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 10/05/08 01:18, Wouter Snels wrote: > I ran ./vmcore.sh >/tmp/vmcore.log 2>&1 because it seems like there was > a lot of data which was still send to stdout and stderr, .. incase you > needed it, it should be in vmcore.log Wouter, you may also use the script(1) command which automatically stores stdout and stderr into a text output file. But redirecting stderr is also fine. I think we've gathered a lot of debugging info but we need to make one last step to find the cause of the panic. Can you please run the attached script and file the outcome to the PR? It will give us the values of some variables and I'm pretty sure a net maintainer will find what's causing your panic and can produce a fix for it. As soon as we've got the additional debugging information, I'll forward your PR to the appropriate maintainer(s). Thank you for your effort - I know it's been a pain for you to give me all the requested information, but we need that for analysis. Volker --------------020602030903030602040709 Content-Type: text/plain; name="vmcore.sh" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="vmcore.sh" #!/bin/sh +x # automated inspection of vmcore.3, PR kern/127699 cat << EOF | asf -s /boot/kernel.old /tmp/vmcore.txt 1 4 0xc0400000 91d344 kernel 2 1 0xc0d1e000 6a32c acpi.ko 3 1 0xc5772000 3000 if_stf.ko EOF cat << EOF >> /tmp/vmcore.txt bt list *0xc577373d fr 7 p sc p *sc p dst4 p *dst4 quit EOF kgdb -q /boot/kernel.old/kernel /var/crash/vmcore.3 < /tmp/vmcore.txt --------------020602030903030602040709--