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

Chapter 16 245
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: Replace the adapter card. The link did not connect. If the
problem persists with a known good card, see Appendix A, “Submitting
an SR.”
MESSAGE: Driver encountered a hardware problem.
5690 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver
attempted to enable broadcast packets, but encountered an error trying
to read from the network command register on the LAN Controller chip
(“Cause”= 32-bit status from the call to vg_dio_read8). Most likely a
powerfail has occurred.
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. But if the same
problem happens every time, see Appendix A, “Submitting an SR.”
MESSAGE: Driver encountered a hardware problem.
5720 CLAS0001 CAUSE: During a 100VG-AnyLAN link training sequence, the driver
attempted to signal a training failure, but encountered an error trying
to read from the PHY control register on the PHY chip (“Cause”= 32-bit
status from the call to vg_mii_read16). Most likely a powerfail has
occurred.
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. Otherwise, the MII
bus may have failed; replace the adapter card. If the same problem
persists, see Appendix A, “Submitting an SR.”
MESSAGE: Driver encountered a software problem.
5750 CLAS0001 CAUSE: While beginning a 100Base-T connect sequence, the driver
started to reset the PHY chip, but 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 wait for the PHY reset
to finish; 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.
5780 CLAS0001 CAUSE: During a 100Base-T connect sequence, the driver found the
PHY chip was not reset yet, and started to reset it again, but
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