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

358 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
7230 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a 100Base-T connect sequence, the driver attempted to
check for presence of a link signal, but encountered an error trying to
read from the generic status register on the PHY chip (“Cause” = 32-bit
status from the call to pbt_mii_read16).
ACTION: If an interruption in power has 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.”
7260 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: During a 100Base-T connect sequence, the driver attempted to
check for presence of a link signal, but encountered an error trying to
read from the generic status register on the PHY chip (“Cause” = 32-bit
status from the call to pbt_mii_read16).
ACTION: If an interruption in power has 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.”
7290 CLAS0001 MESSAGE: Autonegotiation reports link settings are incompatible
with hub.
CAUSE: If this error occurs, it is probably because the link has reported
a remote fault. Usually this means the adapter card and the hub or
switch to which it is connected, have failed to agree on a link speed and
duplex setting acceptable to both.
ACTION: Verify that the cable is securely connected to the adapter card
at one end, and to a 100Base-TX or 10Base-T hub at the other.
Verify the cable is a correctly wired, Category-5 UTP cable. Category 3
or 4 cables are not acceptable.
If a crossover cable is being used, make sure it is correctly wired.
Check the configuration of the hub or switch port to which the adapter
card is connected. Adjust that configuration and, if necessary, use
NMMGR to adjust the configuration of the link, so that something will
match. If necessary, specify a forced speed and duplex setting, and
disable autonegotiation, at both ends.
7320 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: During a 100Base-T connect sequence, the driver found the link
was not connected yet, 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 link
connect 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