Advanced Communications Controller B.03.32.00 Release Notes

Advanced Communications Controller B.03.30 Release Notes
Defect Fixes in Release ACC B.03.30.00
Chapter 2 25
Defect Fixes in Release ACC B.03.30.00
• JAGad16980
Symptoms: pdisplay runc on ports 2 and 7 of the 2/8-port cards does not work and outputs
the following error:
Error: Port 7 exceeds the maximum allowed for the card type.
Defect/Fix: Whenever you try to use the runc command to configure the last port of any
2-port or 8-port ACC card, the command fails with an error. This defect was caused by a
logic error in the port validation code. This defect has been corrected.
• JAGad13781
Symptoms: zmasterd cold startup or x25init failure indicating insufficient HP-UX
memory for the operation.
Defect/Fix: The root cause for these failures was the code holding a spinlock when calling
MALLOC with wait. If MALLOC needed to sleep in this case, it would return a NULL
pointer which normally indicates no memory available. The fix is to unlock the spinlock
before calling the MALLOC macro.
• JAGad09926
Symptoms: x25init fails with the following message:
[x25stop] X.25 interface zx25m0p2 has been stopped
ixetune: IXE_SNREG ioctl failed: Invalid argument
Too many IXE lines configured in /etc/netconf
Defect/Fix: The fix is in the application using X.25. If an application is using the X.25
subsystem with ACC, and if the "zmasterd stop" or "zmasterd kill" command is issued, a
"x25stop -K" command must be issued. The "x25stop -K" command should be issued after
doing the zmasterd stop/kill command. This is necessary because the zmasterd stop/kill
command deallocates the ZCOM data structures and there is no way the X.25 subsystem
would know that the data structures have been deleted. If the "x25stop" command is not
given, then all successive "x25init" commands may give error messages stating that the
"x25tune" command failed.
• JAGad13782
Symptoms: Multiple connections over ACC/X25 are made. After 5 days of intensive stress
on the machine it needs to be rebooted because of a memory leak in the 512 bucket. The
problem can be reproduced on all possible hw systems running HPUX 11.00.