From owner-freebsd-current Fri Jan 15 08:21:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05396 for freebsd-current-outgoing; Fri, 15 Jan 1999 08:21:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from k6n1.znh.org ([207.109.235.35]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05369 for ; Fri, 15 Jan 1999 08:21:02 -0800 (PST) (envelope-from zach@uffdaonline.net) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id QAA17322; Fri, 15 Jan 1999 16:19:34 GMT (envelope-from zach) Message-ID: <19990115101934.C16631@znh.org> Date: Fri, 15 Jan 1999 10:19:34 -0600 From: Zach Heilig To: Brian Feldman , Archie Cobbs Cc: freebsd-current@FreeBSD.ORG Subject: Re: Weird file corruption? References: <199901130527.VAA10163@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Brian Feldman on Wed, Jan 13, 1999 at 05:26:40PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 13, 1999 at 05:26:40PM -0500, Brian Feldman wrote: ... > How could it be memory when it's written to disk, extracted, then after a nearly > full build read again? Why would it extract completely the first time with no > errors? I had this exact same problem when evaluating pentium motherboards a while back. One of my (parity!) simms was marginal [later verified with a simm checker], but it was not noticed until after I made one corrupt archive [and deleted the originals]. Luckily, both the simm and the motherboard were still returnable. This also verified for me that most Intel chipsets for pentium do not use parity even if available. -- Zach Heilig / Zach Heilig To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message