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

Chapter 18 391
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
may have been altered. If this happens frequently, see Appendix A ,
“Submitting a CR.
87 ($57) MESSAGE: Cannot load a system routine.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator encountered an error while trying to load code
for the write initiator procedure needed for the link type configured in
NMCONFIG.
ACTION: Probably not all software required to operate this type of link
is installed. Software was incorrectly installed, or you may need to
purchase additional software or install newer patches. Reinstall the
link software or contact your Hewlett-Packard Representative for
assistance.
88 ($58) MESSAGE: Cannot open NM logging.
CAUSE: During a link open attempt by an upper-level subsystem, the
link module configurator encountered a positive (error) status when
trying to open NM logging against the link’s subsystem ID.
ACTION: This event is informational. No action is required. The module
configurator cleared the error and will attempt to continue. However,
NM logging may not be available to the link. You may need to install
new NM logging patches. If the problem occurs every time, see
Appendix A , “Submitting a CR.
89 ($59) MESSAGE: Cannot freeze a memory area.
CAUSE: This is a generic error that during a link-open or some other
operation by an upper level subsystem, link software encountered an
error while trying to freeze some data into memory before passing the
driver a pointer to that data.
ACTION: The system may be low on available memory. Try closing any
unnecessary applications or sessions and retry the operation.
90 ($5A) MESSAGE: Did not receive an expected port message.
CAUSE: This is a generic error that during a link-open or some other
operation by an upper level subsystem, link software sent a port
message to the driver, then encountered an error while awaiting the
correct reply message.
ACTION: Severity and side effects of this error are dependent upon the
purpose of the message that was not received. There may be a system
problem with message ports, or the link driver may have sent the wrong
reply message. If this happens every time, see Appendix A ,
“Submitting a CR.
107 ($6B) MESSAGE: Cannot create a buffer pool.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator encountered an error while trying to create an