From dean@odyssey.apana.org.au  Sat Oct 12 08:19:44 2002
Return-Path: <dean@odyssey.apana.org.au>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6423237B401
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 12 Oct 2002 08:19:44 -0700 (PDT)
Received: from odyssey.apana.org.au (odyssey.apana.org.au [203.11.114.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D32B043EAF
	for <FreeBSD-gnats-submit@freebsd.org>; Sat, 12 Oct 2002 08:19:42 -0700 (PDT)
	(envelope-from dean@odyssey.apana.org.au)
Received: (from dean@localhost)
	by odyssey.apana.org.au (8.9.3/8.9.3) id XAA37128;
	Sat, 12 Oct 2002 23:19:41 +0800 (WST)
Message-Id: <200210121519.XAA37128@mail.wa.apana.org.au>
Date: Sat, 12 Oct 2002 23:19:41 +0800 (WST)
From: Dean Hollister <dean@odyssey.apana.org.au>
Reply-To: Dean Hollister <dean@odyssey.apana.org.au>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: Kernel Panics in 4.7-STABLE with 486 CPUs
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         43978
>Category:       i386
>Synopsis:       Kernel Panics in 4.7-STABLE with 486 CPUs
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Oct 12 08:20:01 PDT 2002
>Closed-Date:    Sun Jul 13 00:51:17 PDT 2003
>Last-Modified:  Sun Jul 13 00:51:17 PDT 2003
>Originator:     Dean Hollister
>Release:        FreeBSD 4.7-STABLE i386
>Organization:
Australian Public Access Network Association Inc
>Environment:
System: FreeBSD odyssey.apana.org.au 4.7-STABLE FreeBSD 4.7-STABLE #0: Sat Oct 12 12:02:04 WST 2002 root@odyssey.apana.org.au:/usr/src/sys/compile/ODYSSEY i386
>Description:
Booting a 4.7-STABLE kernel within a 486 CPU generates the following 
kernel panics:

486DX4-100, 20MB RAM:

Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x0
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc02247a4
stack pointer		= 0x10:0xc02fef1c
frame pointer		= 0x10:0xc02fef24
code segment		= base 0x0, limit 0xffffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 0 (swapper)
interrupt mask		= net tty bio cam
trap number		= 12
panic: page fault

486DX-120, 50MB RAM:

Fatal trap 12: page fault while in kernel mode
fault virtual address	= 0x0
fault code		= supervisor read, page not present
instruction pointer	= 0x8:0xc0227ee4
stack pointer		= 0x10:0xc0302f1c
frame pointer		= 0x10:0xc0302f24
code segment		= base 0x0, limit 0xffffff, type 0x1b
			= DPL 0, pres 1, def32 1, gran 1
processor eflags	= interrupt enabled, resume, IOPL = 0
current process		= 0 (swapper)
interrupt mask		= net tty bio cam
trap number		= 12
panic: page fault

These kernel panics even ocurr if the GENERIC kernel is compiled and 
booted.

This fault/bug has been commented on the STABLE mailing list and is 
suspected to be related to recent vm changes.
>How-To-Repeat:
cd /usr/src/sys/i386/conf
config GENERIC
cd ../../compile/GENERIC
make depend
make
make install
reboot
[kernel panic ocurrs before any devices are probed]
>Fix:

>Release-Note:
>Audit-Trail:

From: =?KOI8-R?Q?=F7=CC=C1=C4=C9=CD=C9=D2=CF=D7_=ED=C9=C8=C1=C9=CC?= <vladimirow@mail.ru>
To: freebsd-gnats-submit@FreeBSD.org, dean@odyssey.apana.org.au
Cc:  
Subject: Re: i386/43978: Kernel Panics in 4.7-STABLE with 486 CPUs
Date: Sun, 13 Oct 2002 14:52:15 +0400

 Very similar problem on AMD Athlon-800 128Mb RAM
 

From: zoonie <zoonie@zilch.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc: dean@odyssey.apana.org.au
Subject: Re: i386/43978: Kernel Panics in 4.7-STABLE with 486 CPUs
Date: Mon, 14 Oct 2002 10:02:12 -0400 (EDT)

 having the same problem on an intel P4, 768MB RAM
 
 

From: Dean Hollister <dean@odyssey.apana.org.au>
To: zoonie <zoonie@zilch.org>
Cc: freebsd-gnats-submit@FreeBSD.org, dean@odyssey.apana.org.au
Subject: Re: i386/43978: Kernel Panics in 4.7-STABLE with 486 CPUs
Date: Mon, 14 Oct 2002 22:08:25 +0800 (WST)

 Quoting zoonie <zoonie@zilch.org>:
 
 > having the same problem on an intel P4, 768MB RAM
 
 As I discovered, wind your system back to 4.7-RELEASE (RELENG_4_7) seems to be 
 the temporary workaround. Unless a fix for this has been committed and I 
 haven't noticed due to not reading emails often enough. :-)
 
 Regards,
 
 d.
State-Changed-From-To: open->feedback 
State-Changed-By: kris 
State-Changed-When: Sun Jul 13 00:09:28 PDT 2003 
State-Changed-Why:  
This sounds like a bug was temporarily introduced into 4.7-STABLE. 
Chances are it was fixed soon thereafter - does the problem persist 
with 4.8-RELEASE? 

http://www.freebsd.org/cgi/query-pr.cgi?pr=43978 
State-Changed-From-To: feedback->closed 
State-Changed-By: kris 
State-Changed-When: Sun Jul 13 00:51:01 PDT 2003 
State-Changed-Why:  
Submitter reports problem is resolved. 

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