From owner-freebsd-current Sun Apr 19 17:46:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25609 for freebsd-current-outgoing; Sun, 19 Apr 1998 17:46:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from taliesin.cs.ucla.edu (Taliesin.CS.UCLA.EDU [131.179.96.166]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA25598 for ; Mon, 20 Apr 1998 00:45:51 GMT (envelope-from scottm@mordred.cs.ucla.edu) Received: (qmail 11801 invoked from network); 20 Apr 1998 00:44:45 -0000 Received: from mordred.cs.ucla.edu (131.179.48.34) by taliesin.cs.ucla.edu with SMTP; 20 Apr 1998 00:44:45 -0000 Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.8.8/8.8.8) id RAA04292 for current@freebsd.org; Sun, 19 Apr 1998 17:45:49 -0700 (PDT) (envelope-from scottm) Date: Sun, 19 Apr 1998 17:45:49 -0700 (PDT) From: Scott Michel Message-Id: <199804200045.RAA04292@mordred.cs.ucla.edu> To: current@FreeBSD.ORG Subject: Spurious crashes while making world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No, this isn't a report. There are some who pointed out that these "crashes" or "anomolies" are caused by "bad" DRAM. Whilst this may in fact be the case, we might want to consder adding another entry to this FAQ: Mixed DRAM. What I discovered, after changing out DRAM twice, was that I ended up with a combination of Fast Page and EDO. Even worse, the combination was in one bank of SIMMS (one 32M FP and one 32M EDO). The moral of the story is probably to buy DRAM from mail order and not from that venerable warehouse of reliable product, Fry's. So, before we start down the path "Your DRAM is bad" we might want to suggest "Is your DRAM mixed Fast Page and EDO?" BTW: Anyone know of a good way to stare at the chip and determine this? -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message