Date: Fri, 24 Jan 1997 21:27:50 +0100 From: se@freebsd.org (Stefan Esser) To: joe@via.net (Joe McGuckin) Cc: hardware@freebsd.org Subject: Re: NCR SCSI problem Message-ID: <Mutt.19970124212750.se@x14.mi.uni-koeln.de> In-Reply-To: <199701241911.LAA13945@monk.via.net>; from Joe McGuckin on Jan 24, 1997 11:11:38 -0800 References: <199701241911.LAA13945@monk.via.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 24, joe@via.net (Joe McGuckin) wrote: > FreeBSD 2.1.6-RELEASE. > > Jan 24 11:02:29 news /kernel: ncr0 <ncr 53c875 wide scsi> rev 3 int a irq 10 on pci0:10 > Jan 24 11:02:29 news /kernel: ncr0 waiting for scsi devices to settle > Jan 24 11:02:29 news /kernel: (ncr0:0:0): "IBM XP31070W !x 81K6" type 0 fixed SCSI 2 > Jan 24 11:02:29 news /kernel: sd0(ncr0:0:0): Direct-Access > Jan 24 11:02:29 news /kernel: sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled. > Jan 24 11:02:30 news /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. > I'm using a Symbios '875 PCI card with 1 Fast-Wide drive and 3 narrow drives. > > About twice a week we have a crash. Luckily, last night it didn't reboot, so > we could see the messages. > > sd0(ncr:0:0:0) COMMAND FAILED (4 28) @f11b0a00 The 28 above indicates a "Queue Full" condition, which means that the command failed because of resource exhaustion. (The default of 4 tagged commands should not cause this, but it is possible, that some device can't deal with even that number of active commands in certain situations). You may try with less tags allowed for target 0: # ncrcontrol -t 0 -s tags=2 (Or completely disable tags with "tags=0".) > assertion "cp" failed: file "../../pci/ncr.c line 5560 > > swap_pager: I/O error - pagein failed error 5 > vm_fault: pager input (probably hardware error) The SCSI code in 2.2 is much more robust. It retries commands in such situations, and most probably would have recovered from the Queue Full condition. > Are there known problem with this (or any other NCR) card? This > machine is used as a news server, so it gets lots of activity. The most likely cause of your problem is the lack of SCSI command retries in 2.1.x. Regards, STefan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Mutt.19970124212750.se>