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

Chapter 16 261
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
auto-reset itself, up to a total of 12 times or more, even though this
happened during diagnostic testing. If the problem persists, the system
may be low on timers; try stopping some applications before retrying
again.
MESSAGE: Driver encountered a software problem.
8030 CLAS0001 CAUSE: While the link was disconnected, the driver received an
interrupt from the PHY chip on the adapter card, and began to initiate
a link reconnect, 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 reawaken the driver for a
reconnect attempt if no interrupt arrived. 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.
8060 CLAS0001 CAUSE: During a link connect attempt, the driver received an interrupt
from the PHY chip on the adapter card and passed that to a lower level,
but the lower level returned an error (“Cause”= 32-bit status from the
call to vg_isr_call_phy_state_machine).
ACTION: This informational error is typically preceded by another
error message giving better information about the original cause; check
log data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.
MESSAGE: Driver encountered a software problem.
8090 CLAS0001 CAUSE: While the link was connected and working, the driver received
an interrupt from the PHY chip on the adapter card and passed that to
a lower level, but the lower level returned an error (“Cause”= 32-bit
status from the call to vg_isr_call_phy_state_machine). Probably
the link has unexpectedly disconnected.
ACTION: This informational error is typically preceded by another
error message giving better information about the original cause; check
log data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.