PROBLEM: (TKTR32485, QAR 51577) (Patch ID: OSF410-400253) ******** This patch is an upgrade/replacement for the OTTO/OPPO ATM driver and fixes a number of flow control and signalling problems. If you are seeing "No Buffer Space" messages, experiencing pauses or hangs when receiving data on signalling/ilmi pvc's, or have any problems with FLOWMASTER flow control with CLIP or LANE over ATM, you should install this patch. PROBLEM: (KAOQ51240, QAR 53078) (Patch ID: OSF410-400286) ******** This patch contains performance enhancements to the ATM OTTO driver when greater than 300 VC's are configured. This replacement driver users hash buckets to improve search time in the VC data structures resulting in significant performance gains. PROBLEM: (ZPOBB1275/HPAQA05DF/QAR 56054) (Patch ID: OSF410-400425) ******** This patch fixes two problems with the ATM 350 driver. On reboot, a panic could be encountered before getting into single user mode. The panic would occur inside the ltaintr routine and this routine would be noted in the dump stack trace. This problem was seen on Personal Workstation 500ua and the ATM 350 card. The second problem is a panic: thread_block: interrupt level call when rt_preempt_opt (REALTIME preemption) is enabled. A typical stack trace would look like this for the top of the stack: panic thread_block() thread_preempt() panic thread_block() unix_release_force() unix_release() schedtransmit() softclock_scan() or this: panic thread_block() thread_preempt() panic thread_block() unix_release_force() unix_release() ottooutput() atm_cmm_send() PROBLEM: (HPAQA05DF/ZPOBB12755/QAR 56054) (Patch ID: OSF410-400432) ******** This patch is an upgrade enhancement to the ATM350 driver. This patch prevents panics in driver routines that can be called from different interrupt levels. PROBLEM: (TKTB23716/QAR 55019) (Patch ID: OSF410-405174) ******** This patch fixes a panic from the ATM OTTO/OPPO driver. The panic message is "ltaintr panic: no TX pkt" The stack trace is: 0 boot() 1 panic() 2 ltaintr() 3 intr_dispatch_no_post() 4 _XentInt() 5 swap_ipl() 6 boot() 7 panic() 8 ltaintr() 9 intr_dispatch_no_post() 10 _XentInt() 11 SAddPstMsg() 12 amEncU8() 13 amEncTkns() 14 amEncPduHdr() 15 amBldMsg() 16 amGenPdu() 17 amComM07SND() 18 amActvConTbl() 19 AmLiAsdDatInd() 20 AsUiAsdDatInd() 21 asV3xAa4Sx_y() 22 asV30ProcessSdPdu() 23 asV30Pdu8S4() 24 AsLiAalDatInd() 25 atm_sig_process_receive() 26 atm_sig_event_process() This panic occurs easily when the load on ATM is high and the following message will be seen in /var/adm/messages file: (your destination and source addresses will be different) Destination Address: "4707900000000000a03e0010" Call Duration: 0 seconds ATM LANE - Connection Released, cause = 3 VC released on interface lta0:Source Address: "39392f816879fffff010313802b8053180" PROBLEM: (EVT102770) (Patch ID: OSF410-405550) ******** This patch corrects a problem which can result in a cache inconsistency and a 'lta: TX queue broken' system panic. The following is a representative stack trace: panic : lta: TX queue broken 0 boot 1 panic 2 ltaintr 3 intr_dispatch_post 4 _XentInt 5 swap_ipl 6 boot 7 panic 8 ltaintr 9 intr_dispatch_post 10 _XentInt