From owner-freebsd-alpha  Thu Apr 12  1:48:15 2001
Delivered-To: freebsd-alpha@freebsd.org
Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204])
	by hub.freebsd.org (Postfix) with ESMTP id C7F3B37B42C
	for <freebsd-alpha@FreeBSD.ORG>; Thu, 12 Apr 2001 01:48:12 -0700 (PDT)
	(envelope-from K.J.Koster@kpn.com)
Received: by l04.research.kpn.com with Internet Mail Service (5.5.2653.19)
	id <2TM2BLTK>; Thu, 12 Apr 2001 10:48:11 +0100
Message-ID: <59063B5B4D98D311BC0D0001FA7E452205FD9B33@l04.research.kpn.com>
From: "Koster, K.J." <K.J.Koster@kpn.com>
To: 'Riccardo Veraldi' <Riccardo.Veraldi@fi.infn.it>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: RE: Interested in your opinion "machine check" 
Date: Thu, 12 Apr 2001 10:48:09 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Dear Riccardo,

> 
> I actually did A LOT of compilation work withotu haveing heavily disk
> access and nothing happened. So I think it's not the RAM in 
> my case but maybe I am wrong
>
Well, if this is actually a PSU problem, the disk I/O may well be causing
supply dips that causes the RAM to barf.

    Kees Jan

================================================
 You are only young once,
       but you can stay immature all your life.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message