NS3000/iX Error Messages Reference Manual (36923-90043)

Chapter 18 385
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
14 ($0E) MESSAGE: Cannot release ADA memory object.
CAUSE: During shutdown, the driver requested the I/O system to
release a memory object, but received an error reply in response.
ACTION: This error should not occur. The driver may be confused, or
there is a system problem. However, the driver will ignore the error and
attempt to continue with the shutdown. If this happens frequently, see
Appendix A , “Submitting a CR,”
15 ($0F) MESSAGE: Cannot get ADA memory object.
CAUSE: During initial startup, the driver attempted to obtain a memory
object via the I/O system, but received a bad status in the reply in
response.
ACTION: Probably the amount of frozen memory on the system is very
high; if you have the GLANCE tool you can try to check memory usage.
Try retrying the operation again later, or first terminate some
applications and then retry.
18 ($12) MESSAGE: Cannot close NM logging.
CAUSE: The link module configurator or deconfigurator attempted to
close access to the NM logging facility, but encountered an error.
ACTION: This is an informational warning that the logfile may still be
open. Use of the :SWITCHNMLOG command should not be affected,
however there may be a delay at system shutdown time. If this happens
every time, see Appendix A , “Submitting a CR.”
19 ($13) MESSAGE: Cannot unfreeze a memory area.
CAUSE: After previously freezing a data structure into system memory,
software encountered an error trying to unfreeze the same memory.
ACTION: This is an informational warning that some system memory
resources may have been lost. Software probably continued, ignoring
the error. Software may be confused, or the pointer to the memory area
may have been changed. If this happens every time, see Appendix A ,
“Submitting a CR.”
22 ($16) MESSAGE: Powerfail detected.
CAUSE: The driver was notified of a power failure by the I/O system, or
detected all 1’s on a hardware register read, and, upon checking further,
saw that its hardware I/O address space was disabled, indicating a
powerfail had already occurred.
ACTION: This event is informational. No action is required. Power
failures can occur at any moment. If the driver was executing at the
moment power failed, power then returned, and the driver ran to
completion, noticing this error along the way. Upon exit, the driver was
then officially notified of a powerfail by MPE. The driver then
attempted powerfail recovery, and should now be operating the same as