Return to BSD News archive
Xref: sserve comp.os.386bsd.questions:14076 comp.periphs.scsi:26155
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!hilbert.dnai.com!redstone.interpath.net!news.sprintlink.net!sundog.tiac.net!wizard.pn.com!satisfied.elf.com!news.mathworks.com!news.kei.com!sol.ctr.columbia.edu!xlink.net!xlink100!sunny.metaworks.de!me-tech.metaworks.de!mschmidt
Date: 19 Oct 1994 21:24:00 +0100
From: mschmidt@me-tech.metaworks.de (Michael Schmidt)
Newsgroups: comp.os.386bsd.questions,comp.periphs.scsi
Message-ID: <5Z8rh0hrNgB@me-tech.metaworks.de>
References: <1994Oct18.210200.5893@integrity.uucp>
Subject: Re: FreeBSD and SCSI problems
Keywords: SCSI
Summary: Problems with SCSI Bus
X-Newsreader: XP v3.02
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Organization: ME Technology
Lines: 27
In article <1994Oct18.210200.5893@integrity.uucp>
haynes@mpd.tandem.com (Jeff Haynes)
wrote:
> If I stress the SCSI bus ( I'll show how I do that in a minute),
> the bus hangs with the SCSI LED stuck on (in most cases).
> The command that I use to stress the bus is:
> cd /
> find . -type f -print -exec cp {} /dev/null \;
>
> This command will run for a while (5-10 minutes) before hanging.
> Sometimes it even completes, but if I run the same command again
> it hangs.
Is any of your SCSI devices connected via external cables?
If yes then *please* be sure of *good* cables, in some cases bad
SCSI cables not completely following the SCSI guidelines cause
problems.
Bye
------------------\
Michael Schmidt | mschmidt@me-tech.metaworks.de : Email
ME Technology | ++49 +6741 7126 : Fax
QNX Products \----------- SCSI and Connectivity
## CrossPoint v3.02 ##