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

Chapter 17 373
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
reproduce the problem, then stop link tracing and save the resulting
NMTC####.PUB.SYS file for analysis by Hewlett-Packard, and see
Appendix A , “Submitting a CR.”
9480 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: The driver finished transferring a data frame, but encountered
an error while trying to send the frame to an upper layer protocol via a
port message (“Cause” = 32-bit status returned by the call to send_msg).
ACTION: This error is reported at a low level, where the actual send
fails. It should be followed by a another error giving more information.
Locate that error and look it up also. The driver will now attempt to
clean up and continue.
9510 CLAS0001 MESSAGE: Error from upper layer protocol read completor.
CAUSE: The driver finished transferring a data frame and passed it to
an upper layer protocol, but the protocol’s read completor returned an
error which was not one of the expected, legal errors the driver was able
to handle (“Cause” = 32-bit status returned from the read completor).
ACTION: This is an informational error only. The driver incremented a
statistic, logged the error, then attempted to free the read buffer and
continue. However, the protocol may not have received the inbound
frame, therefore some applications could be hung.
There may be a problem in the upper layer protocol. Also, if the protocol
had already freed the buffer, this may have resulted in a SysAbort from
the Buffer Manager. If the problem occurs frequently, start link tracing,
reproduce the problem, then stop link tracing and save the resulting
NMTC####.PUB.SYS file for analysis by Hewlett-Packard, and see
Appendix A , “Submitting a CR.”
9540 CLAS0001 MESSAGE: Link common reported an inbound buffering problem.
CAUSE: After completing a read and delivering a data buffer to an
upper layer protocol, the ISR encountered an error when trying to refill
the SAP’s buffer cache. (“Cause” = 32-bit status from Lnk_buf_refill).
ACTION: This message is informational; this might be because of
contention on the system for buffers. However, if the underlying
contention or problem persists, the SAP may run out of buffers and no
longer be able to receive data over the network.
If upper level network subsystems appear hung, try shutting them
down manually, or shutting down and restarting the network link; if
the problem persists, see Appendix A , “Submitting a CR.”
9570 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver finished transferring a diagnostic loopback data
frame, but then discovered it was either not in loopback mode anymore,
or there was no pending diagnostic request message (“Cause” = 32-bit
encoded value, giving driver current state: Hewlett-Packard use only).