From pauls@locust.etext.org  Sun Mar 30 18:53:56 1997
Received: from locust.etext.org (locust.etext.org [206.252.8.100])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA08371
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 30 Mar 1997 18:53:56 -0800 (PST)
Received: (from pauls@localhost) by locust.etext.org (8.8.5/8.7.3) id VAA18542; Sun, 30 Mar 1997 21:53:50 -0500 (EST)
Message-Id: <199703310253.VAA18542@locust.etext.org>
Date: Sun, 30 Mar 1997 21:53:50 -0500 (EST)
From: Paul Southworth <pauls@locust.etext.org>
Reply-To: pauls@locust.etext.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: Cyrix 6x86L-P200+ crashes w/ page fault
X-Send-Pr-Version: 3.2

>Number:         3150
>Category:       kern
>Synopsis:       Cyrix 6x86L-P200+ crashes w/ page fault
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 30 19:00:01 PST 1997
>Closed-Date:    Sun Mar 22 09:09:22 PST 1998
>Last-Modified:  Sun Mar 22 09:13:15 PST 1998
>Originator:     Paul Southworth
>Release:        FreeBSD 2.2.1-RELEASE i386
>Organization:
The ETEXT Archives
>Environment:

	Cyrix 6x86L-P200+ CPU, Mustang R534E motherboard, 128Mb EDO RAM,
	3C595, Adaptec 2940UW.  CPU serial number is GAKJ3702A.

>Description:

	Error is always a variant on this (below).  Sometimes it
	reboots.  Other times it hangs after the final "page fault"
	is printed at bottom.  Other times it hangs after "syncing
	disks...".  Machine stays up for 1-3 hours before crashing.
	
	Fatal trap 12: page fault while in kernel mode
	fault virtual address   = 0x10
	fault code              = supervisor read, page not present
	instruction pointer     = 0x8:0xf01317c6
	stack pointer           = 0x10:0xf01a8c34
	frame pointer           = 0x10:0xf01a8c44
	code segment            = base 0x0, limit 0xfffff, type 0x1b
	                        = DPL0, pres 1, def32 1, gran 1
	processor eflags        = interrupt enabled, resume, IOPL=0
	current process         = idle
	interrupt mask          = net tty
	panic: page fault

>How-To-Repeat:

	Looks like any significant load on the system will cause
	the crash.  For example, starting a dump to tape, compiling
	libc from source, running glimpseindex on a 750Mb archive.
	The "current process" field of the panic information varies
	but is always something innocuous (eg, "idle" or "named", etc).

>Fix:
	
	Unknown.  Exact same configuration is currently running happily
	with an Intel P5-133 CPU, same setup except for motherboard jumper
	settings to support the P5-133.

>Release-Note:
>Audit-Trail:

From: Louis Giliberto <gilibert@cig.mot.com>
To: freebsd-gnats-submit@freebsd.org, pauls@locust.etext.org
Cc:  Subject: Re: kern/3150: Cyrix 6x86L-P200+ crashes w/ page fault
Date: Fri, 04 Apr 1997 14:00:30 -0600

 This looks very similar to a PR I submitted on 2.1.7 a few weeks
 ago.  It is PR kern/3072.  I experienced almost the same exact
 thing except with 2.1.7
 
 -Louis
 
 -- 
 Louis Giliberto
 Software Consultant at Motorola, Cellular Infrastructure Group
 gilibert@cig.mot.com, (847) 632-7945 (work), (847) 632-2867 (fax)

From: Michael Newlyn Blake <michael.blake@Sun.COM>
To: freebsd-gnats-submit@freebsd.org, gilibert@cig.mot.com
Cc: mblake@frogtown.com
Subject: Re: kern/3150: Cyrix 6x86L-P200+ crashes w/ page fault
Date: Thu, 24 Apr 1997 13:29:10 -0700

 I am having the exact same problem under 2.2.1, only more so.  This
 seems to happen even when the system isn't being placed under a
 particularly high load.  When the system doesn't crash completely, it
 can still have problems with the console locking up, not being able to
 spawn new processes, etc.  In fact, at the moment I am at work.  The
 system (fozzy.frogtown.com, 204.188.115.1) has stoped responding, but it
 is still routing packets between it's PPP interface and ethernet
 interface.
   System is an AMD 486 clone 40MHz CPU with 16MB memory.  We will be
 trying to swap out the motherboard this evening in the hopes that it
 will help some.  I think we may have even managed to collect a few crash
 dumps, but I can't verify that until I get home and reset the computer
 so I can log in to it.
   Cheers.
 ------------------------
 Michael Newlyn Blake
 ENS/MPK18 Building Support
 Michael.Blake@Eng.Sun.Com
 x83987/415-786-3987

From: Paul Southworth <pauls@etext.org>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: kern/3150 Cyrix 6x86L-P200+ crashes w/ page fault
Date: Sun, 22 Mar 1998 09:51:05 -0500 (EST)

 On Sun, 22 Mar 1998, Studded wrote:
 
 :	I am writing to you in regards to your FreeBSD Problem
 :Report. The FreeBSD project is currently conducting a beta test on
 :version 2.2.6 and feedback as to whether you are still experiencing
 :your problem would be very valuable. 
 :
 :	If you are still experiencing the problem you reported, it
 :would help the project track the problem if you could upgrade to the
 :latest snapshot of 2.2.6-Beta (located at releng22.freebsd.org) and
 :test your problem again. 
 
 The system in question is a production server and I can't toy with it.  I
 removed the Cyrix CPU and installed a P5-133 instead since I found no fix
 for the Cyrix problem. I don't have any other motherboards that will drive
 the Cyrix CPU at 200Mhz (I'm driving it like a 6x86-P166+ in a Solaris/x86
 system now). My hunch is that this may have been a cooling problem and not
 a FreeBSD bug, but it's hard to say for sure.
 
 --Paul
 
State-Changed-From-To: open->closed 
State-Changed-By: steve 
State-Changed-When: Sun Mar 22 09:09:22 PST 1998 
State-Changed-Why:  
Originator has no way to test if 2.2.6 has solved this problem 
because this is a prodcuction server.  The problem may have 
been due to insufficient cooling. 
>Unformatted:
