From owner-freebsd-stable Mon May 1 16:22:51 2000 Delivered-To: freebsd-stable@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id A2FF437B588 for ; Mon, 1 May 2000 16:22:07 -0700 (PDT) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.22 2000/04/06 17:58:51 dmccart Exp $) with ESMTP id QAA07593; Mon, 1 May 2000 16:22:05 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id QAA19899; Mon, 1 May 2000 16:22:04 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id TAA13823; Mon, 1 May 2000 19:22:04 -0400 (EDT) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14606.4507.916264.944604@hip186.ch.intel.com> Date: Mon, 1 May 2000 16:22:03 -0700 (MST) To: Daniel Frazier Subject: Re: make buildworld fails... In-Reply-To: <390E0F78.AE694C64@magpage.com> References: <200005012244.PAA18097@freeway.dcfinc.com> <390E0F78.AE694C64@magpage.com> X-Mailer: VM 6.75 under Emacs 20.3.11 Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Monday, May 1, Daniel Frazier wrote: ] > > Wow, not quite the answers I was looking for, but at least you've all > given me an idea of what to look for. Thanks for your help. By the > way, do you know of any RAM stress test/diagnostic utility that could > help narrow this down? > Try: http://reality.sgi.com/cbrady_denver/memtest86/ I've used this recently on some DIMMs that I got at fry's (and promptly returned because they were crap). There's people that say "only a hardware memory tester is reliable" which is true, but at least this program helped**. -Jr ** helped in the sense that I saw craploads of errors which if I was running an OS at that point in time, would have translated into non-cool things. The progie doesn't really help "narrow down" anything. Just "got bad RAM--go get another stick." .... -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message