From nobody@FreeBSD.org  Thu Feb 21 23:51:42 2008
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 09B9916A400
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 21 Feb 2008 23:51:42 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
	by mx1.freebsd.org (Postfix) with ESMTP id EAC5613C45B
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 21 Feb 2008 23:51:41 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m1LNn7kH047716
	for <freebsd-gnats-submit@FreeBSD.org>; Thu, 21 Feb 2008 23:49:07 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.14.2/8.14.1/Submit) id m1LNn7DJ047713;
	Thu, 21 Feb 2008 23:49:07 GMT
	(envelope-from nobody)
Message-Id: <200802212349.m1LNn7DJ047713@www.freebsd.org>
Date: Thu, 21 Feb 2008 23:49:07 GMT
From: Eric Kingston <ericnk@esreco.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: FreeBSD 6.3 Release: Fatal trap 12: page fault while in kernel mode
X-Send-Pr-Version: www-3.1
X-GNATS-Notify:

>Number:         120954
>Category:       kern
>Synopsis:       [panic] FreeBSD 6.3 Release: Fatal trap 12: page fault while in kernel mode
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    vwe
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Feb 22 00:00:05 UTC 2008
>Closed-Date:    Fri Oct 17 15:35:44 UTC 2008
>Last-Modified:  Fri Oct 17 15:35:44 UTC 2008
>Originator:     Eric Kingston
>Release:        FreeBSD 6.3 Release
>Organization:
Standard Industries
>Environment:
FreeBSD ifabgate.esreco.net 6.3-RELEASE FreeBSD 6.3-RELEASE #0: Wed Jan 16 04:45:45 UTC 2008     root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP  i386
>Description:
After installing FreeBSD 6.3 Release on a Shuttle XPC SD30G2B, intel 945GC + ICH7 chipset, Intel E6400 core 2 duo 2.13 Ghz, 1066 Mhz FSB processor, I logged on the console as root and while attempting a shutdown -r now I happened upon the following Fatal Trap 12....

Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address	= 0x2c
fault code		= supervisor read, page not present
instruction pointer	= 0x20:0xc08f47e9
stack pointer		= 0x20:0xd5aeda08
frame pointer		= 0x28:0xd5aeda14
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		= 904 (getty)
trap number		= 12
panic: page fault
cpuid = 1
Uptime: 20m21s

The problem also occurs while attempting filesystem activity with a command like..   "find / -name "*.so" .

I will also add that I installed FreeBSD 6.2 Release on the same system and everything worked flawlessly, no kernel panic or trap errors at all.


>How-To-Repeat:
Install FreeBSD 6.3 Release on a Shuttle XPC SD30G2B, intel 945GC + ICH7 chipset, Intel E6400 core 2 duo 2.13 Ghz, 1066 Mhz FSB processor, 512MB DDR2, 667Mhz RAM, log in as root on the console and run "shutdown -r now".


>Fix:


>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: remko 
State-Changed-When: Fri Feb 22 20:04:42 UTC 2008 
State-Changed-Why:  
Can you give us a kern el du m p information please? 
visit http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html 
for more information. We need this to see what is going on 


Responsible-Changed-From-To: freebsd-i386->freebsd-bugs 
Responsible-Changed-By: remko 
Responsible-Changed-When: Fri Feb 22 20:04:42 UTC 2008 
Responsible-Changed-Why:  
Can you give us a kern el du m p information please? 
visit http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html 
for more information. We need this to see what is going on 

http://www.freebsd.org/cgi/query-pr.cgi?pr=120954 

From: "Eric Kingston" <ericnk@esreco.net>
To: <bug-followup@FreeBSD.org>,
	<ericnk@esreco.net>
Cc:  
Subject: Re: kern/120954: [panic] FreeBSD 6.3 Release: Fatal trap 12: page fault while in kernel mode
Date: Thu, 6 Mar 2008 13:54:02 -0700

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_001C_01C87F91.89130650
 Content-Type: text/plain;
 	charset="us-ascii"
 Content-Transfer-Encoding: 7bit
 
 It appears that the ACPI implementation for Shuttle is broken.  When I boot
 with ACPI disabled everything works fine.  It may be related to PR
 kern/120953.
 
  
 
 Eric
 
 ------=_NextPart_000_001C_01C87F91.89130650--
 
Responsible-Changed-From-To: freebsd-bugs->vwe 
Responsible-Changed-By: vwe 
Responsible-Changed-When: Sat Mar 8 23:30:29 UTC 2008 
Responsible-Changed-Why:  
grab 

http://www.freebsd.org/cgi/query-pr.cgi?pr=120954 

From: Volker <volker@vwsoft.com>
To: bug-followup@FreeBSD.org, ericnk@esreco.net
Cc:  
Subject: Re: kern/120954: [panic] FreeBSD 6.3 Release: Fatal trap 12: page
 fault while in kernel mode
Date: Sun, 09 Mar 2008 00:29:46 +0100

 Eric,
 
 it is very likely possible to have a faulty ACPI implementation having
 such impact. Also while looking at your PR kern/120953 I think your acpi
 dsdt/asl might be the cause.
 
 As already requested, please give us a kernel backtrace, which might be
 useful in any way. Most likely you'll see first signs for a bad ACPI
 code in dmesg (you haven't filed one in the PR ticket, so we even can't
 check that).
 
 First, you should check with your hardware vendor for a BIOS update. If
 they don't have one for download on their website, you should query
 tech-support and ask for an ACPI standards compliant version.
 
 If that fails at all, you should make yourself familiar with ACPI
 debugging and check if you're able to create an AML override file and
 load that in place of the original AML code provided by your mobo.
 
 Also please have a look at the ACPI dokumentation:
 http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/acpi-debug.html
 
 `man 4 acpi' (section OVERRIDING YOUR BIOS BYTECODE)
 `man 8 acpidump'
 
 If you would show us the kerneldump and a dmesg (verbose boot) we might
 make a first suggestion where to start checking your issues.
 
 If you could save output of `acpidump -dt' to a file and provide a
 download URL to that file, I'm pretty sure, someone will have a look
 what might be wrong with your AML code.
 
 Should you have figured out it's really your ACPI which is causing that,
 please don't forget to report back so we can close this ticket.
 
 Thanks!
 
 Volker
State-Changed-From-To: feedback->closed 
State-Changed-By: vwe 
State-Changed-When: Fri Oct 17 15:35:23 UTC 2008 
State-Changed-Why:  
closing this, as this is a BIOS issue. 
Thank you for reporting. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=120954 
>Unformatted:
