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

232 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
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.
4360 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: Before attempting to forward a diagnostic input-output request
message to its ISR, the driver discovered the ISR was already in a
“dead” state and unable to process requests request (“Cause” = 16-bit
encoded value, giving driver input event code and current state: HP use
only).
ACTION: If the operator already knows the driver is in the process of
being closed, this error can be ignored. The driver attempted to send an
error reply for the diagnostic request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
4390 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While processing a diagnostic register read-write 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
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.
4400 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While attempting to forward a diagnostic hardware-control
request to its ISR, 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. 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.
4410 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: Before attempting to forward a diagnostic hardware-control
request to its ISR, the driver discovered the ISR was already in a “dead”
state and unable to process requests (“Cause” = 16-bit encoded value,
giving driver input event code and current state: HP use only).