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

Chapter 16 231
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
subsystem (“Cause” = 32-bit status returned by the call to
vg_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.
4270 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: HP 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.”
4300 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While processing a diagnostic input-output request message,
the driver was unable to locate a free storage element in which to save
reply information (“Cause” = 32-bit status returned by the call to
vg_dvr_save_msg).
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 driver may not attempt to
reply to this request; if not, the session which sent it may hang. Most
likely the previous error was fatal and the driver is about to “die”, then
will either attempt an auto-reset or else require a manual shutdown
and restart.
4330 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While processing a diagnostic input-output request message,
the driver encountered an error (“Cause” = 32-bit status returned by
the call to vg_dvr_copy_send_to_isr). Probably no comm frame was
available.
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 driver may not attempt to