From owner-freebsd-stable  Wed Feb  7 15:23:42 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id PAA06819
          for stable-outgoing; Wed, 7 Feb 1996 15:23:42 -0800 (PST)
Received: from localhost.cdrom.com (localhost.cdrom.com [127.0.0.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA06814
          Wed, 7 Feb 1996 15:23:39 -0800 (PST)
Message-Id: <199602072323.PAA06814@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: Host localhost.cdrom.com [127.0.0.1] didn't use HELO protocol
To: Fred Gilham <gilham@csl.sri.com>
cc: stable@freebsd.org
Subject: Re: I can crash freebsd-stable reliably 
In-reply-to: Your message of "Wed, 07 Feb 1996 13:25:37 PST."
             <199602072125.NAA01716@lily.csl.sri.com> 
Date: Wed, 07 Feb 1996 15:23:39 -0800
From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>
Sender: owner-stable@freebsd.org
Precedence: bulk


>I can reliably crash the system by doing dumps of the two seagate
>drives at the same time.  It takes less than five minutes to do this.
>
>The symptoms are that the activity light on the system goes hard on as
>well as the light on one of the disk drives.  Also, the console
>message starts repeatedly reporting
>
>ahc0: target 2 lun 0 (sd2) timed out
>
>After that the whole disk subsystem seems to go south.
>
>I've tried using the scsi-select utility to change the speed of the
>scsi bus to 5mb/sec, but that doesn't cure the problem.

This sounds very much like a cableing or termination problem.

Are you using internal or external periferals?
Are you using active termination?
How long are your cables?

>-Fred Gilham   gilham@csl.sri.com

--
Justin T. Gibbs
===========================================
  FreeBSD: Turning PCs into workstations
===========================================