
PROBLEM: (89371, 89509, INPUT) (PATCH ID: TCR520-021)
********
PROBLEM: (89371)  (PATCH ID: )
   The following message on the console or in /var/adm/messages;
   "panic (cpu 0) ics_unable_to_make_progress: heartbeat checking blocked"
   Typical stack trace;
crash> tf
>  0 boot                 src/kernel/arch/alpha/machdep.c : 2644
   1 panic                src/kernel/bsd/subr_prf.c : 1401
   2 ics_mct_llassert_not_stalled  src/kernel/tnc_common/tnc_ics/ics_mct
                                   /ics_mct_llmgmt.c : 2512
   3 cnx_have_quorum      src/kernel/cnx/cnx_tx.c : 338
   4 describe_config      src/kernel/cnx/cnx_agent_action.c : 3292
   5 cnx_get_info         src/kernel/cnx/cnx_agent_action.c : 1009
   6 syscall              src/kernel/arch/alpha/syscall_trap.c : 725
   7 _Xsyscall            src/kernel/arch/alpha/locore.s : 1814
PROBLEM: (89509)  (PATCH ID: )
   The following message on the console or in /var/adm/messages;
   "panic (cpu 0): ics_unable_to_make_progress: input thread stalled"
   Typical stack trace;
crash> tf
>  0 boot                 src/kernel/arch/alpha/machdep.c : 2644
   1 panic                src/kernel/bsd/subr_prf.c : 1401
   2 ics_mct_llassert_not_stalled  src/kernel/tnc_common/tnc_ics/ics_mct
                          /ics_mct_llmgmt.c : 2505
   3 cnx_have_quorum      src/kernel/cnx/cnx_tx.c : 338
   4 describe_config      src/kernel/cnx/cnx_agent_action.c : 3292
   5 cnx_get_info         src/kernel/cnx/cnx_agent_action.c : 1009
   6 syscall              src/kernel/arch/alpha/syscall_trap.c : 725
   7 _Xsyscall            src/kernel/arch/alpha/locore.s : 1814


PROBLEM: (89757) (PATCH ID: TCR520-023)
********
PROBLEM: (89757)   (PATCH ID: )
   The follwing message on the console or in /var/adm/messages;
   "ics_mct: Node arrival waiting for out of line node down cleanup to 
   complete. MC node n" (where n is one of the cluster node numbers which
   is rebooting)
   Another symptom can be RPC's do not complete after MC errors.


PROBLEM: (92453) (PATCH ID: TCR520-139)
********
This patch addresses a problem that occurs when higher priority threads
running on a cluster member block the internode communication service 
Memory Channel transport(ics_ll_mct) subsystem's input thread 
(ics_input_thread) from execution. 
When the problem occurs, the member panics with the following string:
panic (cpu x): ics_unable_to_make_progress: input thread stalled


PROBLEM: (ES_G03236, TKT300910, ES_G03322) (PATCH ID: TCR520-145)
********
This patch fixes numerous panics and hangs with internode communication
subsystem sequence numbers. It can manifest itself in ics_mct:
unable_to_make_progress panics, lock panics, or sequence problem panics.


PROBLEM: (DEK055425) (PATCH ID: TCR520-127)
********
This patch fixes a panic with the string 'rcnx_status: different node.'
 0 thread_block : 3102
 1 thread_preempt : 4962
 2 smsync_to_readyq : 6227
 3 bs_bflush : 4434
 4 bs_bfdmn_flush_bfrs : 6541
 5 mntflushbuf : 1877
 6 cms_flushbufs : 9263
 7 boot : 2744
 8 panic : 1334
 9 rcnx_status_V1 : 4155
10 svr_rcnx_status_V1 : 76
11 icssvr_daemon_per_node : 1213


PROBLEM: (83248) (PATCH ID: TCR520-146)
********
This patch fixes a boot hang on 'ics_mct: Node arrival waiting for out of line
node down cleanup to complete.'


PROBLEM: (94202, DSATM29S2) (PATCH ID: TCR520-200)
********
This patch fixes a Clusterwide hang when there is lots of Memory Channel
traffic.


PROBLEM: (94792) (PATCH ID: TCR520-211)
********
This patch addresses an assertion panic when a user program passes an invalid
pointer to the kernel via sys_call.  The following message on the console or in
/var/adm/messages;
PANIC: "cmn_err: CE_PANIC: ICS MCT Assertion failed: (ectx->el_flags & (1<<0)) 
== 0, file: ics_mct_oolencoder.c line: xxxx"


PROBLEM: (93293) (PATCH ID: TCR520-172)
********
This patch addresses an assertion panic that can occur when another member is
in the process of going down.  The following message on the console or in 
/var/adm/messages;
"cmn_err: CE_PANIC: ICS MCT Assertion failed: icsmc_na[mc_node].ni_ptr != 0L,
 file: ics_mct_llmgmt.c. line xxxx"

Typical stack trace;

    crash> tf -q
    0 stop_secondary_cpu
    1 panic
    2 event_timeout
    3 printf
    4 panic
    5 cmn_err
    6 ics_mct_ref_rel
    7 ics_mctcli_llwaitfornothrottle
    8 icscli_waitfornothrottle
    9 icscli_handle_get
   10 cli_rcfsrec_ics_begin_lock_xfer
   11 cfs_rec_recover_filesystem
   12 cfs_rec_start_server


PROBLEM: (117-1-20383) (PATCH ID: TCR520-161)
********
This patch corrects an ICS handle memory leak.


PROBLEM: (94631, GB_G04797, GB_G03887, GB_G04326) (PATCH ID: TCR520-260)
********
This patch addresses a memory leak in the ICS memory channel transport.  The
leak only occurs in the case where a node sending a message/RPC to another node
receives an error indicating the destination node was invalid (down or node 
doesn't exist). A symptom of this could be a system hang in an extreme case
(e.g. a user level fuction looping many times sending to a nonexistant node).


PROBLEM: (94280) (PATCH ID: TCR520-262)
********
This patch addresses a node hang that occured during testing of Memory Channel
cable pulls.  When a Memory Channel cable is pulled, the node is taken down, 
the cable is plugged back in, and the node is rebooted.  This sometimes causes 
one of the members in the cluster to hang.


PROBLEM: (95974, DEK100417, FS.96178) (PATCH ID: TCR520-259)
********
This patch addresses a panic when a node is joining the cluster. A node
recognizing the joining node panics while it is trying to establish channel
connection with the peer node. The following message is displayed on the
console or in /var/adm/messages;
panic (cpu x): ics_mct: rx conn 3



