Date: Mon, 29 Sep 1997 08:37:14 +0200 From: sthaug@nethelp.no To: se@FreeBSD.ORG Cc: scsi@FreeBSD.ORG Subject: Re: Possible ncr problem? Message-ID: <905.875515034@verdi.nethelp.no> In-Reply-To: Your message of "Sun, 28 Sep 1997 11:01:42 %2B0200" References: <19970928110142.45106@mi.uni-koeln.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Any thought on what this means? > > 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. I have a slightly different problem. I have an ASUS SC200 controller with a Seagate ST15150N (the old half-height 4 GB Barracuda) and an IBM DORS 32160. The bootup messages are: (ncr0:0:0): "IBM DORS-32160 WA0A" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): 10.0 MB/s (100 ns, offset 8) (ncr0:1:0): "SEAGATE ST15150N 0022" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): 10.0 MB/s (100 ns, offset 8) My problem is that I get the COMMAND FAILED, Sep 29 02:05:09 verdi /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 5565 Sep 29 02:05:09 verdi /kernel: sd1(ncr0:1:0): COMMAND FAILED (4 28) @f08e1600. at irregular intervals, and it's always the Seagate disk it happens to. When this starts, it never stops again until I reboot the machine. The machine quickly becomes unusable when it happens. (And yes, it happened again last night, while /etc/daily was being run.) Any ideas? Steinar Haug, Nethelp consulting, sthaug@nethelp.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?905.875515034>