From owner-freebsd-current@FreeBSD.ORG  Thu May  8 03:45:52 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 6FE2237B401
	for <current@freebsd.org>; Thu,  8 May 2003 03:45:52 -0700 (PDT)
Received: from critter.freebsd.dk (esplanaden.cybercity.dk [212.242.40.114])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 49F7C43F85
	for <current@freebsd.org>; Thu,  8 May 2003 03:45:51 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h48AjmrB002379;
	Thu, 8 May 2003 12:45:48 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: Heiko Schaefer <hschaefer@fto.de>
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Thu, 08 May 2003 12:36:41 +0200."
             <20030508122258.M78057@daneel.foundation.hs> 
Date: Thu, 08 May 2003 12:45:48 +0200
Message-ID: <2378.1052390748@critter.freebsd.dk>
cc: current@freebsd.org
Subject: Re: data corruption with current (maybe sis chipset related?) 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 08 May 2003 10:45:52 -0000

In message <20030508122258.M78057@daneel.foundation.hs>, Heiko Schaefer writes:

>sorry to be pushy, but have you found anything - or been able to reproduce
>anything since then ? i'm still confused how exactly you determined that
>some data on your disk was corrupt.

No, I'm not any further.

What I saw was the stdout/stderr from a "make universe" that suddenly
had a bunch of zero bytes in the middle.

The thing we need, more than anything else, is a way to reproduce
this on demand.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.