From owner-freebsd-hackers  Mon Mar 29 11:44:22 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from implode.root.com (root.com [209.102.106.178])
	by hub.freebsd.org (Postfix) with ESMTP id 2BBDC15232
	for <hackers@FreeBSD.ORG>; Mon, 29 Mar 1999 11:44:16 -0800 (PST)
	(envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.8/8.8.5) with ESMTP id LAA09469;
	Mon, 29 Mar 1999 11:41:36 -0800 (PST)
Message-Id: <199903291941.LAA09469@implode.root.com>
To: Darren Reed <avalon@coombs.anu.edu.au>
Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), hackers@FreeBSD.ORG
Subject: Re: another ufs panic.. 
In-reply-to: Your message of "Tue, 30 Mar 1999 01:50:00 +1000."
             <199903291550.BAA28981@cheops.anu.edu.au> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 29 Mar 1999 11:41:36 -0800
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Well, I toggled the internal BIOS termination setting and
>it still crashes.
>
>when tar got to the end of the run and went back to change
>access/modification times of files in ports/x11-fonts/getbdf
>it crashed.
>
>I think I'll go down to just the two devices involved (wd0
>and that scsi drive), trip the chains and see what happens.
>
>any suggestions (other than upgrade) if it still panics ?
>
>the job at hand is to copy /usr, /usr/local, /usr/src from
>wd0 to the scsi disk.  736952k, 101133 files.

   I had a machine here that behaved the same way (consistently crashed
during heavy filesystem usage). It turned out to be a memory problem,
specifically too much electrical load for the motherboard it was plugged
in to.

-DG

David Greenman
Co-founder/Principal Architect, The FreeBSD Project


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