Date: Sun, 12 Oct 1997 03:11:16 -0700 From: John-Mark Gurney <gurney_j@efn.org> To: Stefan Esser <se@FreeBSD.ORG> Cc: scsi@FreeBSD.ORG Subject: Re: Trouble with dump on ncr Message-ID: <19971012031116.19283@hydrogen.nike.efn.org> In-Reply-To: <19971012094426.47163@mi.uni-koeln.de>; from Stefan Esser on Sun, Oct 12, 1997 at 09:44:26AM %2B0200 References: <19971011091605.32335@mi.uni-koeln.de> <199710120615.AAA18578@pluto.plutotech.com> <19971012094426.47163@mi.uni-koeln.de>
index | next in thread | previous in thread | raw e-mail
Stefan Esser scribbled this message on Oct 12:
> On 1997-10-12 00:15 -0600, Kenneth Merry <ken@plutotech.com> wrote:
> > > The start unit command should instead be issued from the
> > > recovery code in the generic SCSI layer, IMHO, whenever
> > > the return status from the SCSI card driver indicates a
> > > drive has (been) stopped in an attempt to recover from
> > > that situation.
> >
> > FWIW, that's what the new CAM SCSI code does. The da (i.e. sd)
> > driver does a read capacity upon open. If the read capacity returns with
> > 0x04, 0x02 ("Logical unit not ready, initializing cmd. required"), the error
> > recovery code issues a start unit command to the drive.
>
> I downloaded that code, but did not have time
> to look into it in detail. It is unfortunate,
> that many parts outside /sys have to me made
> aware of the CAM driver, IMHO.
well.. right now I'm compiling a kernel, with the new CAM code, to
boot one of my crash machines with.. the only really thing that needs
to be changed is config and MAKEDEV.. the others I believe are just
support files for interfacing with the code (libcam and
include/Makefile)... if I remeber right, I just looked at the patches
about 10-15 minutes ago.. :)
ttyl..
--
John-Mark Gurney Modem/FAX: +1 541 683 6954
Cu Networking
Live in Peace, destroy Micro$oft, support free software, run FreeBSD
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19971012031116.19283>