*BSD News Article 87200


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!lucy.swin.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.syd.connect.com.au!phaedrus.kralizec.net.au!news.mel.aone.net.au!grumpy.fl.net.au!news.webspan.net!news1.exit109.com!en.com!news.IAEhv.nl!visi.com!mr.net!newshub.tc.umn.edu!fu-berlin.de!news.coli.uni-sb.de!news.phil.uni-sb.de!not-for-mail
From: rock@wurzelausix.CS.Uni-SB.DE (D. Rock)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Problems in ncr.c SCSI code
Date: 21 Jan 1997 17:34:50 GMT
Organization: Universität des Saarlandes
Lines: 35
Message-ID: <5c2unq$jvs@pf1.phil.uni-sb.de>
NNTP-Posting-Host: wurzelausix.cs.uni-sb.de
X-Newsreader: TIN [UNIX 1.3 950824BETA PL0]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:34313

While doing some stress testing on some connected SCSI drives
I discovered a problem, while opening the same raw-device
more than once at the same time. I was able to reproduce
the error with the following commands:
% dd if=/dev/rsd0 of=/dev/null & dd if=/dev/rsd0 of=/dev/null
Then I get the following error messages:
sd1(ncr1:1:0): NOT READY asc:4,1
sd1(ncr1:1:0):  Logical unit is in process of becoming ready
, retries:2
sd1(ncr1:1:0): NOT READY asc:4,1
sd1(ncr1:1:0):  Logical unit is in process of becoming ready
, retries:1
sd1(ncr1:1:0): NOT READY asc:4,1
sd1(ncr1:1:0):  Logical unit is in process of becoming ready
, FAILURE
sd1(ncr1:1:0): NOT READY asc:4,1
sd1(ncr1:1:0):  Logical unit is in process of becoming ready
, retries:2
sd1(ncr1:1:0): NOT READY asc:4,1
sd1(ncr1:1:0):  Logical unit is in process of becoming ready
, retries:1
sd1(ncr1:1:0): NOT READY asc:4,1
sd1(ncr1:1:0):  Logical unit is in process of becoming ready
, FAILURE
Sometimes one process stops with a 'device not configured'.
This failure seems to occur only during open. While running
both dd's no additional messages appear (even with a skip=xxx
for one dd, which makes the harddisk do heavy seeks).

The problem is ncr-related. With a Adaptec 2940 everything
just works fine.
(No difference with 2.1.6-RELEASE or 3.0-CURRENT)

Thanks for hints
Daniel