Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 30 Mar 1997 21:53:50 -0500 (EST)
From:      Paul Southworth <pauls@locust.etext.org>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   kern/3150: Cyrix 6x86L-P200+ crashes w/ page fault
Message-ID:  <199703310253.VAA18542@locust.etext.org>
Resent-Message-ID: <199703310300.TAA08672@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         3150
>Category:       kern
>Synopsis:       Cyrix 6x86L-P200+ crashes w/ page fault
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          support
>Submitter-Id:   current-users
>Arrival-Date:   Sun Mar 30 19:00:01 PST 1997
>Last-Modified:
>Originator:     Paul Southworth
>Organization:
The ETEXT Archives
>Release:        FreeBSD 2.2.1-RELEASE i386
>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.

>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703310253.VAA18542>