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

Chapter 16 241
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
read from the PHY status 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 a CR.”
5510 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a 100VG-AnyLAN link training sequence, the driver
attempted to clear PHY statistics, but encountered an error trying to
read all statistics from the LAN controller chip (“Cause” = 32-bit status
from the call to vg_isr_read_clr_tlan_stats). Most likely a
powerfail has occurred.
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. If the same problem
persists, see Appendix A , “Submitting a CR.”
5540 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a 100VG-AnyLAN link training sequence, the driver
attempted to request a test interrupt, 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 a CR.”
5570 CLAS0001 MESSAGE: Driver encountered a software problem.
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.