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

398 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
ACTION: Probably the link driver returned an error reply when asked to
enable tracing. The driver may have a problem. Check for other,
driver-specific error messages which may give more information about
the problem, and look them up also. If no other errors are found, see
Appendix A , “Submitting a CR.”
216 ($D8) MESSAGE: Driver received an unknown port message.
CAUSE: The driver received a port message which it does not
implement, or containing a function code which it does not implement.
ACTION: This is an informational error only. If this error occurred as
part of a driver reset operation, it may be ignored. The driver did not
attempt to return an error reply to the message sender. That sender
may now be hung, awaiting a reply. Attempt to determine what action
caused the error. Activate link tracing, reproduce the problem, then
stop link tracing and save the resulting NMTCnnnn.PUB.SYS trace data
file, see Appendix A , “Submitting a CR.”
223 ($DF) MESSAGE: One or more bad bind parms passed by upper level
protocol.
CAUSE: This is a generic error, reported when the driver received a bind
(rendezvous) from an upper layer protocol, but the parameters in the
request were not satisfactory to the driver. There are a number of
separate causes; look up the specific sublocation code that was logged,
for more information.
ACTION: All such errors are caused by bugs in the upper layer protocol.
Attempt to determine what protocol was trying to bind, then see
Appendix A , “Submitting a CR.”
224 ($E0) MESSAGE: A data buffer is too long.
CAUSE: During the receive, the driver was asked to prepare a data block
for receive, but the block length or memory allocation was beyond the
driver's configured length.
ACTION: This is an informational error only. If this problem happens
repeatedly and impacts the normal operation, then try configuring the
buffer length to the next higher value and see Appendix A , “Submitting
a CR.”
225 ($E1) MESSAGE: One or more bad utility parms passed to driver.
CAUSE: The driver received a utility register access request from an
upper level tool program such as PLNKUTIL, but the register number
specified was out of the range of legal register values for the selected
register set.
ACTION: This is an informational error only. This problem most likely
occurred while diagnosing some previous problem. Retry the operation
using a legal register number for the register set you have selected.