From owner-freebsd-bugs@FreeBSD.ORG Sat Oct 4 22:40:06 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 BCB211065699 for ; Sat, 4 Oct 2008 22:40:06 +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 AB30C8FC12 for ; Sat, 4 Oct 2008 22:40:06 +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 m94Me6H8079212 for ; Sat, 4 Oct 2008 22:40:06 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m94Me6u7079211; Sat, 4 Oct 2008 22:40:06 GMT (envelope-from gnats) Date: Sat, 4 Oct 2008 22:40:06 GMT Message-Id: <200810042240.m94Me6u7079211@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: Sat, 04 Oct 2008 22:40:06 -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 00:38:38 +0200 This is a multi-part message in MIME format. --------------030100040509040701090805 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Wouter, please run the attached script and file a followup to the PR (leave bug-followup@ in CC). The script will rebuild the environment of your crashed kernel (load your old kernel from /boot/kernel.old and load kld's into address space), then will give us the backtrace and some code snippets of the faulting code. I've included three instruction addresses picked from your various panic messages. At least two of them are related to if_stf.ko (judged from their code addresses). Volker --------------030100040509040701090805 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 *0xc083b4ac list *0xc577373d list *0xc576e73d quit EOF kgdb /boot/kernel.old/kernel /var/crash/vmcore.3 < /tmp/vmcore.txt --------------030100040509040701090805--