From owner-freebsd-current@FreeBSD.ORG Sat May 10 01:27:32 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 03A8337B401; Sat, 10 May 2003 01:27:32 -0700 (PDT) Received: from MX4.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FDA343FE3; Sat, 10 May 2003 01:27:30 -0700 (PDT) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-32-7-dsl.mus.estpak.ee [80.235.32.7]) by MX4.estpak.ee (Postfix) with ESMTP id 641C61D0020; Sat, 10 May 2003 11:27:29 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h4A1RT50001561; Sat, 10 May 2003 04:27:29 +0300 (EEST) (envelope-from vallo) Date: Sat, 10 May 2003 04:27:29 +0300 From: Vallo Kallaste To: Don Lewis Message-ID: <20030510012729.GA1342@kevad.internal> References: <20030509153335.GA61844@dragon.nuxi.com> <200305092059.h49KxbM7038755@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200305092059.h49KxbM7038755@gw.catspoiler.org> User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-current@FreeBSD.org cc: hschaefer@fto.de Subject: Re: data corruption with current (maybe sis chipset related?) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2003 08:27:32 -0000 On Fri, May 09, 2003 at 01:59:37PM -0700, Don Lewis wrote: > I've seen it on my Athlon XP box with 1GB of ECC RAM. If I ran "make > buildworld" a number of times in a row, it would barf on a corrupted > file in /usr/src. A 16 byte chunk of a source file would be changed to > some sort of random garbage. It was just the copy of the file that was > cached in RAM that was corrupted. Rebooting the system would show that > the file was undamaged. Adding the kernel options mentioned earlier in > this thread makes the machine run flawlessly. How did you built the world for testing? With missing /etc/make.conf or with some specific options, with -j or without? I have SMP Athlon box with 1GB ECC memory and would like to reproduce it. I'm able to reproduce it at will on P4 Celeron with 128MB of memory (gcc dies in parallel buildworld). -- Vallo Kallaste