Patch-ID# 101378-08 Keywords: WIDE scsi negotiation esp isp driver fw synchronous maxdma HBA reset Synopsis: SunOS 5.3: WIDE scsi negotiation and esp and isp driver fixes Date: Jun/08/94 Solaris Release: 2.3 SunOS release: 5.3 Unbundled Product: Unbundled Release: Topic: SunOS 5.3: WIDE scsi negotiation and esp and isp driver fixes BugId's fixed with this patch: 1143567 1145242 1137670 1136580 1149518 1145757 1134617 1148668 1151965 1155505 1154770 1163617 1162277 1164926 1162475 Changes incorporated in this version: 1162475 Relevant Architectures: sparc Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Files included with this patch: /kernel/drv/esp /kernel/drv/isp /kernel/drv/sd Problem Description: 1162475 esp: Restore data pointer triggers a SCSI bus reset If a data transfer is in progress and a restore data pointer message is issued, it appears that the ddi dma window check somehow fails. The host adapter first attempts to abort the data transfer with an abort message. Failing that, it reset the bus. In any case, this translates into a hard failure. STK uses the restore data pointer message because they do not have a look-aside data buffer to handle incompressible data. They simply issue a restore data pointer message and restart the data transfer instead. Net effect, under Solaris 2.3, you can't backup your system with an STK tape drive with data compression enabled. (from 101378-07) 1164926 sd: need mechanism to restart command for sun4 if HBA returns TRAN_BUSY When user runs volumne manager on a Sun4 machine and uses CD-ROM drive, he can sometime get his regular command rejected and see message like: WARNING: /dev/ncr@3d,200000/sd@6,0 (sd7): transport rejected (0) (from 101378-06) 1162277 esp: unnecessary maxdma check within esp.c There appears to be an un-necessary DMA size check within esp.c. From what I can ascertain, the data transfers are broken into 64k transport sizes anyway, so that checking for exceeding the maxdma value does not appear to be warranted. (from 101378-05) 1163617: Part of patch 101378-03 missing For rev -01 of patch 101378, there was a prepatch script that would edit /etc/system. This script was missing from revs -03 and -04. The change to /etc/system sets scsi_options to 0x3f8. (from 101378-04) 1155505: isp: driver should always try synchronous data xfer negotiations first If drives are in synchronous mode when isp starts booting and scsi_options don't have SYNC flag set, isp tries to use ASYNC mode. That gives a lot of firmware errors. Hence, isp driver should always try SYNC negotiations first. 1154770 isp: upgrade f/w to 1.12 this f/w fix (isp_fw.c) fixes the null handle problem (spr893) (isp returns a response packet without a handle which blows up the isp driver) ; 1-7-94 ggm [spr893] the Bus_Dev_Rst_Seq_Int* ; routine was changed to process * ; the following SCSI messages: * ; BUS DEVICE RESET, ABORT, and * ; ABORT TAG. * ; 1-10-94 ggm [spr893] to correct the null * ; handle problem all decisions * ; based on the scsi_task_state are* ; now based on all 8 states. * ; (from 101378-03) 1148668 isp: timeouts and fatal errors caused by changing pkt_time 1151965 isp: f/w version 1.11 1148668: the 1093 isp driver copies the packet resp_time over to pkt_time. This is a violation of SCSA and also causes spurious timeouts and fatal errors. Furthermore, if a packet is transported with pkt_time == 0 then this means no timeout, The fatal timeout handling code should ignore these packets. 1151965: this is a f/w release from qlogic (1.11) which will go in prom 1.17 this release fixes: SPR 898 - Enhancement Call Syserr spr 899 - Set parity enable bit correctly spr 900 - Fix for system hang when response queue gets full spr 901 - Set dqcb_cmd_depth_limit correctly spr 902 - Patches for earlier SPR894/897 spr 885 - Correct ise of throttle. (IGOR's request) (from 101378-02) 1136580 1149518 1145757 1134617 1149518: the esp driver does not handle target initiated sync mode correctly which causes a hang and timeout if the negotiation is immediately followed by a data xfer the problem is in programming the offset and period registers. The req/ack delay is correctly set in the soft copy of this register but not in the register itself. The next time the register is programmed, the soft copy value is used and then there is no problem which is why this bug was not noticed before. 1136580: Heavily loaded SS600MP with DSBE/S on SES/B panics. Please see bug itself for the actual configration where this happens. 1145757: esp does not issue a device scsi reset when you call scsi_reset(ROUTE, RESET_TARGET) from sd driver. instead it issues a test unit ready. it will impact all target drivers that issue scsi_reset to a particular device. scsi_reset(ROUTE, RESET_ALL) works still. 1134617: Getting "WARNING: Processor level 3 SBus interrupt not serviced" message during C2+ bootup of alpha2.0-a and alpha2.0-b. (from 101378-01) 1143567 esp: eliminate warning message for wide scsi negotiation rejection 1145242 isp: disble default SCSI_WIDE capability 1137670 sd: add support for wide data tranfer negotiations These bugs deal with WIDE scsi negotiation. 1145242 SCSI_WIDE capability should be disabled for isp for all targets by default. only if target driver wishes, WIDE capability should be turned on by a per target basis. 1143567 When ever a SCSI disk drive initiates a wide data transfer negotiation, the esp host adapter driver correctly rejects the message (it's not a wide host adapter). BUT, it then prints out warning messages which are displayed on both the console and logged in the messages file. This guarantees we will have customers calling up about this "problem". 1137670 The disk driver does not check the inquiry data to see if wide xfers are supported by the drive. The driver should check the inquiry data first before asking the HBA to negotiate wide transfer size. This is to maintain compatibility with our current installed base of SCSI disk drives. This bug currently prevents us from mixing wide and narrow devices on an ISP since the narrow devices do not all behave correctly. Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- none Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev