Advanced Communications Controller B.03.32.03 Release Notes

nacc2_end_io+0x5b0
nacc2_isr+0x1244
sapic_interrupt+0x2c
mp_ext_interrupt+0x3f0
ivti_patch_to_nop3+0x0
sul_pcxu_stop_here+0x0
N2Z_F0_rserv+0x144
sq_wrapper+0x94
str_sched_mp_daemon+0x174
str_sched_daemon+0x298
im_mpnetstr+0x28
DoCalllist+0x3c
main+0x28
$vstart+0x48
istackatbase+0x88
Defect/Fix: This problem happens due to synchronization issue. During data transmission,
if the application issues a disconnect, this request can be taken by another thread and clean
the queues. As a result, when the last transmission of data is done, it tries to detach the
message from the queue which is already made NULL by other thread causing the system
to panic. This problem is avoided by checking queue head before detaching the message.
• JAGaf02574
Symptoms: System Panics with Data Page Fault with following stack trace.
stack trace for event 0
crash event was a panic
panic+0x6c
report_trap_or_int_and_panic+0x94
interrupt+0x208
$ihndlr_rtn+0x0
N2Z_F_data_ind+0x20
N2z_iev_pass_data_up+0x14c
N2z_ReadEvent_Recvd+0x20f8
Zc_putq+0x64
nacc1_receive_data+0x1a4
nacc1_pass_rxdata+0x8c
nacc1_cmplt_read+0x838
nacc2_complete_req+0x34a8
nacc2_end_io+0x580
nacc2_isr+0x126c
sapic_interrupt+0x2c
mp_ext_interrupt+0x26c
ivti_patch_to_nop3+0x0
idle+0x46c
Defect/Fix: It happens while processing inbound data of an established Virtual Circuit (VC).
The panic was due to dereferencing NULL valued inbound data address variable. The
address variable got NULL due to synchronization problem. The fix is done by adding a
check point and changing the code to make proper synchronization.
• JAGaf05994
Symptoms: System Panics with Data Page Fault with following stack trace.
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0xd9c
nokgdb+0x8
N2Z_F0_conn_conf+0x5a4
N2Z_F0_wput+0xebc
putnext+0xcc XSO_F_putnext+0x44
streams_put+0xe8
XSO_F0_a_connect_resp+0x268
Patches and Fixes for this Version 13