Advanced Communications Controller B.03.32.03 Release Notes

XSO_F_handler+0xdb0
XLS_F_handler+0x14a8
XSO_F_handler+0x408
XPR_F_pr_usrreq+0x540
soaccept+0x590
sodequeue+0x254
accept+0x22c
syscall+0x28c
$syscallrtn+0x0
Defect/Fix: This problem happens when the upper layers do an accept when there is no
incoming call. The driver tries to send a connect confirmation, but the connect structures
are not filled completely(which is filled when there is an incoming call)causing the system
to panic. Code changes have been made so that, the driver before continuing with the call
accept checks Nz_INB_CALL flag. If it is not set, the call is disconnected.
• JAGaf31334
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
trap+0xedc
thandler+0xd20
N2z_Disable_ZLUs+0x474
N2z_shutdown_x25_subsys+0x618
N2Z_F0_close+0x820
close_wrapper+0x38
csq_protect+0x138
osr_pop_subr+0x3a0
osr_close_subr+0x330
hpstreams_close_int+0x388
hpstreams_close+0x2c
call_open_close+0x28c
closed+0xe4 spec_close+0x64
vn_close+0x48 vno_close+0x20
closef+0x64
exit+0xc3c
rexit+0x24
syscall+0x750
syscallinit+0x55c
Defect/Fix: The panic was happened due to dereferencing NULL valued return value from
N2Z_GET_VCP macro. Resolution: The fix is done by changing N2Z_GET_VCP macro to
check the content of vctbl (Virtual Circuit table) against NULL value.Also modified the
functions which uses N2Z_GET_VCP macro to check the return value for NULL.
• JAGaf33949
Symptoms: For TCP/IP over X.25ACC network ,Successive ping's after the first ping always
fails to place an outbound call.
Defect/Fix: On issuing a ping, it opens a stream of type UNKNOWN for placing an outbound
call. Once the call is closed, The stream's type is not moved properly back to UNKNOWN
and is left inconsistent. Successive pings try to reuse the inconsistent stream to place an out
bound call and hence always fails to do so. Problem is fixed by moving the stream to the
proper state by setting the correct stream type on receiving the VC_DOWN event.
• JAGae53365
Symptoms: ACC not recovering after sending RNR(Receiver Not Ready).
Defect/Fix: After sending an RNR, ACC/X.25 driver did not send RR to clear the flowcontrol
i.e. NLI2ZCOM driver was not coming out of flowcontrol mode. This caused the
communication to be in a pending (hung) state until another event clears the flowcontrol
14 Advanced Communications Controller B.03.32.03 Release Notes