NS3000/iX Error Messages Reference Manual (36923-90041)
244 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: Driver encountered a software problem.
5570 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver
requested a test interrupt, then encountered an error while trying to
get or reset a timer (“Cause”= 32-bit status from the call to
vg_start_timer). This timer was to be used to verify the test
interrupt arrives; the driver cannot connect the link if a PHY timer
cannot be started. If this error is reported, it is because the driver has
already encountered some other error.
ACTION: Typically preceded by another error message giving better
information about the original cause; check log data for that error and
look it up also. The driver did not dump, but will still attempt to
auto-reset itself, up to a total of 12 times or more. If the problem
persists, the system may be low on timers; try stopping some
applications before retrying again.
MESSAGE: Driver encountered a software problem.
5600 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver
received the expected test interrupt, but encountered an error while
trying to stop and release a timer (“Cause”= 32-bit status from the call
to vg_stop_timer). This timer was used to wait for the test interrupt
to arrive. If this error is reported, it is because the driver has already
encountered some other error.
ACTION: This is a warning that some timer resources may have been
lost. The link did not connect. Typically preceded by another error
message giving better information about the original cause; check log
data for that error and look it up also. Unless this happens constantly,
the system should continue to run, and the driver will probably retry
the connect. If the problem happens every time, see Appendix A,
“Submitting an SR.”
MESSAGE: Driver encountered a software problem.
5630 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver’s
ISR module attempted to send a training request to its DVR module,
but encountered an error (“Cause”= 32-bit status returned by the call to
vg_isr_copy_send_to_dvr). 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
stopped trying to connect the link.
MESSAGE: An expected PHY interrupt did not arrive.
5660 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver
requested a test interrupt from the PHY chip on the adapter card, but
received a timeout instead (“Cause” is not used here). The driver cannot
connect the link if PHY interrupts do not work.