Advanced Communications Controller B.03.32.03 Release Notes

• JAGaf86284
Symptoms: System panics with a Data Page Fault and the stack trace looks as below:
panic+0x6c
report_trap_or_int_and_panic+0x94
trap+0xf04
thandler+0xd20
N2Z_F0_L_GETSTATS_ioctl+0x268
N2Z_F0_wput+0x2fe0
putnext+0xcc
wait_iocack+0x6c str_istr_ioctl+0x2d4
Defect/Fix: The problem happens when x25stat is issued on disabled terminals. This is
because the function which gets the status of the terminals does not check whether the
terminal is disabled and issues a request to firmware for statistics. The Firmware will not
upload statistics for disabled terminals and therefore panics. The fix is to return immediately
if statistics are requested for a disabled terminal without querying the firmware.
• JAGae40056
Symptoms: System panics with a Data Page Fault and the stack trace looks as below:
panic+0x6c
report_trap_or_int_and_panic+0x94
trap+0xedc
nokgdb+0x8
N2Z_F0_G_GETSTATS_ioctl+0x1b0
N2Z_F0_wput+0x2aec
putnext+0xcc
wait_iocack+0x6c
Defect/Fix: The problem happens when N2Z_F0_G_GETSTATS_ioctl tries to get the link
statistics of a port which has already been stopped. This is because the link zlu data structures
of the stopped port are in an inconsistent state. The fix is to check if the link zlu data structures
of the stopped port are valid or not, if they are not valid N2Z_F0_G_GETSTATS_ioctl will
return with an error.
• JAGae08952
Symptoms: Card reset occurred with the following message in /var/opt/acc/log/.tlog file -
05:31:49 zcom 00212 Card 0 write completion with none outstanding! Port number = 6
Terminal number = 101. 05:31:49 zcom 00232 Card 0 - Firmware failure induced (card reset)!
Defect/Fix: When zx25d driver issues a Clear Request on a VC, the driver flushes the High
and Low priority message queue of the corresponding ZLU, even if the DMA is active for
that ZLU. Hence on DMA completion the DAM driver does not find any messages in the
above queues to be moved to Unacknowledged queue. After some time when the DAM
driver receives a transmission completion for previously DMA'ed message, it enters the
FIRQ processing. In FIRQ processing, it searches for the message in the Unacknowledged
queue, and since the DAM driver did not find any messages earlier in High and Low priority
message queues to be moved to Unacknowledged queue, it logs an error with "write
completion with none out standing" and "Firmware failure induced (card reset)" messages
in .tlog file and crashes the card. This issue has been taken care by checking in zx25d driver
whether DMA is active for that ZLU before flushing the High and Low priority queues. If
the messages were flushed while DMA was active, in transmission completion path code
change has been done to distinguish whether it's a real firmware failure or not and hence
not to crash the card in the above scenario.
• JAGae69940
Symptoms: System Panics with the following stack trace.
panic+0x14
report_trap_or_int_and_panic+0x4c
trap+0xeb0
10 Advanced Communications Controller B.03.32.03 Release Notes