From vanmaren@marker.cs.utah.edu  Mon Mar 10 19:48:14 1997
Received: from marker.cs.utah.edu (marker.cs.utah.edu [155.99.212.61])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA23496
          for <FreeBSD-gnats-submit@freebsd.org>; Mon, 10 Mar 1997 19:48:14 -0800 (PST)
Received: (from vanmaren@localhost) by marker.cs.utah.edu (8.7.5/8.7.3) id UAA12884; Mon, 10 Mar 1997 20:48:12 -0700 (MST)
Message-Id: <199703110348.UAA12884@marker.cs.utah.edu>
Date: Mon, 10 Mar 1997 20:48:12 -0700 (MST)
From: Kevin Van Maren <vanmaren@marker.cs.utah.edu>
Reply-To: vanmaren@fast.cs.utah.edu
To: FreeBSD-gnats-submit@freebsd.org
Subject: NCR/SYM875 card with Ultra drive
X-Send-Pr-Version: 3.2

>Number:         2944
>Category:       kern
>Synopsis:       NCR/SYM875 card with Ultra drive
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 10 19:50:03 PST 1997
>Closed-Date:    Mon Mar 10 22:13:09 PST 1997
>Last-Modified:  Thu Mar 13 07:00:02 PST 1997
>Originator:     Kevin Van Maren
>Release:        FreeBSD 2.2-970225-GAMMA i386
>Organization:
University of Utah, CSL
>Environment:

FreeBSD 2.2-970225-GAMMA generic install kernel.

>Description:
I boot the kernel: 2:sd(0,a)/kernel (from install floppy)

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).
        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)
========

Also, note that Ultra negotiation is not enabled by the driver,
although the BIOS does initially enable it.

Here is the complete `dmesg' output:

========
Copyright (c) 1992-1996 FreeBSD Inc.
Copyright (c) 1982, 1986, 1989, 1991, 1993
        The Regents of the University of California.  All rights reserved.

FreeBSD 2.2-970225-GAMMA #0: Tue Feb 25 13:16:19 GMT 1997
    root@admin1.calweb.com:/usr/src/sys/compile/GENERIC
Calibrating clock(s) relative to mc146818A clock ... i586 clock: 90211866 Hz, i8
254 clock: 1193281 Hz
CPU: Pentium (90.20-MHz 586-class CPU)
  Origin = "GenuineIntel"  Id = 0x524  Stepping=4
  Features=0x1bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
real memory  = 50331648 (49152K bytes)
avail memory = 46309376 (45224K bytes)
Probing for devices on PCI bus 0:
chip0 <Intel 82434NX (Neptune) PCI cache memory controller> rev 17 on pci0:0
chip1 <Intel 82378ZB PCI-ISA bridge> rev 3 on pci0:2
ncr0 <ncr 53c875 wide scsi> rev 3 int a irq 10 on pci0:6
ncr0 waiting for scsi devices to settle
(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)
3067MB (6281856 512 byte sectors)
vga0 <Display device> rev 0 on pci0:12
Probing for devices on the ISA bus:
sc0 at 0x60-0x6f irq 1 on motherboard
sc0: VGA color <16 virtual consoles, flags=0x0>
ed0 not found at 0x280
ed1 not found at 0x300
fe0 not found at 0x300
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio2: disabled, not probed.
sio3: disabled, not probed.
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
lpt1 not found at 0xffffffff
mse0 not found at 0x23c
psm0: disabled, not probed.
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fdc0: NEC 72065B
fd0: 1.44MB 3.5in
fd1: 1.2MB 5.25in
ft0: Colorado tape
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <WDC AC2420H>
wd0: 405MB (830760 sectors), 989 cyls, 15 heads, 56 S/T, 512 B/S
wdc0: unit 1 (wd1): <WDC AC31200F>
wd1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 at 0x170-0x177 irq 15 on isa
wdc1: unit 0 (atapi): <HITACHI CDR-8130/0020>, removable, accel, dma, iordy
wcd0: 1377/2755Kb/sec, 128Kb cache, audio play, 255 volume levels, ejectable tra
y
wcd0: 120mm data disc loaded, unlocked
bt0 not found at 0x330
uha0 not found at 0x330
aha0 not found at 0x330
aic0 not found at 0x340
nca0 not found at 0x1f88
nca1 not found at 0x350
sea0 not found
wt0 not found at 0x300
mcd0 not found at 0x300
matcdc0 not found at 0x230
scd0 not found at 0x230
ie0 not found at 0x360
ep0 not found at 0x300
ex0 not found at 0x300
ix0 not found at 0x300
le0 not found at 0x300
lnc0 not found at 0x280
ze0 not found at 0x300
zp0 not found at 0x300
npx0 on motherboard
npx0: INT 16 interface
apm0: disabled, not probed.
changing root device to sd0a
ncr0: aborting job ...
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)
========

>How-To-Repeat:

Boot Quantum 3.2GB Fireball on NCR/SYM875 SCSI host adapter.

>Fix:

Unknown
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: mpp 
State-Changed-When: Mon Mar 10 22:13:09 PST 1997 
State-Changed-Why:  
Duplicate of PR# 2330. 

From: Stefan Esser <se@freebsd.org>
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 <vanmaren@marker.cs.utah.edu> 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

From: vanmaren@fast.cs.utah.edu (Kevin Van Maren)
To: se@freebsd.org, 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 14:06:27 -0700

 > On Mar 10, Kevin Van Maren <vanmaren@marker.cs.utah.edu> 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 ...
 
 The drive is narrow -- I don't believe they make a wide version.
 
 > 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 ...
 
 I'll try to get to it tonight.
 
 > > 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 ...
 
 Okay.  I'm sure you announce when it is working right.
 
 > > (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 ...
 
 This was with the install kernel.  I rebuilt a modified GENERIC
 kernel (changed root to sd0 from wd0, got rid of drivers, etc) 
 and I didn't get this message anymore.  (I think FAILSAFE is 
 enabled; I'll have to check when I get home).
 
 Should I try GENERIC unmodified except with the SCSIDEBUG?
 
 > Regards, STefan
 
 Thanks,
 Kevin

From: vanmaren@fast.cs.utah.edu (Kevin Van Maren)
To: vanmaren@fast.cs.utah.edu
Cc: FreeBSD-gnats-submit@freebsd.org, se@freebsd.org
Subject: Re: kern/2944: NCR/SYM875 card with Ultra drive
Date: Thu, 13 Mar 1997 07:58:04 -0700

 > 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 ...
 > 
 /* target and LUN we want to debug */
 #define DEBUGTARG 9 /*9 = dissable*/
 
 Hmmm...what if you have a device at ID 9?
 I'm compiling the GENERIC kernel w/ SCSIDEBUG and #define DEBUGTARG 6.
 
 Okay, how do I make the internal buffer big enough so that it
 will hold enough messages so it doesn't overflow before syslog
 is running?  I have a whole bunch of logs, but they are all AFTER
 the problem, and I don't have annother machine here I can use
 for a serial console (which is obviously they way it should be
 done).
 
 Kevin
>Unformatted:
