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

250 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
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 hardware problem.
6180 CLAS0001 CAUSE: During a 100Base-T connect sequence after the link came up,
the driver attempted to check the final speed and duplex settings, but
encountered an error trying to read from the PHY address register on
the PHY chip (“Cause”= 32-bit status from the call to vg_mii_read16).
Most likely a powerfail has occurred. This error cannot occur on older
PHY chips.
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 hardware problem.
6200 CLAS0001 CAUSE: During a 100Base-T connect sequence, the driver attempted to
adjust the duplex setting of the LAN controller chip, but encountered
an error trying to read from the network command register on that 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 software problem.
6230 CLAS0001 CAUSE: During a 100Base-T connect sequence, after the link failed to
connect, the driver started a retry, 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 link to
connect. 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.”