NS3000/iX Error Messages Reference Manual (36923-90041)
Chapter 16 179
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: EEPROM reads can be sensitive to software timing. If you
have GLANCE or a similar tool, run it and check the CPU load on the
system. If the load is high, try reducing the CPU load, then retry the
operation. If the problem persists, the adapter card has probably failed;
replace the adapter card.
MESSAGE: EEPROM write error on adapter card.
59 ($3B) CAUSE: During a diagnostic operation, the driver attempted to write to
an EEPROM chip on the adapter card, but the write failed to return one
of the necessary acknowledgment bits. This indicates the data was not
written properly.
ACTION: EEPROM writes can be sensitive to software timing. If you
have GLANCE or a similar tool, run it and check the CPU load on the
system. If the load is high, try reducing the CPU load, then retry the
operation. If the problem persists, the adapter card has probably failed;
replace the adapter card.
MESSAGE: Adapter card PHY did not finish reset in the time allowed.
60 ($3C) CAUSE: During a link connect sequence, the driver tried 3 times to
reset the PHY chip, but it still did not go “ready” after the reset.
ACTION: This is a fatal hardware error. Replace the adapter card. The
driver cannot connect the link if the PHY will not reset. If the problem
persists with a known good card, see Appendix A, “Submitting an SR.”
MESSAGE: Adapter card produced an illegal interrupt.
61 ($3D) CAUSE: The link driver has received an interrupt from the card during
normal operation, but the driver should have specifically disabled that
interrupt at startup.
ACTION: The driver will attempt to perform a dump of all host context
data structures and adapter card memory, then reset itself and
continue. Save the resulting NETDMP##.PUB.SYS file for possible
analysis by Hewlett-Packard. But first, replace the adapter card and
see if this corrects the problem. If not, see Appendix A, “Submitting an
SR.”
MESSAGE: No adapter card found on specified HP-PB bus.
62 ($3E) CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator did not find an HP-PB bus at the hardware
path specified in NMCONFIG.
ACTION: Verify the path in NMCONFIG is correct and complete, and
matches the path where a supported 100VG-AnyLAN or 100Base-T
adapter card is installed in your computer backplane. If the path passes
through bus converters, verify the SYSGEN configuration has entries
for the higher-level bus converters leading to that path. If necessary,