Patch Name: PHKL_30509 Patch Description: s700_800 11.00 SCSI Ultra160 Cumulative Patch Creation Date: 04/05/24 Post Date: 04/06/07 Hardware Platforms - OS Releases: s700: 11.00 s800: 11.00 Products: N/A Filesets: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP Automatic Reboot?: Yes Status: General Release Critical: Yes PHKL_30509: CORRUPTION PHKL_29494: PANIC CORRUPTION PHKL_29093: PANIC HANG PHKL_27555: PANIC CORRUPTION HANG PHKL_27024: PANIC HANG System panics when defective device generates hundreds of SCSI bus resets per second. System panics with data page fault. Process hangs after kernel reports an error while handling a "Contingence Allegience" condition. Category Tags: defect_repair hardware_enablement general_release critical panic halts_system corruption Path Name: /hp-ux_patches/s700_800/11.X/PHKL_30509 Symptoms: PHKL_30509: ( SR:8606346346 CR:JAGaf07173 ) When odd number of bytes are transferred by a SCSI device connected to an Ultra 160 (A6828A or A6829A) card, the number of bytes transferred is reported incorrectly by the Ultra160 driver. This could result in loss of data integrity. ( SR:8606351535 CR:JAGaf12340 ) open(2) on the device node corresponding to the SCSI initiator ID of the card fails. PHKL_29494: ( SR:8606286153 CR:JAGae50096 ) While booting up, if a DAT tape drive is connected to a SCSI Ultra160 card (A6828A/A6829A), the system panics with the following stack trace : panic+0x14 report_trap_or_int_and_panic+0x84 interrupt+0x3c4 $ihndlr_rtn+0x0 scsi_cbfn+0xd8 scsi_fast_cbfn+0x26c c8xx_basic_cmp_cbfn+0x144 c8xx_call_cbfns+0xc0 c8xx_isr+0x2f8 sapic_interrupt+0x34 mp_ext_interrupt+0x314 ivti_patch_to_nop3+0x0 idle+0x1e84 swidle_exit+0x0 ( SR:8606295528 CR:JAGae59213 ) The following message appears in syslog.log file when the SCSI Ultra160 driver performs negotiation during domain validation with non-Ultra160 speed device, such as Fujitsu disk(MAJ3182MC) using Parallel Protocol Request(PPR) message: "SCSI: Unhandled Message Reject" ( SR:8606296155 CR:JAGae59766 ) 1) With the SCSI Ultra160 card (A6828A/A6829A), while using the STM tool, downloading the firmware to the controller of a StorageWorks Disk System 2300 fails, and the following message is logged in the syslog.log file: "Scripts detected non Active Tag". This failure is followed by a SCSI bus reset. 2) When SCSI Ultra160 card (A6828A/A6829A) is connected to untagged devices, there is a possibility of data integrity issue. PHKL_29093: ( SR:8606292714 CR:JAGae56466 ) Continuous SCSI bus resets are seen when a single ended CD-ROM drive is connected to a system with an Ultra160 card. ( SR:8606297198 CR:JAGae60712 ) System may panic with an alignment fault and the following stack trace when connected to a narrow device: panic+0x6c report_trap_or_int_and_panic+0x94 interrupt+0x208 $ihndlr_rtn+0x0 c8xx_isrMA+0x3cc c8xx_isrSIP+0x158 c8xx_isr+0x334 sapic_interrupt+0x2c mp_ext_interrupt+0x26c ivti_patch_to_nop3+0x0 idle_nonpset_loop+0x704 idle+0x7ac swidle_exit+0x0 ( SR:8606298628 CR:JAGae62127 ) a) The message "First party detected bus hang (HTH)" is seen in the syslog. This also results in SCSI bus reset. b) System panics with the following stack trace: panic+0xa0 kmem_arena_panic+0xc8 kmem_chk_poison+0x12c kfree+0x138 io_mem_free+0x3c ike_psm_free_shared_mem+0x90 compat10_dma_free+0x2c dma_cleanup+0xb8 c8xx_DataCleanup#HLO_CL_#i3_0x400+0x124 c8xx_done#HLO_CL_#i3_0x400+0x110 c8xx_isrRST+0x3cc c8xx_isrSIP+0x25c c8xx_isr+0x308 sapic_interrupt+0x34 up_ext_interrupt+0x224 ivti_patch_to_nop2+0x0 idle+0x6d0 swidle_exit+0x0 PHKL_27555: ( SR:8606255146 CR:JAGae19473 ) System panics with the following stack trace : panic+0x6c assfail+0x3c c8xx_timer+0x804 invoke_callouts_for_self+0x230 sw_service+0x120 mp_ext_interrupt+0x408 ivti_patch_to_nop3+0x0 cc_spinunlock+0x48 spinunlock+0x6c b_psema+0x1c8 local_lockf+0x4c vx_lockf+0xac lockf+0x1b8 syscall+0x808 $syscallrtn+0x0 ( SR:8606267745 CR:JAGae31985 ) System panics with a Data Page Fault with the following stack trace : panic+0x6c report_trap_or_int_and_panic+0x94 interrupt+0x208 $ihndlr_rtn+0x0 c8xx_isrSTO+0x28 c8xx_isrSIP+0x1b4 c8xx_isr+0x36c sapic_interrupt+0x2c mp_ext_interrupt+0x3f0 ivti_patch_to_nop3+0x0 gelan_if_resolved_output+0x580 hp_dlpi_wput+0xfc putnext+0xf0 putnext_return_one+0x10 ip_wput_ire+0xd84 ip_wput+0xe8 putnext+0xf0 tcp_wput_proto+0x390 tcp_wput+0x170 putnext+0xf0 streams_putmsg2+0x470 t_ksndrel+0x778 soclose+0xe18 soo_close+0x90 closef+0x64 close+0x104 syscall+0x7d4 $syscallrtn+0x0 ( SR:8606251412 CR:JAGae17477 ) System panics with the following stack trace : assfail+0x50 c8xx_start+0x690 c8xx_timer+0x1380 invoke_callouts_for_self+0x340 soft_intr_handler+0x100 external_interrupt+0x490 bubbledown ( SR:8606271666 CR:JAGae35874 ) The postinstall script uses ioscan(1M) to determine if an Ultra160 card is present on the system. On systems with large configurations, this command can take a very long time. ( SR:8606260652 CR:JAGae24975 ) System panics with the following stack trace : panic+0x6c assfail+0x3c c8xx_start+0x7cc c8xx_timer+0x300 invoke_callouts_for_self+0x230 sw_service+0x120 mp_ext_interrupt+0x408 ivti_patch_to_nop3+0x0 cc_spinunlock+0x48 spinunlock+0x6c semop+0x524 syscall+0x834 $syscallrtn+0x0 ( SR:8606288219 CR:JAGae52150 ) System panics with the following stack trace : bad_news+0x580 bubbledown+0x0 c8xx_isrAbortDone+0x590 c8xx_isrUDC+0x450 c8xx_isrDIP+0x4b0 c8xx_isr+0x5f0 sapic_interrupt+0x60 external_interrupt+0x250 bubbledown+0x0 idle+0x7b0 netcall_stub+0x0 idle+0x740ubbledown ( SR:8606260893 CR:JAGae25215 ) diskinfo(1M) reports zero disk capacity on Ultra320 IBM disk drives connected to the Ultra160 HBA. ( SR:8606265839 CR:JAGae30093 ) ioscan(1M) hangs forever during system boot-up. ( SR:8606286566 CR:JAGae50505 ) Data integrity problem is seen during I/O with A6828A and A6829A Ultra160 SCSI cards under heavy traffic conditions. ( SR:8606224108 CR:JAGad93204 ) Unexpected SCSI bus resets are seen using A6828A and A6829A Ultra160 SCSI cards connected to two systems in multi-initiator configuration with the following message logged in syslog: "SCSI Gross Error on " ( SR:8606266332 CR:JAGae30581 ) When two systems are connected in multi-initiator configuration using A6828A or A6829A Ultra160 SCSI cards, with I/O's happening on both systems, if one of the systems panic, it enters into an endless reboot loop. ( SR:8606262931 CR:JAGae27261 ) System panics with a Spinlock deadlock message and the following stack trace : panic+0x14 too_much_time+0x2e0 wait_for_lock+0x14c sl_retry+0x1c c8xx_if_tgt_open+0x50 sctl_open+0x1370 call_open_close+0x188 opend+0x128 spec_open+0xa8 vns_copen+0x4c vn_open+0xa8 copen+0xd0 open+0x3c syscall+0x200 $syscallrtn+0x0 ( SR:8606267106 CR:JAGae31349 ) The postinstall script is not compatible with the current scripts architecture. ( SR:8606229159 CR:JAGad98212 ) System panics with the following stack trace : panic+0x6c report_trap_or_int_and_panic+0x94 interrupt+0x208 $ihndlr_rtn+0x0 c8xx_timer+0x5c invoke_callouts_for_self+0x9c sw_service+0x108 mp_ext_interrupt+0x170 ivti_patch_to_nop3+0x0 idle+0x5b4 swidle_exit+0x0 ( SR:8606266776 CR:JAGae31021 ) Handshake-to-Handshake (HTH) time-out errors were seen during system boot-up. ( SR:8606255080 CR:JAGae19409 ) System panics with the following stack trace : assfail+0x50 c8xx_if_start+0x1a0 scsi_start_bus_locked+0xfb0 scsi_start+0x110 scsi_strategy_real+0xcc0 ioforw_int+0x130 soft_intr_handler+0x100 external_interrupt+0x490 bubbledown $DEBUG_ABBREV_CE0002_zzlast_debug_c $DEBUG_PROCS_ABBREV_CE0002_domainname_c+0x2d7e9f8ff28da05 ( SR:8606266447 CR:JAGae30695 ) Processes appear to have hung forever following an abort request because of a bus hang condition. PHKL_27024: ( SR:8606260875 CR:JAGae25197 ) Process hangs and is non-interruptible with the following message in the system log file: Set up error during Contingent Allegiance ( SR:8606238121 CR:JAGae07162 ) Under heavy load on the SCSI bus, 64 Abort messages may be logged in the system log file over a short period of time (10-15 seconds). Abort messages look like the following: SCSI: Request Timeout; Abort Tag -- lbolt: 667772, dev: bc02a000, io_id: 26bfda9 ( SR:8606234217 CR:JAGae03437 ) System panics due to a "Data page fault" with the following stack trace: panic+0x6c report_trap_or_int_and_panic+0x94 interrupt+0x208 $ihndlr_rtn+0x0 scsi_lookup_bp+0x38 scsi_dequeue_bp+0x18 100_2c82_cl_c8xx_done+0xa4 c8xx_isrRST+0x328 c8xx_isrSIP+0x2b0 c8xx_isr+0x334 sapic_interrupt+0x2c ( SR:8606252783 CR:JAGae17850 ) When the c8xx driver detects a problem with a device, it steps down the transfer rate to a sustainable rate. But the driver fails to step the transfer rate back up to Ultra160 after the problem that caused the step down is fixed. A message like the following is logged in the system log file at step down time: SCSI: Ultra160 Controller at 0/6/2/0: Warning: Data transfer rate stepped down for target 3. Now operating at 5 MB/s (Slow Narrow). Possible causes are improper termination, improper cabling, or malfunctioning hardware. ( SR:8606233087 CR:JAGae02311 ) System panics due to "callout table overflow" with the following stack trace when continuous SCSI bus resets are detected by the driver: panic+0x14 settimeout_for_cpu+0x174 Ktimeout+0x3c c8xx_reset_chip+0x129c c8xx_isrRST+0x94 c8xx_isr+0x15cc sapic_interrupt+0x2c ( SR:8606237636 CR:JAGae06674 ) Process hangs and is non-interruptible with the following message in the system log file: Device violation of Contingent Allegiance PHKL_25014: ( SR:8606213503 CR:JAGad82695 ) Enhancement to add support for SCSI Ultra160 core I/O and add-in bus adapters. This patch is required in order to use these cards. Defect Description: PHKL_30509: ( SR:8606346346 CR:JAGaf07173 ) When the number of bytes transferred by the device is odd and an Ignore Wide Residue is sent by the target at the completion of the I/O, the driver doesn't update the data residual count. This results in improper byte transfers. Resolution: The driver code has been modified to update the residual count when an Ignore Wide Residue message is sent by a target at the end of an odd byte I/O transfer. ( SR:8606351535 CR:JAGaf12340 ) The management processor on MSA30 disk enclosure does not have a dedicated SCSI target ID. It responds to the SCSI ID of the initiator. In order to communicate with the management processor, open(2) on the device node corresponding to the SCSI initiator ID should be allowed. Resolution: Fixed the driver to allow open(2) on the device node corresponding to the SCSI initiator ID. PHKL_29494: ( SR:8606286153 CR:JAGae50096 ) When a domain validation I/O request completes with an error condition, the original I/O request is returned to the upper layer, but the sense buffer for the original I/O request is not populated. This causes the system to panic with a data page fault when this invalid pointer is referenced. Resolution: The driver code has been modified to correctly populate the sense buffer of the original I/O request. ( SR:8606295528 CR:JAGae59213 ) During domain validation, the driver sends a PPR request to the target device. Although the target device responds with a valid PPR response, the Ultra160 driver rejects the response because of an error in the driver code and logs an error message in syslog.log file. Resolution: The driver code has been modified to handle the valid PPR response correctly. ( SR:8606296155 CR:JAGae59766 ) When the number of bytes transferred is greater than 2K, the driver does not update the nexus during reselection. This results in firmware download failure or possible data integrity issue. Resolution: The driver code has been modified to update the nexus during untagged reselection. PHKL_29093: ( SR:8606292714 CR:JAGae56466 ) When negotiating for synchronous narrow mode, the target device responded with parameters that were outside the HBA's supported range of values. On receiving the response, the driver should send a reject message to the target so that it goes to the asynchronous narrow mode. However, due to an error in the driver code, the reject message was not sent and the target device remained in the synchronous mode, whereas, the driver was operating in asynchronous mode. This caused the "First party detected bus hang (HTH)" message to be displayed in the syslog followed by a SCSI bus reset during the data phase. Resolution: The code has been modified to handle the out of range parameters correctly. ( SR:8606297198 CR:JAGae60712 ) When the driver finds that the target device is going to the Data Phase erroneously, it transfers two bytes at a time and tries to get the device to an expected phase before aborting the command. Since narrow devices transfer only one byte at a time, there is a possibility that the target device may change phase after transferring one byte resulting in phase mismatch. The phase mismatch handler in the driver adjusts the data address by one which results in an odd byte aligned address. Later, when this address was accessed, the system panicked with an alignment fault. Resolution: The driver code has been modified to transfer one byte at a time for narrow target devices and two bytes for wide target devices. ( SR:8606298628 CR:JAGae62127 ) a) If the WDTR message is rejected by the target device, the driver failed to send a SDTR message because it assumed that the target was already in asynchronous narrow mode. This resulted in a mismatch in the negotiated parameters between the initiator and the target, causing the HTH timer to timeout during the data transfer and the HTH message was displayed in the syslog. On detecting the HTH timer expiry, the SCSI bus was reset by the driver. b) When displaying the HTH message, one of the chip registers was incorrectly accessed. This caused the system to panic. Resolution: a) The driver code has been modified to send an SDTR message irrespective of whether the driver is already in the asynchronous narrow mode or not. b) The driver code has been modified not to access the chip register when dumping the HTH message. PHKL_27555: ( SR:8606255146 CR:JAGae19473 ) a) The timer was incorrectly being started on abort requests in the select queue. This was leading to an assertion failure on time-out. b) The timer on abort requests was being started even when these requests were not yet given to the chip. Resolution: The driver code has been modified such that : a) Abort requests that are in the select queue are not timed out. b) The timer on abort requests is not started until the request is given to the chip. ( SR:8606267745 CR:JAGae31985 ) The transmit queue array (iocb) index for abort requests was not getting updated. When there was a select time-out on the abort requests, the system panicked when trying to access the uninitialized iocb index. Resolution: The driver code has been modified to correctly update the transmit queue array index for abort requests. ( SR:8606251412 CR:JAGae17477 ) When Domain Validation was in progress and a SCSI Bus reset occurred, the system panicked because it tried to incorrectly modify the if_lun pointer. Resolution: The code has been changed not to modify the if_lun pointer when there is a SCSI Bus Reset. ( SR:8606271666 CR:JAGae35874 ) The postinstall script used ioscan(1M) without the -k option which resulted in actual hardware scanning. This resulted in a long execution time on systems with large configurations. Resolution: The postinstall script has been modified to invoke ioscan(1M) with the -k option. ioscan(1M) with the -k option uses in-kernel cache for the ioscan data. This reduces the time taken by ioscan(1M) on systems with large configurations. ( SR:8606260652 CR:JAGae24975 ) The system panicked because a flag indicating that the DMA set-up is done was not set for auto sense I/O requests even though the resource for the auto sense I/O request was set-up during bus open. Resolution: The code has been changed to set the flag for auto sense I/O requests. ( SR:8606288219 CR:JAGae52150 ) The system panicked with a Data TLB fault, because it was trying to dereference an invalid pointer. Resolution: Checks have been made in the driver so that invalid pointers are not dereferenced. ( SR:8606260893 CR:JAGae25215 ) diskinfo(1M) on the Ultra320 IBM drive reported zero capacity because the driver did not handle untagged I/O requests correctly. Resolution: The code has been modified such that the untagged I/O requests are handled correctly. ( SR:8606265839 CR:JAGae30093 ) ioscan(1M) hung because of a missing SCSI interrupt. The ioscan request and all subsequent I/O requests did not get processed because the timer routine did not clear a flag after it processed the previous interrupt. Resolution: The fix is to clear the flag in the timer routine. ( SR:8606286566 CR:JAGae50505 ) Data integrity problem occurred because one of the card registers was not programmed correctly. Resolution: The card register has been programmed correctly to take care of the data integrity problem. ( SR:8606224108 CR:JAGad93204 ) When A6828A and A6829A SCSI Ultra160 cards are connected in multi-initiator configuration, where more than one initiator tries to arbitrate for the bus, the card may go into hang state which can result in not detecting the Dual Transition (DT) edge of the SCSI clock. The card goes into hang state because the device parameters were written into the card registers before winning the arbitration. This results in the SCSI Gross Error (SGE) and driver resets the SCSI bus. Resolution: The driver has been modified to not write the device parameters onto the card registers when the initiator tries to arbitrate for the bus. Only the device ID is written to the card registers to do the arbitration. The other parameters are set after winning the arbitration. ( SR:8606266332 CR:JAGae30581 ) The system was going into an endless reboot sequence because the initiator did not respond to the REQs sent by the target device. Resolution: The driver has been modified so that the initiator sends ACKs for the REQs received. ( SR:8606262931 CR:JAGae27261 ) A local variable inside a function got corrupted which caused the function to be executed in an infinite loop. The spinlock was held while entering the function and hence the system panicked with a spinlock deadlock because the lock was never released. Resolution: Code has been modified to prevent the variable from getting corrupted. ( SR:8606267106 CR:JAGae31349 ) The postinstall script was exiting unconditionally with a success value in the middle of the script, instead of setting the exitval variable and exiting only at the end of the script. Resolution: The postinstall script has been modified as per scripts architecture recommendations. ( SR:8606229159 CR:JAGad98212 ) When the SCSI bus open fails with any error, the timer is not cancelled. Because of this, the timer pops up and tries to access uninitialized data structures thereby causing the system to panic. Resolution: The code has been changed to cancel the timer if the SCSI bus open fails. ( SR:8606266776 CR:JAGae31021 ) The HTH time-out errors were seen when the system was doing an ioscan(1M) during boot-up. The error was generated because the driver did not re-negotiate for SDTR once the WDTR was rejected by the target device. Resolution: The fix is to re-negotiate for SDTR when WDTR is rejected by the target device. ( SR:8606255080 CR:JAGae19409 ) An assertion failure was wrongly indicated for the LISC_SLEEPING state. It is possible to have multiple threads running on different processors and hence the LISC_SLEEPING state is a valid state. Resolution: Code has been modified to remove the assertion check for LISC_SLEEPING state. ( SR:8606266447 CR:JAGae30695 ) When an abort request times out, currently, the driver ignores the time-out. This could lead to process timeouts and the process appears to have hung forever. Resolution: The driver code has been changed to reset the SCSI bus if an abort request times out, to prevent aborts happening again and again. PHKL_27024: ( SR:8606260875 CR:JAGae25197 ) Upon reception of a SCSI Check Condition from a device, the driver automatically switches temporarily to the untagged queuing mode and sends a Request Sense command. If the setup of this command fails, the driver remains in the untagged queuing mode. This prevents any further IO for that device to be processed, thus hanging the processes accessing this device. Resolution: Switch to the untagged queuing mode only after the setup of the Request Sense command succeeds. ( SR:8606238121 CR:JAGae07162 ) The completion queue can silently wrap around. This causes the driver to miss the completion of 64 IOs. These IOs eventually timeout and the driver aborts them, causing a flurry of messages in the system log file. Resolution: Increase the size of the completion queue so it can hold the maximum number of IOs potentially in progress on the SCSI bus at any point in time. ( SR:8606234217 CR:JAGae03437 ) In some cases, an IO can be found on both the select queue and the nexus table. This can lead to a corruption of the select queue when the IO is returned to the upper layer, which leads to the system panic. The corruption is limited to one kernel data structure and does not cause corruption of user data. Resolution: Remove the IO from the select queue before returning it to the upper layer. ( SR:8606252783 CR:JAGae17850 ) After a target reset occurs, the Domain Validation procedure is initiated only if the device is configured at Ultra160 speed, when it should really be initiated if the initiator is configured at Ultra160 speed. Resolution: Change the Domain Validation criteria to check whether the initiator is configured at Ultra160 speed. ( SR:8606233087 CR:JAGae02311 ) A new timer is set on reception of every SCSI bus reset. This leads to an overflow of the timer table that causes the system to panic. Resolution: When a bus reset occurs, the previous timer, if any, is cancelled and a new timer is set. This ensures that only one timer per SCSI bus exists at any point in time, thus preventing the overflow of the timer table. ( SR:8606237636 CR:JAGae06674 ) When the driver detects the completion of an I/O from a device while this device is in Contingent Allegiance Condition, the driver logs a message, but does not report the completion to the upper layer. This causes the process that initiated the I/O to hang. Resolution: When an I/O completes while the device is in Contingent Allegiance Condition, return the I/O to the requesting layer for further action (typically a retry). PHKL_25014: ( SR:8606213503 CR:JAGad82695 ) Adding support for SCSI Ultra160 on HP-UX 11.00. Resolution: New c8xx driver that supports SCSI Ultra160 core I/O and add-in bus adapters on HP-UX 11.00. Enhancement: No SR: 8606213503 8606224108 8606229159 8606233087 8606234217 8606237636 8606238121 8606251412 8606252783 8606255080 8606255146 8606260652 8606260875 8606260893 8606262931 8606265839 8606266332 8606266447 8606266776 8606267106 8606267745 8606271666 8606286153 8606286566 8606288219 8606292714 8606295528 8606296155 8606297198 8606298628 8606346346 8606351535 Patch Files: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libhp-ux.a(scsi_c8xx.o) /usr/conf/lib/libhp-ux.a(scsi_c8xx_dbg.o) /usr/conf/lib/libhp-ux.a(scsi_c8xx_pdk.o) OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/master.d/c8xx what(1) Output: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/lib/libhp-ux.a(scsi_c8xx.o): scsi_c8xx.c $Date: 2004/03/31 03:35:58 $Revision: r1 1ros/10 PATCH_11.00 (PHKL_30509) /usr/conf/lib/libhp-ux.a(scsi_c8xx_dbg.o): scsi_c8xx_dbg.c $Date: 2002/06/10 17:41:45 $Revision : r11ros/3 PATCH_11.00 (PHKL_27024) /usr/conf/lib/libhp-ux.a(scsi_c8xx_pdk.o): scsi_c8xx_pdk.c $Date: 2003/02/26 15:57:56 $Revision : r11ros/6 PATCH_11.00 (PHKL_27555) OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: /usr/conf/master.d/c8xx: c8xx $Date: 2001/09/10 19:59:08 $Revision: r11ros/1 PATCH_11.00 (PHKL_25014) cksum(1) Output: OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: 1272705762 198368 /usr/conf/lib/libhp-ux.a(scsi_c8xx.o) 945528340 158320 /usr/conf/lib/libhp-ux.a(scsi_c8xx_dbg.o) 3768038414 16312 /usr/conf/lib/libhp-ux.a(scsi_c8xx_pdk.o) OS-Core.KERN2-RUN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP: 1390640948 948 /usr/conf/master.d/c8xx Patch Conflicts: None Patch Dependencies: s700: 11.00: PHKL_30508 s800: 11.00: PHKL_30508 Hardware Dependencies: None Other Dependencies: PHKL_27555: Multi-initiator support is available on Ultra160 SCSI cards with hardware revisions later than A6828-60001 and A6829-60001. PHKL_25014: This patch is one of the two needed to support the SCSI Ultra160 interface on HP-UX 11.00. The two patches are PHKL_25014 and PHKL_25023. These patches may be installed independently of each other and in any order. Without SCSI Ultra160 controller hardware present on the system, these changes will have no impact on your system. Supersedes: PHKL_29494 PHKL_29093 PHKL_27555 PHKL_27024 PHKL_25014 Equivalent Patches: PHKL_30511: s700: 11.11 s800: 11.11 Patch Package Size: 170 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Login as root. 3. Copy the patch to the /tmp directory. 4. Move to the /tmp directory and unshar the patch: cd /tmp sh PHKL_30509 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHKL_30509.depot By default swinstall will archive the original software in /var/adm/sw/save/PHKL_30509. If you do not wish to retain a copy of the original software, include the patch_save_files option in the swinstall command above: -x patch_save_files=false WARNING: If patch_save_files is false when a patch is installed, the patch cannot be deinstalled. Please be careful when using this feature. For future reference, the contents of the PHKL_30509.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHKL_30509.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHKL_30509.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: None