Date: Fri, 25 Oct 1996 00:01:50 +0200 From: se@zpr.uni-koeln.de (Stefan Esser) To: bde@zeta.org.au (Bruce Evans) Cc: darrylo@sr.hp.com, freebsd-bugs@freefall.freebsd.org, scrappy@freefall.freebsd.org Subject: Re: bin/1547 Message-ID: <199610242201.AAA00600@x14.mi.uni-koeln.de> In-Reply-To: <199610230940.TAA29780@godzilla.zeta.org.au>; from Bruce Evans on Oct 23, 1996 19:40:14 %2B1000 References: <199610230940.TAA29780@godzilla.zeta.org.au>
index | next in thread | previous in thread | raw e-mail
Bruce Evans writes: > >Synopsis: ncrcontrol won't work with FAILSAFE kernel > > > >State-Changed-From-To: feedback-closed > >State-Changed-By: scrappy > >State-Changed-When: Tue Oct 22 22:47:11 PDT 1996 > >State-Changed-Why: > > > >Originator Confirmed Closure > > It's obviously still broken. A struct depends on MAX_TARGET which > depends on SCSI_NCR_DFLT_TAGS which depends on FAILSAFE. I tested > this. It is broken :-). Sorry, this had been reported long ago, but had lower priority (for me) than quite a number of other things. > I have to use the equivalent of FAILSAFE here for a Toshiba MK547FB > boot drive, but I didn't notice the problem because I changed the > source to define SCSI_NCR_DEFLT_TAGS as 0 before FAILSAFE existed, > and have never used FAILSAFE. I will try to fix this, together with two other small problems in ncrcontrol (some uncritical commands work only for root and to many LUNs may be reported). Regards, STefanhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610242201.AAA00600>