PROBLEM:        (MCPMC39C7)     (Patch ID: ASE130-002)
*******
This fixes a problem where SCSI host pings would drop out for 30 seconds.
This drop out would occur from 0 to 20 or more times a day.

The problem only happens in ASE environments with 3 or more members.

You would find SCSI host ping alert messages seen in the daemon.log file.

The message sequence looks something like this:

Dec  7 13:59:12 alpha3 DECsafe: local HSM Info: iobus path alpha1 \
 (163.35.136.3) state change old = PING_OK new = PING_NOT_OK_INTERFACE_UNKNOWN
Dec  7 13:59:12 alpha3 DECsafe: local HSM Warning: Can't ping alpha1 over
 the SCSI bus
Dec  7 13:59:12 alpha3 DECsafe: local HSM ***ALERT: network ping to host \
 alpha1 is working but SCSI ping is not
                :
                :
Dec  7 13:59:42 alpha3 DECsafe: local HSM Info: iobus path alpha1 \
 (163.35.136.3) state change old = PING_NOT_OK_INTERFACE_UNKNOWN new = PING_OK

Notice the 30 second time difference between when the SCSI pings stop working
and when they start working again.

Note that there are no error messages in either the binary errlog or
the kern.log file associated with the SCSI ping drop outs. The SCSI ping
dropouts appear to happen for no reason.

PROBLEM:        (QCABBY052)     (Patch ID: ASE130-014)
*******
This fixes a problem where the system will panic with a panic string of
"kernel memory fault" with the following stack trace:

        0 boot()
        1 panic()
        2 trap()
        3 _XentMM()
        4 am_select()
        5 spec_select()
        6 vn_select()
        7 undo_scan()
        8 do_scan()
        9 select()
        10 syscall)
        11 _Xsyscall()

PROBLEM:        (ZPOB91873, QAR 46416)  (Patch ID: ASE130-014)
*******
This fixes a problem where a service will not failover to another member
because it can not reserve SCSI devices.  The SCSI reservations fail
because Unit Attention messages depleted the retry count.  This also
adds logging of Unit Attention events in binary.errlog from the
 SCSI_reserve() and SCSI_release() functions of the Availability Manager.

PROBLEM:        (MCPM47960)     (Patch ID: ASE130-014)
*******
This fixes a problem where the system will panic with a panic string of
"kernel memory fault" with the following stack trace:

        0 boot()
        1 panic()
        2 trap()
        3 _XentMM()
        4 bcopy()
        5 am_ping_complete()
        6 am_ping_complete_thread()

PROBLEM:	(QAR 57350)	(Patch ID: ASE130-024)
********
This patch fixes a problem where, under certain conditions like SCSI aborts
and resets, it's possible for host target mode CCB's to be issued multiple
times.  This can corrupt the SIM nexus queue and result in system panics
("simple_lock: time limit exceeded") on multi-processor, and system hangs
on single processor systems.  A sample stack trace for the panic may look
like:

  0 stop_secondary_cpu()
  1 panic("event_timeout: panic request")
  2 event_timeout()
  3 xcpu_puts()
  4 printf()
  5 panic("simple_lock: time limit exceeded")
  6 simple_lock_fault()
  7 simple_lock_time_violation()
  8 sim_action()
  9 xpt_sim_func()
  10 xpt_action()
  12 cdisk_complete()
  13 xpt_callback_thread()

PROBLEM:	(QAR 57380, MCPMC059X)	(Patch ID: ASE130-024)
********
This patch fixes a kernel memory fault panic caused by a race condition
when the AM de-initializes and removes the device structures.  

A sample stack trace might look like:

  0 boot()
  1 panic("thread_block: simple lock owned")
  2 thread_block()
  3 thread_preempt()
  4 boot()
  5 panic("kernel memory fault")
  6 trap()
  7 _XentMM()
  8 am_find_device()
  9 SCSI_cleanup_device()
  10 am_dereg_notification_devices()
  11 am_de_initialize()
  12 am_handle_ioctl()
  13 am_ioctl()
  14 spec_ioctl()
  15 vn_ioctl()
  16 ioctl_base()
  17 ioctl()
  18 syscall()
  19 _Xsyscall()