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

Chapter 16 229
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
this log event means it is being ignored.
4130 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While attempting to forward a protocol separate (unbind)
message 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. The driver
dropped this request message without further action, likely resulting in
timeouts and failure of the network and/or protocol to cleanly shut
down.
4134 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: Before attempting to forward a protocol separate (unbind)
request to its ISR, the driver discovered the ISR was already in a “dead”
state and unable to process requests (“Cause” = 32-bit status stating
the driver is “dying”).
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 separate request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
4140 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While attempting to forward a diagnostic or LINKCONTROL
statistics 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. The driver
dropped this request message without further action, likely resulting in
timeouts and possibly a hung C.I. or program session. A system reboot
may be required to recover from that session hang.
4144 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: Before attempting to forward a diagnostic or LINKCONTROL
statistics request to its ISR, the driver discovered the ISR was already
in a “dead” state and unable to process requests (“Cause” = 32-bit
status stating the driver is “dying”).