From owner-freebsd-hardware Wed Mar 20 07:06:19 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA07188 for hardware-outgoing; Wed, 20 Mar 1996 07:06:19 -0800 (PST) Received: from itsdsv1.enc.edu (itsdsv1.enc.edu [199.93.252.241]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA07167 Wed, 20 Mar 1996 07:06:10 -0800 (PST) Received: (from owensc@localhost) by itsdsv1.enc.edu (8.6.11/8.6.9) id KAA05394; Wed, 20 Mar 1996 10:04:58 -0500 Date: Wed, 20 Mar 1996 10:04:58 -0500 (EST) From: Charles Owens To: Dan Polivy cc: freebsd-stable@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: -stable and NCR problems? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 19 Mar 1996, Dan Polivy wrote: > Hey, > > I just got -stable working, and have had a few odd problems with my ncr0 > PCI scsi controller...It seemed to work fine for 2.1-RELEASE...what has > changed in the ncr driver from release->stable? I can try and give you > more info if you need it...lemme go look in the logs.....Well, just > seeing if anyone else has had this problem? Thanks! What are you seeing? I'm seeing this sorta stuff: Mar 17 12:59:39 dingo /kernel: ncr0:0: ERROR (0:140) (40-67-4) (8/13) @ (abc:008c0064). Mar 17 12:59:42 dingo /kernel: script cmd = c0000001 Mar 17 12:59:42 dingo /kernel: reg: da 10 c0 13 47 08 00 0f a4 40 80 67 00 00 07 00. Mar 17 12:59:42 dingo /kernel: ncr0: have to clear fifos. Mar 17 12:59:42 dingo /kernel: ncr0: handshake timeout Mar 17 12:59:42 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 17 12:59:43 dingo /kernel: , retries:3 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 17 12:59:43 dingo /kernel: ncr0:0: ERROR (80:100) (8-2a-0) (8/13) @ (544:900b0000). Mar 17 12:59:43 dingo /kernel: script cmd = 910a0000 Mar 17 12:59:43 dingo /kernel: reg: da 10 80 13 47 08 00 0f 01 08 00 2a 80 00 02 00. Mar 17 12:59:43 dingo /kernel: ncr0: handshake timeout Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0aede00. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6600. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): COMMAND FAILED (6 ff) @f0ad6800. Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred field replaceable unit: 14 Mar 17 12:59:43 dingo /kernel: , retries:1 Mar 17 12:59:43 dingo /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Mar 17 12:59:43 dingo /kernel: cd0(ncr0:2:0): UNIT ATTENTION asc:29,0 Mar 17 12:59:43 dingo /kernel: cd0(ncr0:2:0): Power on, reset, or bus device reset occurred Usually, after a brief delay, it picks up where it left off with no problem, but I have had a few reboots that could be related. Is this similar to what you're seeing? Should I suspect the driver, my SCSI cable/termination or something else? thanks, --- ------------------------------------------------------------------------- Charles Owens Email: owensc@enc.edu "I read somewhere to learn is to Information Technology Services remember... and I've learned that Eastern Nazarene College we've all forgot..." - King's X -------------------------------------------------------------------------