ACC Release Notes for the B.03.01 Release

15
Advanced Communications Controller Release Notes for the B.03.01 Release
Known Problems and Workarounds for ACC Products
configuration. When this happens, zmlog prints an error
message in the ZCOM error log file and ignores the log buffer.
This problem is very difficult to reproduce in the lab, hence the
cause is still unknown. It is suspected that the cause is
contention in the driver, when multiple pieces of driver codes
are trying to log messages and hit some unprotected critical
sections.
The LDM driver is modified to detect this log buffer corruption.
When this happens, it sets up the “overrun” error code to carry
some debug information, then fixes up the log buffer and
returns a consistent log buffer to zmlog. On return, zmlog
should display a negative overrun error code. zmlog is also
modified to print the log buffer in hex to the log file when this
happens.
These two changes work independently. They catch and detect
the problem in different spots. When this problem occurs
again, either one of these code changes can detect the problem
and show more information about the real cause.
• Using driver trace utilities
ACC comes with the utilities to control and display the driver
runtime trace messages for troubleshooting purposes. These
utilities may also be used to display trace messages from
HP-UX crash dumps (-d option). But they require the crash
dumps to be in 10.x COREDIR format. As a workaround, you
should use crashutil to convert the 11.00 dump files to 10.x
format. For example, assume the 11.00 dump files are in
crash.4:
# crashutil -v COREDIR /var/adm/crash/crash.4 \
/var/adm/crash/crash.400
# nacc_trc -d400