Date: Mon, 29 Sep 1997 10:18:31 -1000 (HST) From: "David Langford" <langfod@dihelix.com> To: se@freebsd.org (Stefan Esser) Cc: langfod@dihelix.com, scsi@freebsd.org Subject: Re: Possible ncr problem? Message-ID: <199709292018.KAA18082@caliban.dihelix.com> In-Reply-To: <19970928110142.45106@mi.uni-koeln.de> from Stefan Esser at "Sep 28, 97 11:01:42 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Interesting that this never happened to me with sd0 but ony to sd1 when I added it to the chain. Well I have a new kernel without the scsi_start_unit() in "sd.c". I have a "make world" running and I did a partial "dump" to "/dev/null". So far no nasty "sd1: COMMAND FAILED (4 28) @f0497000" messages. -David Langford langfod@dihelix.com >Yes, again the QUEUE_FULL problem of the DORS. >This drive can't deal with a reasonable number >of tagged commands at times, it seems. Since >the generic SCSI layer will immediately re-issue >the failed command, there will be no adverse >effect, if it succeeds within 5 retries. > >You may want to remove the call of scsi_start_unit() >from sd.c (there is only one occurance), and see >whether the error messages are still printed ... > >> sd0: <IBM DORS-32160 S82C> type 0 fixed SCSI 2 >> sd1: <IBM DORS-32160 S82C> type 0 fixed SCSI 2 > >There was roumor, that the non-wide DORS does not >support as many tags as the wide version, though I >never had a chance to confirm this myself. >If you want to help debug the problem, then please >try a kernel that does not start the SCSI drives >in /sys/scsi/sd.c:sdopen(). >Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709292018.KAA18082>