PROBLEM: (QAR 70824) (Patch ID: OSF440-062) ******** This patch fixes a problem in which a system with a KZPCA host bus adapter may hang when the SCSI bus is reset. PROBLEM: (QAR 72878, QAR 73074) (Patch ID: OSF440-119) ******** The event logger will report command timeouts. PROBLEM: (QARs 71852, 72677) (Patch ID: OSF440-129) ******** A panic, machine check, or hang can occur when aborting an I/O due to a command timeout or aborting an application program with pending I/Os. PROBLEM: (QAR 71852, QAR 73310, QAR 73450) (Patch ID: OSF440-129) ******** The following problems on the ITPSA driver that supports the KZPCM adapteron can occur while the system is processing a SCSI bus or SCSI bus device reset request that is issued from the class driver: 1. The following ITPSA events are logged in the /var/adm/binary.errlog file or the /var/adm/messages file: a. Command timeout b. Illegal instruction c. HTH timeout d. SCSI bus reset error 2. The system panics and displays the message "xpt_callback: ccb not on any list" 3. The system panics and displays the message "simple_lock: time limit exceeded" PROBLEM: (QAR 73625) (Patch ID: OSF440-129) ******** On the 8951U and 8952U adapters, SCSI bus resets are lost when these adapters are connected to single ended drives. PROBLEM (QAR 72677) (Patch ID: OSF440-129) A "simple_unlock: no locks owned by cpu" panic can occur during boot when lockmode is set to 4. PROBLEM: (QAR 71594) (Patch ID: OSF440-072) ******** This patch fixes a problem with the ITPSA driver for KZPCM and KZPCA devices, which resulted in a syncrhonization problem, causing the SCSI bus to hang. Sense data was potentially lost because the autosense command was being queued at the tail of the request queue. In addition, request sense and inquiry commands were updated to ensure that there are no other synchronization problems. PROBLEM: (QAR 72008) (Patch ID: OSF440-235) ******** This patch fixes a simple lock timeout panic. It was possible for a bus reset to be generated before the previous bus reset was processed, causing excessive processing within the ISR. PROBLEM: (QAR 74525) (Patch ID: OSF440-235) ******** This patch fixes kernel memory fault panic caused by a SWS data structure being released twice. PROBLEM: (QAR 72879) (Patch ID: OSF440-235) ******** This patch fixes a problem where chip interrupt register fields in error log are incorrect. PROBLEM: (QAR 73998) (Patch ID: OSF440-235) ******** This patch fixes a problem where an error message was being logged for a condition, which is not a true error. PROBLEM: (75578, 78319, 75527, 77190) (PATCH ID: OSF440-386) ******** This patch fixes the following two problems with the ITPSA driver: - The driver negotiated for ULTRA2 speed when it was attached to a single-ended bus. With this patch, the driver will negotiate for ULTRA speed if attached to a single-ended bus and ULTRA2 speed if attached to a LVD bus. - The system will panic in itpsa_allocReq() on boot when lockmode=4 is set. PROBLEM: (STL047529) (PATCH ID: OSF440-561) ******** The patch fixes a problem with some slower tape devices serviced by the itpsa driver by lengthening the timeout value used. PROBLEM: (BCSM91X60) (PATCH ID: OSF440-568) ******** This patch fixes a simple lock time-out and kernel memory fault that can occur with EV6 hardware and the itpsa driver. Stack traces look like the following: panic+228: stop_secondary_cpu(0xff800180) event_timeout+252: panic("event_timeout: panic request") xcpu_puts+76: event_timeout() printf+312: xcpu_puts() panic+584: printf() simple_lock_fault+492: panic("simple_lock: time limit exceeded") simple_lock_time_violation+24: simple_lock_fault() simple_lock_D+0: simple_lock_time_violation() WARNING: "st" irregularity: repeating frame: simple_lock_D+0 0 stop_secondary_cpu src/kernel/arch/alpha/cpu.c : 614 1 panic src/kernel/bsd/subr_prf.c : 751 2 event_timeout src/kernel/arch/alpha/cpu.c : 1183 3 xcpu_puts src/kernel/bsd/subr_prf.c : 895 4 printf src/kernel/bsd/subr_prf.c : 423 5 panic src/kernel/bsd/subr_prf.c : 804 6 trap src/kernel/arch/alpha/trap.c : 1760 7 _XentMM src/kernel/arch/alpha/locore.s : 1741 8 thread_dup src/kernel/arch/alpha/pcb.c : 638 9 itpsa_hba_go src/kernel/io/cam/iti/itpsacfg.c : 744 PROBLEM: (86450, none) (PATCH ID: OSF440-601) ******** This patch fixes a panic in the itpsa driver. It is seen when an abort to the SCSI rewind command is issued. The problem is a result of the TLZ10 not responding to selections while performing a rewind. The panic string will look as follows: "xpt_callback: callback on freed CCB" PROBLEM: (91878) (PATCH ID: OSF440-780) ******** This patch adds the capability for KZPCA devices to work with SCSI devices that only support asynchronous data transfers. Typically this problem with data transfer negotiation happens during boot and results in certain SCSI devices not being available after OS boot has completed. ie- these SCSI devices would be seen at console level but not under Tru64 and there would be console error messages related to these deveices during boot. Previously during data transfer negotiations, the KZPCA would issue a MESSAGE REJECT message when it received a SYNCHRONOUS DATA TRANSFER REQUEST message with REQ/ACK offset set to zero from a target. However this is a valid SCSI transaction indicating that the target does not support synchronous data transfers with the implied agreement that data transfer mode should be set to asynchronous mode. PROBLEM: (94632) (PATCH ID: OSF440-900) ******** Kernel memory fault seen at boot time with the following messages and stack trace: ITPSA: can't allocate script memory trap: invalid memory read access from kernel mode crash> tf > 0 stop_secondary_cpu src/kernel/arch/alpha/cpu.c : 1394 1 panic src/kernel/bsd/subr_prf.c : 1320 2 event_timeout src/kernel/arch/alpha/cpu.c : 2341 3 printf src/kernel/bsd/subr_prf.c : 1004 4 panic src/kernel/bsd/subr_prf.c : 1378 5 trap src/kernel/arch/alpha/trap.c : 2285 6 _XentMM src/kernel/arch/alpha/locore.s : 2219 7 itpsa_newReq src/kernel/io/cam/iti/itpsa.c : 4279 PROBLEM: (GB_G02141) (PATCH ID: OSF440-723) ******** This patch fixes a kernel memory fault panic after an "ITPSA: itpsa_action - error converting path ID to ITPSA softc structure" message. This is caused because the error logger tries to use a pointer to a data structure which is not valid. PROBLEM: (GB_G04640) (PATCH ID: OSF440-901) ******** Under certain type of tape errors, the SDLT tape drive sends SCSI messages to the KZPCA adapter which, while still compliant with the SCSI signalling specifications, are semantically wrong. This causes the adapter to suspend the SCSI bus for 30+ seconds and reset the bus. The fix in this patch kit prevents the bus suspension and reset, which is disruptive, from happening and enables the recovery of the source of error from the tape drive. SCSI trace shows 546329 299_880 Bus Free 546330 3_300 Arb 546331 2_236 Arbwin 7 546332 0_932 +Select 7,1 546333 0_952 +Sel/Resel End 546334 3_952 +MsgOut C0 Identify 546335 11_652 CMD - Write(6) <-- KZPCA sends a write to the tape 0A 00 00 0F CE 00 546336 4_668 MsgIn 02 Save Data Ptr 04 Disconnect <-- tape disconnects to complete the operation 546337 72.984_698_496 Bus Free 546338 2_428 Arb 546339 1_364 Arbwin 1 546340 1_232 Resel 7,1 <-- tape reconnects 546341 0_492 Sel/Resel End 546342 37.835_845_308 MsgIn 80 Identify 02 Save Data Ptr <<< tape sends a SDP message ! 04 Disconnect 546343 92_568 Bus Reset <-- KZPCA resets bus after 37 seconds 546344 21_993_576 Bus Free Proble: tape reconnects, sends and identify then a Save data pointer (SDP) message. The KZPCA driver is not expecting the SDP message at this point since it does not make any sense. The code falls into the default handler which hangs the bus. The bus eventually gets reset. PROBLEM: (none) (PATCH ID: OSF440-1043) ******** This patch fixes a window where I/Os for a given SCSI target can be created while the target is in the process of negotiating its synchronous parameters. This can cause the IO to pick up asynchronous connection parameters to a target which we negotiate for synchronous connection. This can result in failure to access the target device and generation of "HTH error" messages.