PROBLEM:	(CLD ZUO101032)		(Patch ID: OSF410-400138)
********
This patch fixes a panic with the message "ltaintr: no TX pkt".  An example 
stack trace is shown below:

   0 boot()
   1 panic(s = 0xfffffc000065e1f0 = "ltaintr: no TX pkt")
   2 ltaintr()
   3 kn15aa_dispatch_iointr()
   4 _XentInt()
   5 swap_ipl()
   6 boot()
   7 panic(s = 0xfffffc000065e1f0 = "ltaintr: no TX pkt")
   8 ltaintr()
   9 kn15aa_dispatch_iointr()
  10 _XentInt()
  11 gh_zero_memory()
  12 idle_thread()

The panic is a result of the ATM ILMI component overflowing a message buffer.
It will only occur for certain patterns of ATM addresses, and is most likely
to happen when ATM Classical IP is in use.

This patch may also fix other ILMI interoperability problems that do not
result in panics.

PROBLEM:        (CLD ZUO101032)         (Patch ID: OSF410-400138)
********
When the default UNI Version 3.0 signalling is used, it can sometimes take a 
very long time (1.5 minutes or more) for ATM connections to be re-established 
after a network interruption (e.g. a disconnected cable).

This patch changes the default recovery timer and greatly speeds up 
re-connection following an interruption.

PROBLEM:	(QAR 49699)		(Patch ID: OSF410-400138)
********
This patch fixes a possible kernel memory fault panic that might occur on an 
ATM ARP server.  The panic might also occur if a remote system tries to 
establish any ATM connection with invalid signalling parameters.  The panic 
occurs in the routine otto_manage_delvc().

PROBLEM:				(Patch ID: OSF410-400138)
********
This patch fixes a possible interoperability problem with IBM 8260 switches
(certain firmware revisions).  The problem prevents the Digital UNIX system
from joining an emulated LAN.  The system repeatedly rejects of the 
incoming point-to-multipoint VC connections with a cause value of 100.

This problem could also occur any time a remote system attempted a connection
where the Forward and Backward SDU sizes were not equal.

PROBLEM:  (DEKBC1129)	 (Patch ID: OSF410-400219)
********
This problem is caused by corruption in an internal queue of the LANE ARP
code.  The symptoms are either a system hang in process_event_queue() or
one of the following kernel memory fault stack traces:

        0  boot()
        1  panic("kernel memory fault")
        2  trap()
        3  _XentMM()
        4  event_queue_insert()
        5  la_arp_update()



        0  boot()
        1  panic("kernel memory fault")
        2  trap()
        3  _XentMM()
        4  process_event_queue()
        5  la_arp_refresh_callback()
        6  timer_process()

PROBLEM:  (TKTB26124)	 (Patch ID: OSF410-400219)
********
This problem is cause by incorrectly keeping track of the refernce counts of 
the internal ATM ESI structures.  The following is the stack trace of the kernel
panic:

        0 boot()
        1 panic("ATM ESI CLONE DELETE BOTCH")
        2 atm_cmm_esi_cleanup()
        3 atm_cmm_collector()

PROBLEM:  (TKTB26122)	 (Patch ID: OSF410-400219)
********
The symptoms of this problem vary depending on whether or not patch 138.00
is installed.  The problem is triggered by shutting down signaling (i.e.,
issuing the following command "atmsig down driver=xxxx") and then bringing
signaling back up (i.e., "atmsig up  driver=xxxx") when LANE is active.
Without patch id 138.00 installed the following kernel memory fault will result:

           0 boot
           1 panic(s = 0xfffffc00006c7680 = "kernel memory fault")
           2 trap()
           3 _XentMM()
           4 otto_manage_delvc()
           5 otto_manage()
           6 atm_cmm_zombiefy_vc()
           7 atm_cmm_new_call()
           8 AmUiAmtConInd()
           9 amUsrM05S00()
          10 amActvConTbl()
          11 AmLiAsdDatInd()
          12 AsUiAsdDatInd()
          13 asV3xAa4Sx_y()
          14 asV30ProcessSdPdu()
          15 asV30Pdu8S4()
          16 AsLiAalDatInd()
          17 atm_sig_process_receive()
          18 atm_sig_event_process()

With patch 138.00 installed, LANE will not restart unless the following
commands are issued:

         "atmconfig down driver=xxxxx"
         "atmconfig up driver=xxxxx"

PROBLEM:  (TKTB25174)	 (Patch ID: OSF410-400219)
********
A system panic is caused by trying to funnel a thread which is in interrupt
context.  The kernel stack trace associated with this problem is as follows:

          0 boot()
          1 panic("thread_block: interrupt level call")
          2 thread_block()
          3 unix_release_force()
          4 unix_release()
          5 cm_rcv()
          6 atm_cmm_receive()
          7 ottoread()
          8 ltaintr()
          9 intr_dispatch_post()
          10 _XentInt()


FILE(s):

/sys/BINARY/atm.mod			subset OSFATMBIN410
CHECKSUM: 42593    325
/sys/BINARY/atmip.mod			subset OSFATMBIN410
CHECKSUM: 39233    241
/sys/BINARY/lane.mod            	subset OSFATMBIN410
CHECKSUM: 65378    348
/sys/BINARY/uni3x.mod			subset OSFATMBIN410
CHECKSUM: 43862    935
/usr/sys/include/atm/sys/atm_smi.h	subset OSFATMBINCOM410
CHECKSUM: 07815      7	RCSfile: atm_smi.h	RCS: 1.1.9.3
/usr/sys/include/atm/cmm/cmm.h          subset OSFATMBINCOM410
CHECKSUM: 39495     25  RCSfile: cmm.h       RCS: 1.1.15.4
