Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Mar 1996 15:57:33 +0100
From:      se@zpr.uni-koeln.de (Stefan Esser)
To:        Jim Lowe <james@miller.cs.uwm.edu>
Cc:        current@freebsd.org
Subject:   Re: NCR disk controller, hp disk
Message-ID:  <199603101457.AA04448@Sisyphos>
In-Reply-To: Jim Lowe <james@miller.cs.uwm.edu> "NCR disk controller, hp disk" (Mar  8, 16:39)

next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 8, 16:39, Jim Lowe wrote:
} Subject: NCR disk controller, hp disk

Hi Jim!

Sorry for the late reply ...
I had intended to stay off my office this weekend
and only came in by accident ...

Well, lets see:

} I have an NCR 825 PCI disk controller.  I just attached a second disk
} to the controller and am trying to access it.  The second disk works
} just fine under dos, but not freebsd-current.  I am getting the following
} errors:
} 
} sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted
} , retries:4
} sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted
} , retries:3
} sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted
} , retries:2
} sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted
} , retries:1
} sd1(ncr0:1:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted
} , FAILURE
} sd1: error reading primary partition table reading fsbn 0 (sd1 bn 0; cn 0 tn 0 s
} n 0)

This particular HP drive (the C3724S) is known 
to cause problems with tagged commands. Please
rebuild your kernel with

options "SCSI_NCR_DFLT_TAGS=0"

and everything will be fine again.

You can reenable tags for the first drive using

# ncrcontrol -s tags=0 -s tags=4


I'd be really interested to understand what is
going wrong here, since this is the only drive 
known to cause that kind of problem. The driver
sends the command and the drive its reply just
fine, but this reply indicates that the drive
doesn't accept a tagged command, though it did
inidcate support for this feature before.

} Any clues as to what to try/do next?  The boot up information follows.
} I am not sure why I am getting the probe0(ncr0:9:0) errors either.

This is a result of your building the kernel
with "options SCSIDEBUG" and having a target
of 9 selected in "/sys/scsi/scsi_debug.h".

Please change this '9' into a '1' and send the 
boot log, since this may help me understand the
reason for the incompatibility.

If you are interested in getting this resolved,
I'd need you to do a few more tests later. But
you may choose to use the drive without tagged
commands instead, it will still be fast enough :)


Regards, STefan
-- 
 Stefan Esser, Zentrum fuer Paralleles Rechnen		Tel:	+49 221 4706021
 Universitaet zu Koeln, Weyertal 80, 50931 Koeln	FAX:	+49 221 4705160
 ==============================================================================
 http://www.zpr.uni-koeln.de/~se			  <se@ZPR.Uni-Koeln.DE>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603101457.AA04448>