Advanced Communications Controller B.03.32.00 Release Notes

Patches and Fixes for this Version

Chapter 1 9

Defect Fixes in ACC Version B.03.32.00

This release fixes the following defects.

• JAGad28181

Symptoms: Frames larger than 8220 bytes are discarded when received by the

HDLC.FRAME layer (level-1).

Defect/Fix: The ACC HDLC/LAP-B (ABM) User’s Guide states that the maximum frame

size is 10066 bytes. The limit has been raised to that value.

• JAGad54596

Symptoms: When x25init is run against an X.25 link repeatedly, a DMA timeout or

firmware error may result. This error could also happen when using other protocols such

as HDLC-LAPB or HDLC-LAPD.

Defect/Fix: During the disable processing, a NULL pointer is incorrectly de-referenced by

the code in unstdt_build(). A check has been added to avoid this de-reference.

• JAGab67173

Symptoms: zconfig() portsc request hangs if a card is not available.

Defect/Fix: During a card startup, if the startup fails, zmon leaves the card in whatever

state it was in previously (e.g. being Reset). This allows API requests to be accepted by

LDM and DAM to operate on a non-functioning mux. If the API request is a

zconfig/zport request, it is never completed and therefore it hangs the calling program.

The zmon restart mechanism has been modified to fix this defect.

• JAGac77692

Symptoms: On systems with unstable firmware/hardware (one that can startup, but then

fails), the card crashes and the ZMON restart mechanism can get confused. This may

result in an un-stoppable ZCOM subsystem, or a system panic. Manually stopping the

ZCOM subsystem when ZMON is busy in card restarts can also cause this situation.

Defect/Fix: The problem is caused by the driver making card restart requests to ZMON,

while ZMON is still retrying card restart or card shutdown. These multiple requests can

confuse ZMON and hence leave the system in a unstable state. Two changes have been

made to stop the various problems.

— At the end of a successful card “stop” or “restart”, all pending card restart requests are

ignored. This prevents ZMON from being swamped by the card requests.

— When a card “shutdown” request competes and loses to a card “restart” request, the

“shutdown” request retries immediately. Normally, it should win the IFT back and the

other card restart requests will give up immediately.