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

372 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
9390 CLAS0001 MESSAGE: Internal driver error.
CAUSE: While processing a received frame, the ISR detected an
unsupported packet format. (“Cause” = 32-bit status returned from
Lnk_recv_strip_hdr). Because this should have been caught during
the rendezvous with the upper level system (SAP), this is an
unexpected error condition.
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 HP, and see Appendix A ,
“Submitting a CR.”
9420 CLAS0001 MESSAGE: Internal driver error.
CAUSE: While processing a received frame, the ISR encountered an
error when trying to swap buffers between the driver’s receive pool and
the SAP’s buffer pool. (“Cause” = 32-bit status from
Bmgr_io_exchange_pb).
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 HP, and see Appendix A ,
“Submitting a CR.”
9450 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,