From owner-freebsd-scsi Sat May 2 21:16:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25371 for freebsd-scsi-outgoing; Sat, 2 May 1998 21:16:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA25362 for ; Sat, 2 May 1998 21:16:07 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt2-27.HiWAAY.net [208.147.148.27]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id XAA12757 for ; Sat, 2 May 1998 23:16:05 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id WAA01749 for ; Sat, 2 May 1998 22:48:45 -0500 (CDT) Message-Id: <199805030348.WAA01749@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: ncr0 error From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 02 May 1998 22:48:45 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is this something to worry about, or simply an unusual occurance? This HD and SCSI card have been running about 6 months and this is the first thing like this that I know of. Have mentioned elsewhere that I have often (usually) been able to freeze this system when running "cvs update" while Netscape is open. This was different. Was running cvsup to update my /home/ncvs, was seeing "SetAttrib" for most every file. (Wonder if I did something to cause that?). Anyhow, cvsup was disk limited, not 28.8 modem limited so I used "mount -u -o async /r/usr2" and happily noticed cvsup running much faster and taking more CPU. Until about halfway thru, X died. Apparently X's death was only a symptom. System is 2.2.6-stable, as of April 22. XFree86 3.3.1. /home/ncvs is a symbolic link to /r/usr2/ncvs and is on the ncr0 controller (Asus SC875, IBM OEM DCHS09W 2222). Swap is on that disk, root and /usr are on an old Adaptec 2940 (rev 0) and Seagate ST32550N. May 1 21:37:46 nospam /kernel: ncr0:0: ERROR (20:0) (8-0-0) (f/3d) @ (script 418:c0000004). May 1 21:37:46 nospam /kernel: ncr0: script cmd = c1000060 May 1 21:37:46 nospam /kernel: ncr0: regdump: da 00 00 3d 47 0f 00 0f 20 08 80 00 00 00 07 0a. May 1 21:37:46 nospam /kernel: ncr0: have to clear fifos. May 1 21:37:46 nospam /kernel: ncr0: restart (fatal error). May 1 21:37:46 nospam /kernel: sd1(ncr0:0:0): COMMAND FAILED (9 ff) @f07b5800. May 1 21:37:46 nospam /kernel: sd1(ncr0:0:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted May 1 21:37:46 nospam /kernel: , retries:3 May 1 21:37:46 nospam /kernel: sd1(ncr0:0:0): WIDE SCSI (16 bit) enabledsd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 15) May 1 21:53:51 nospam /kernel: ncr0:0: ERROR (81:0) (8-0-0) (f/3d) @ (mem 322828:00000000). May 1 21:53:51 nospam /kernel: ncr0: regdump: da 00 40 3d 47 0f 00 0f 35 08 80 00 80 00 0f 0a. May 1 21:53:51 nospam /kernel: ncr0: restart (fatal error). May 1 21:53:51 nospam /kernel: sd1(ncr0:0:0): COMMAND FAILED (9 ff) @f07b5800. May 1 21:53:51 nospam /kernel: sd1(ncr0:0:0): WIDE SCSI (16 bit) enabledsd1(ncr0:0:0): 20.0 MB/s (100 ns, offset 15) May 1 21:53:55 nospam /kernel: pid 16320 (XF86_Mach32), uid 0: exited on signal 6 umounting all the filesystems on the above disk, and running "fsck -y" against them didn't find anything to fix. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message