From owner-freebsd-hardware Sun Mar 30 21:01:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA15348 for hardware-outgoing; Sun, 30 Mar 1997 21:01:49 -0800 (PST) Received: from mx.serv.net (mx.serv.net [199.201.191.10]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA15316 for ; Sun, 30 Mar 1997 21:01:44 -0800 (PST) Received: from MindBender.serv.net by mx.serv.net (8.7.5/SERV Revision: 2.30) id VAA04895; Sun, 30 Mar 1997 21:01:44 -0800 (PST) Received: from localhost.HeadCandy.com (michaelv@localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.7.5/8.7.3) with SMTP id VAA01099; Sun, 30 Mar 1997 21:01:25 -0800 (PST) Message-Id: <199703310501.VAA01099@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: Host michaelv@localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Paul Southworth cc: freebsd-hardware@freebsd.org Subject: Re: Crashes with 6x86L-P200+ In-reply-to: Your message of Sun, 30 Mar 97 21:29:18 -0500. Date: Sun, 30 Mar 1997 21:01:25 -0800 From: "Michael L. VanLoon -- HeadCandy.com" 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). Two things I can think of: Your memory can't handle running at 75MHz (most machines, including your Pentium at 133, run the memory bus at ~66.7MHz). Try turning the memory to a slower "speed" in the BIOS. (For example, if you have a setting that sets the memory to x222 access (how many cycles per word access), try x333)). Your heat sink might not be tightly attached to the chip. Even a small gap, or looseness, will make the chip overheat and be crash- happy. Make sure there is a tight surface-to-surface connection across the entire face of the chip and heat sink. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... -----------------------------------------------------------------------------