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

Chapter 17 357
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
attempt a reset, however it is unlikely this will fix the problem. If the
problem persists with a known-good card, see Appendix A , “Submitting
a CR.”
7140 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: During a 100Base-T connect sequence, the driver attempted to
power up the PHY, but encountered an error while trying to get or reset
a timer (“Cause” = 32-bit status from the call to lnk_timer_start).
This timer was to be used to wait again for the PHY power up 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.
7170 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a 100Base-T connect sequence, after resetting the PHY
chip, the driver encountered an error while trying to read the PHY ID
(“Cause” = 32-bit status from the call to pbt_isr_init_phy_id). 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. Most likely there is
an adapter card hardware problem; the card may need to be replaced.
7200 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: During a 100Base-T connect sequence, the driver attempted to
set a “watchdog” timer to wait for the PHY to complete bringing the link
up, but encountered an error while trying to get or reset a timer
(“Cause”= 32-bit status from the call to lnk_timer_start). 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.