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

Chapter 18 389
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
WAN ACC Sync MUX link drivers. The only other cause is a software
bug; see Appendix A , “Submitting a CR.”
77 ($4D) MESSAGE: Cannot send a port message.
CAUSE: This is a generic error saying that the link driver, module
configurator or deconfigurator, or other module of the link subsystem
encountered an error when trying to send a port message. This error
could be caused by the target module having been already shut down. It
could also be an indication of a more serious system software problem,
and may be followed by a system abort; probably all message frames
have been exhausted by some module running on the system.
ACTION: Severity and side effects of this error are dependent upon the
purpose of the message that was not sent. Attempt to determine the
conditions that led to the error. If it occurred during a shutdown,
possibly this error can be ignored. Otherwise, if the same problem
happens repeatedly, or if a system abort occurs, take a memory dump
and. See Appendix A , “Submitting a CR.”
78 ($4E) MESSAGE: Cannot reset a system timer.
CAUSE: The driver attempted to reset a system timer previously
obtained from I/O Services but encountered an error. This is likely
caused by a bug in system software, or by corruption of the driver’s PDA
context memory.
ACTION: This is a fatal software error. The driver cannot operate
without all necessary timers. If the problem persists, halt the system,
take a memory dump, and reboot. See Appendix A , “Submitting a CR.”
79 ($4F) MESSAGE: Cannot free a system timer.
CAUSE: The driver attempted to release a system timer previously
obtained from I/O Services but encountered an error. This is likely
caused by a bug in system software, or by corruption of the driver’s PDA
context memory.
ACTION: This is a warning that some timer resources may have been
lost. Possibly followed by another error giving more information about
what kind of timer the driver was releasing; check log data for that
error and look it up also. If the problem happens every time, see
Appendix A , “Submitting a CR.”
80 ($50) MESSAGE: Cannot send a port message.
CAUSE: This is a generic error saying that the link driver, module
configurator or deconfigurator, or other module of the link subsystem
encountered an error when trying to send a port message. This error
could be caused by the target module having been already shut down. It
could also be an indication of a more serious system software problem,
and may be followed by a system abort; probably all message frames
have been exhausted by some module running on the system.