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

344 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
problem happens every time the same subsystem is closed, submit an
CR against that subsystem, describing the problem; see Appendix A ,
“Submitting a CR.”
5130 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During a link close operation, the driver encountered an error
while sending an unconfigure reply message to an upper layer
subsystem (“Cause” = 32-bit status returned by the call to
pbt_dvr_send_reply).
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data and look up
that error also, for more actions to take. The subsystem’s access to the
link was closed, but the subsystem did not get the reply; reaction to this
situation is subsystem-dependent. The subsystem have already
terminated. If this problem happens every time the same subsystem is
closed, submit an CR against that subsystem, describing the problem;
see Appendix A , “Submitting a CR.”
The driver may now enter a broken state and not respond to further
requests, requiring a system reboot to completely shut the driver down.
If other subsystems still need to use the link, if you wish you may try
running the VGPBA diagnostic; execute the Reset function to see if that
restores access for the other subsystems, until a reboot can happen.
5160 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received an unconfigure request message before it
received its first configure request (“Cause” = 16-bit encoded value,
giving driver input event code and current state: Hewlett-Packard use
only).
ACTION: This error is informational only. The driver attempted to
return an error reply tothe sending subsystem. If this problem happens
frequently, try to determine what actions lead to the problem, then see
Appendix A , “Submitting a CR.”
5220 CLAS0001 MESSAGE: Unimplemented operation attempted.
CAUSE: The main driver DVR state machine was passed an input event
for which there is no processing implemented. Either there is a driver
bug or some data corruption has occurred (“Cause” = 32-bit ordinal
value of the input event code: Hewlett-Packard use only).
ACTION: Try to determine which operator or program actions led to this
error. Then see Appendix A , “Submitting a CR.”
After this problem occurs, the driver will enter a “broken” state where
is may not respond to further requests. If possible, run the VGPBA tool
program, and use it to force a driver dump, then forward the resulting
NETDMP##.pub.sys file to Hewlett-Packard for analysis. After a dump,
the driver will attempt to auto-reset itself and continue. You may also
use VGPBA to attempt a manual reset of the driver, after which it may