From owner-freebsd-hardware  Sun Mar 30 18:30:06 1997
Return-Path: <owner-hardware>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id SAA06764
          for hardware-outgoing; Sun, 30 Mar 1997 18:30:06 -0800 (PST)
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 SAA06664
          for <freebsd-hardware@freebsd.org>; Sun, 30 Mar 1997 18:29:11 -0800 (PST)
Received: from localhost (pauls@localhost) by locust.etext.org (8.8.5/8.7.3) with SMTP id VAA18093 for <freebsd-hardware@freebsd.org>; Sun, 30 Mar 1997 21:29:18 -0500 (EST)
Date: Sun, 30 Mar 1997 21:29:18 -0500 (EST)
From: Paul Southworth <pauls@locust.etext.org>
To: freebsd-hardware@freebsd.org
Subject: Crashes with 6x86L-P200+
Message-ID: <Pine.NEB.3.95.970330211027.17917A-100000@locust.etext.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hardware@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Yes, another annoying Cyrix owner.  I won't ask you why it's not
recognized as a Pentium because I don't care.  I bought a 6x86L-P200+ and
a Mustang R534E motherboard with SIS 5571 chipset (yes, it really supports
the 6x86-P200).

The machine runs fine for an hour or two and then crashes regularly.  No
obviously replicable action appears to be crashing it, other than that it
generally crashes as soon as any significant load is incurred (eg, running
glimpseindex, running a dump to tape, compiling libc). The same machine is
currently running an Intel P5-133 with no problems (same everything, no
changes other than motherboard jumper settings for the P5-133).

The offending processor has the following stamped on it: 

6x86L-PR200*GP
150Mhz
3.3v

S/N: GAKJ3702A

System is:  FreeBSD 2.2.1, 6x86L-P200+, 128Mb EDO RAM, AHA 2940UW (BIOS
1.25), 3C595, ISA VGA, no X.

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...".

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