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

172 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: This event is informational. No action is required.
13 ($0D) 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
before.
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: Driver timed out waiting for ISR to shut down.
CAUSE: During link shutdown, the driver signaled the ISR to shut
down, then invoked the ISR. The driver then waited repeatedly for the
signal to clear, but it did not.
ACTION: This is an informational warning. The driver gave up waiting,
and continued with the rest of shutdown. If this happens frequently, see
Appendix A , “Submitting a CR.”
16 ($10) MESSAGE: Retrying an operation.
CAUSE: During 100VG-AnyLAN link training, the driver found the ISR
was running, and is waiting again for it to stop running.
ACTION: This is an informational warning. If it occurs repeatedly, the
ISR, or the processor running it, may be stuck; the driver will give up
and will not be able to connect the link. If this happens frequently, see
Appendix A , “Submitting a CR.”
17 ($11) MESSAGE: Cannot release a system plabel.
CAUSE: During the final link-close operation by an upper level
subsystem, the link module deconfigurator encountered an error while
trying to release the link’s write initiator procedure.
ACTION: This is an informational warning that some system memory
resources may have been lost. The module deconfigurator reported an
error, but attempted to continue with the close. If this happens every