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

180 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
change NMCONFIG or contact your Hewlett-Packard Representative
for assistance in determining paths or correcting bus hardware
problems.
MESSAGE: Adapter card found does not match software
configuration.
63 ($3F) 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.
MESSAGE: Memory test failed: memory data miscompare.
64 ($40) CAUSE: Upon reaching the end of a diagnostic test of adapter card
memory or LAN controller chip memory, the driver had accumulated at
least one data pattern mismatch.
ACTION: One or more data patterns written by the driver did not
match the data read back from those same memory locations.
Depending on which test was being performed, either the adapter card
or LAN controller chip is faulty. Replace the adapter card.
MESSAGE: Cannot install interrupt handler.
75 ($4B) 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 the system is running an MPE release which supports
100-Mbit link drivers. The only other cause is a software bug; see
Appendix A, “Submitting an SR.”
MESSAGE: Cannot get ADA memory object.
76 ($4C) CAUSE: During initial startup, the driver attempted to obtain a
memory object via the I/O system, but received a bad status in the reply
for that request.
ACTION: Probably the amount of frozen memory on the system is very
high; if you have the GLANCE tool you can try to check memory usage.
Try retrying the operation again later, or first terminate some
applications and then retry.
MESSAGE: Cannot get a system timer.
77 ($4D) CAUSE: The driver attempted to get a system timer from I/O Services
but encountered an error. This is either caused by exhausting all timers
due to heavy system load, or by system software either failing to release
timers, or having some other bug.