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

224 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
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.
3550 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While attempting to forward a disable-trace 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.
3580 CLAS0001 MESSAGE: Driver initialization failed.
CAUSE: While processing its very first startup message, the driver
encountered a problem (“Cause” = 32-bit status returned by the call to
vg_dvr_initialize). Probably the configured hardware is not present,
is not the correct kind of adapter card, or there was a problem
configuring the ISR into the I/O system.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log for that error and
look it up also, for more actions to take. The driver will attempt to send
an error reply for the startup request. It then enters a “broken” state
and awaits a shutdown, which the module configurator should attempt
automatically.
3610 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: While processing its very first startup message, the driver
encountered a problem trying to send a reply to that message
(“Cause” = 32-bit status returned by the call to vg_dvr_send_reply).
Probably an underlying call to send_msg has failed.
ACTION: The link did not start. This informational error should be
preceded by other errors giving a more specific reason for the failure;
check log data and look up that error also, for more actions to take.
Possibly the process which was to receive the reply no longer exists. The
error occurred on the reply, so if the caller — typically the I/O system —
does exist, it will not receive the reply, and may time out. The hardware
path may or may not be usable after this error, so a system reboot may
be needed before the next retry, however you may attempt a retry
anyway.
3640 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received a second copy of the first initialization
message it would ever get, indicating a second attempt to start the
driver (“Cause” = 16-bit encoded value, giving driver input event code