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

294 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
adapter card, but the read failed to return one of the necessary
acknowledgment bits. This indicates good data was not returned.
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.
60 ($3C) MESSAGE: Adapter card PHY did not finish reset in the time allowed.
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 a CR.”
62 ($3E) MESSAGE: No adapter card found on specified PCI bus.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator did not find an PCI 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 PCI 100Base-T adapter card is
installed in your computer backplane.If necessary, change NMCONFIG
or specify the correct path. The driver automatically configures
software to drive any high-level bus converters leading to that path, so
there should be no need to install them in SYSGEN, but check SYSGEN
for possible path conflicts. If necessary, contact your Hewlett-Packard
Representative for assistance in determining paths or correcting bus
hardware problems.
63 ($3F) MESSAGE: Adapter card found does not match software
configuration.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator found a supported adapter card at the path
specified in NMCONFIG, but it was not the right type of card for the
link being started.
ACTION: Correct the network configuration or plug in the correct type of
adapter card, and retry the operation.
75 ($4B) MESSAGE: Cannot install interrupt handler.
CAUSE: During initial driver startup, the driver was unable to add its
ISR into the MPE I/O system, as an interrupt handler routine for any
adapter card interrupts on that EIR bit.
ACTION: The driver did not start up. There is probably an MPE
software installation problem, with incomplete or incompatible O/S
software. Verify that the I/O path specified for the adapter card for a
supported adapter. The only other cause is a software bug; see