From owner-freebsd-bugs Wed Mar 12 13:00:03 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA10989 for bugs-outgoing; Wed, 12 Mar 1997 13:00:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA10938; Wed, 12 Mar 1997 13:00:01 -0800 (PST) Date: Wed, 12 Mar 1997 13:00:01 -0800 (PST) Message-Id: <199703122100.NAA10938@freefall.freebsd.org> To: freebsd-bugs Cc: From: Stefan Esser Subject: Re: kern/2944: NCR/SYM875 card with Ultra drive Reply-To: Stefan Esser Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The following reply was made to PR kern/2944; it has been noted by GNATS. From: Stefan Esser To: vanmaren@fast.cs.utah.edu Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: kern/2944: NCR/SYM875 card with Ultra drive Date: Wed, 12 Mar 1997 21:55:02 +0100 On Mar 10, Kevin Van Maren wrote: > >Synopsis: NCR/SYM875 card with Ultra drive > > When "changing root device to sd0a" comes up, the machine sits there > for several minutes, until it continues (after printing an error > message). The machine appears to operate correctly after that. > > changing root device to sd0a > ncr0: aborting job ... > ncr0:6: ERROR (90:0) (8-0-0) (0/13) @ (a54:50000000). The error code (0x90) indicates a command ahs been aborted. I can only guess what command that might be, but I assume a incompatibility between the driver and your particular disk drive. Is it possible, that the driver tries to use WIDE transfers with the disk ? This may happen, if both the controller and the drive are capable of WIDE transfers, but the SCSI bus is only 8bit wide. In such a case, the command would time out, and the driver would continue in a failsafe mode ... In order to diagnose this problem, I need SCSI DEBUG logs. You'll have to rebuild your kernel with SCSI debug enabled (an option of the generic SCSI driver, not the NCR driver). Use the kernel option line "options SCSIDEBUG" and edit /sys/scsi/scsi_debug.h to define DEBUGTARGET as 6 ... > Also, note that Ultra negotiation is not enabled by the driver, > although the BIOS does initially enable it. The driver disables it, currently. I have been to busy to cleanly add Ultra-20 support. It is easy as a quick hack, but that's not what I'm after ... > (ncr0:6:0): "QUANTUM FIREBALL_TM3200S 300X" type 0 fixed SCSI 2 > sd0(ncr0:6:0): Direct-Access > sd0(ncr0:6:0): 10.0 MB/s (100 ns, offset 15) Hmmm, no trace of an attempt to use WIDE transfers ... > ncr0:6: ERROR (90:0) (8-0-0) (0/13) @ (a54:50000000). > script cmd = 740a8f00 > reg: de 00 00 13 47 00 0f 0f 35 08 86 00 90 00 0f 02. > ncr0: restart (fatal error). > sd0(ncr0:6:0): COMMAND FAILED (9 ff) @f19f9c00. > sd0(ncr0:6:0): 10.0 MB/s (100 ns, offset 15) I have just got another idea: Please check whether a kernel with "options FAILSAFE" does also show this behaviour ... Regards, STefan