OBSOLETE Patch-ID# 101378-18 Keywords: WIDE scsi negotiation esp isp driver fw synchronous maxdma HBA Synopsis: OBSOLETED by 101318 Date: Jan/17/96 Solaris Release: 2.3 SunOS Release: 5.3 Unbundled Product: Unbundled Release: Topic: SunOS 5.3: WIDE scsi negotiation and esp, sd and isp driver fixes BugId's fixed with this patch: 1134617 1136580 1137670 1143567 1145242 1145757 1148668 1149518 1151965 1152282 1154770 1155505 1162277 1162475 1163617 1164926 1173973 1174992 1183215 1184788 1186920 1188367 1189329 1194397 1199500 1224486 1224604 Changes incorporated in this version: 1224486 1224604 Relevant Architectures: sparc Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: 101318 on Sep/03/97 Files included with this patch: /usr/include/sys/scsi/targets/sddef.h /kernel/drv/esp /kernel/drv/isp /kernel/drv/sd postinstall script Problem Description: 1224486 sd: there should be retries for both read & write in case of media/hw error 1224604 sd: retries on KEY_ABORTED_COMMAND should eventually be given up (from 101378-17) 1186920 kernel panic with data fault when "sched" is accessing diskarray 1199500 isp: with the new ISP PROM, ISP in 2.3 or 2.4 should still run ISP f/w in driver (from 101378-16) 1189329 esp: implicit restore data pointer fix is not complete (bug id 1183215) (bug id1183215 (from 101378-15) 1188367 isp0 : unknown capacity , disk offline (from 101378-14) 1194397 esp: scsi_reset fails with return value zero if patch(101378-10) is applied (from 101378-13) 1184788 ESC - A SCSI-2(?) peripheral eventually times out in SYNC mode of operation (from 101378-12) 1183215 esp: implicit restore pointer at reconnect is incomplete (from 101378-11) 1174992 SC2000 Plus with 17 Modules panics upon boot due to ISP firmware problem, kernel panics running ISP firmware 1.12, 1.11 and earliers. (from 101378-10) 1152282 savecore gets segmentation violation While trying to produce a crash dump on a sun4d, the system savecore program gets a segmentation violation. 1173279 esp: A lot of scsi warning messages are displayed. While trying to start up heavy disk activity and then load and unload the st driver, a lot of scsi warning messages are displayed on the console window. Afterwards, the disks are inaccessible. (from 101378-09) 1173973 esp: scsi resets occurring more often with newer fab FAS286 chips On Sun4d systems (both sundragons and scorpions) we are getting more scsi timeout resets now with the newer reduce die FAS286 chips ( 2400150). They are no longer making the old style chip (2400121) anymore . It doesn't seem to be configuration dependent. On sundragons it occurs most often on tape devices. It also shows up more often with the 1/2 height exabyte 8 mm tape drive. (from 101378-08) 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 volume 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 configuration 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: disable default SCSI_WIDE capability 1137670 sd: add support for wide data transfer 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: -------------------------------- Refer to the Install.info file within the patch for instructions on using the generic 'installpatch' and 'backoutpatch' scripts provided with each patch. Any other special or non-generic installation instructions should be described below. Special Install Instructions: ----------------------------- None.