From owner-freebsd-scsi Thu Sep 18 01:55:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19882 for freebsd-scsi-outgoing; Thu, 18 Sep 1997 01:55:15 -0700 (PDT) Received: from forwiss.tu-muenchen.de (root@forwiss.tu-muenchen.de [131.159.128.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19861; Thu, 18 Sep 1997 01:55:10 -0700 (PDT) Received: from pccog4.forwiss.tu-muenchen.de (hafner@pccog4.forwiss.tu-muenchen.de [131.159.128.55]) by forwiss.tu-muenchen.de (8.8.5/V5) with ESMTP id KAA01841; Thu, 18 Sep 1997 10:55:06 +0200 (MET DST) Received: (hafner@localhost) by pccog4.forwiss.tu-muenchen.de (8.8.5/8.6.12) id IAA03695; Thu, 18 Sep 1997 08:57:34 GMT Date: Thu, 18 Sep 1997 08:57:34 GMT Message-Id: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de> From: Walter Hafner To: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Cc: hafner@forwiss.tu-muenchen.de Subject: Is my NCR controller broken? Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I just want to make sure I don't miss something before changing my mainboard. Please enlighten me. I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI controller). This computer runs for about 3 years now (2.0.5, 2.1.0, 2.1.5) Since about four weeks I keep getting SCSI resets and then the bus is dead. No recovery! And it's really strange because the NCR controller reports totally different errors before hanging. Here are the error reports from the last three crashes (typed in by hand, so the actual format may differ): ------------------------------------------------------------------------------- sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24) ncr0: timeout ccb=f19fbc00 (skip) ------------------------------------------------------------------------------- ncr0:1: ERROR (a0:0) (f-28-0) (8/13) @ (260:00000000). script cmd=fc00001c. reg: da 10 80 13 47 08 01 1f 00 0f 81 28 80 00 00 00. ncr0: restart (fatal error). sd1(ncr0:1:0): command failed (9ff)@f19fbc00. nrc0: timeout ccb=f19fbc00 (skip) ------------------------------------------------------------------------------- ncr0: SCSI phase error fixup: CCB already dequeued (0xf19fbc00) nrc0: timeout ccb=f19fbc00 (skip) ------------------------------------------------------------------------------- I changed everything: * disconnected everything except the system drive -> still errors * changed cables (three different ones) -> still errors * changed termination (two different external ones, internal, different termpower sttings etc.) -> still errors * turned all devices to 5MB synchr. and finally to acync via 'ncrcontrol' -> still errors * finally replaced the system drive (old DEC 5200 against new IBM DAHC 34330) and put 2.2.1 on it -> still errors. Actually, the errors above are from that setup. The only thing I didn't change was the mainboard. I'd be glad if anyone can confirm my suspicion that the NCR controller has gone nuts. I just can't imagine why ... I'd also appreciate it very much if someone with more insight than myself could explain the error reports to me. I'd especially like to know what this 'f19fbc00' means: it shows up in all three errors (what's a 'ccb' anyway?) Thanks in advance! -Walter