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

304 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: This is a fatal software error. It might be caused by a bad
adapter card, by having too many driver users, by a heavy CPU load, or
by attempting to operate the network subsystem or tool which started
the link at too low of a CPU process priority, causing a timeout. Any
condition, such as a timeout or abort, which causes the driver’s module
configurator to cease awaiting the reply and dispose of its reply port,
might also cause this error. The driver now “dies” and awaits a
shutdown, which the module configurator should attempt
automatically.
160 ($A0) MESSAGE: Heartbeat timeout. Adapter card appears to be hung.
CAUSE: The LAN controller chip on the adapter card has failed to
produce any interrupt from normal activity for over 5 seconds. It has
also failed, for an additional 5 seconds, to respond to the driver’s
inquiry by producing a test interrupt. The driver has decided the card is
dead or hung.
ACTION: This is a fatal hardware error. Replace the adapter card. The
driver will enter a “broken” state and await a manual shutdown by the
operator. If you wish you may try running the VGPBA diagnostic and
attempt a reset. If the problem persists with a known good card, see
Appendix A , “Submitting a CR.”
161 ($A1) MESSAGE: Card did not go ready after hard reset.
CAUSE: After performing a hard reset of the adapter card during
startup, the HP-PB interface chip did not report “ready” status, or
reported an error.
ACTION: Replace the adapter card. If the same problem persists even
after replacement with a known good card, contact Hewlett-Packard:
your software could be out of date, but a patch may be available. It is
unlikely this would be caused by a system HP-PB bus hardware
problem.
170 ($AA) MESSAGE: Hub did not report link up within time allowed.
CAUSE: During a link connect attempt, the driver instructed the link
interface chip to connect, but afterward the LINK signal still did not
appear within the 3 second time allowed. The hub may not have liked
some or all of the frames, although it responded anyway. If this error is
logged, it is because the link did not connect within 25 to 30 seconds
after it was instructed to do so.
ACTION: This error is informational only. The driver will retry the
connect. If the problem happens every time, try checking the hub port
configuration, or replacing the cable and/or adapter card.
175 ($AF) MESSAGE: Timeout while awaiting link autonegotiation completion.
CAUSE: The link appears to be connected, but the driver thinks it is still
waiting for it to connect.