From owner-freebsd-current Wed Mar 15 15:09:24 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA08064 for current-outgoing; Wed, 15 Mar 1995 11:24:53 -0800 Received: from paris.ics.uci.edu (mmdf@paris.ics.uci.edu [128.195.1.50]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id LAA08058 for ; Wed, 15 Mar 1995 11:24:52 -0800 Received: from bossanova.ics.uci.edu by paris.ics.uci.edu id aa24161; 15 Mar 95 11:21 PST To: current@freebsd.org Subject: Problems with SCSI drive & ncr Date: Wed, 15 Mar 1995 11:20:34 -0800 From: "Brett J. Vickers" Message-ID: <9503151121.aa24161@paris.ics.uci.edu> Sender: current-owner@freebsd.org Precedence: bulk I've noticed a problem with -current that I don't think I ever noticed with 2.0. When accessed, my second SCSI drive occasionally produces the following error message: sd1(ncr0:1:0): ABORTED COMMAND asc:47,0 SCSI parity error fru:2, retries:4 This doesn't happen with sd0(ncr0:0:0). Here is the relevant boot info: >ncr0 int a irq 9 on pci0:3 > reg20: virtual=0xf2f61000 physical=0xfc800000 >ncr0: restart (scsi reset). >ncr0 scanning for targets 0..6 (V2 pl18 95/02/23) >scbus0: ncr0 waiting for scsi devices to settle >(ncr0:0:0): "QUANTUM EMPIRE_1080S 1100" is a type 0 fixed SCSI 2 >sd0(ncr0:0:0): Direct-Access >sd0(ncr0:0:0): sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. >1029MB (2109376 sectors), 2874 C 8 H 91 S/T 512 B/S >(ncr0:1:0): "SEAGATE ST3390N 9546" is a type 0 fixed SCSI 2 >sd1(ncr0:1:0): Direct-Access >sd1(ncr0:1:0): sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. >328MB (672482 sectors), 2679 C 3 H 83 S/T 512 B/S Brett