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

Chapter 17 303
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
150 ($96) MESSAGE: Pending message table full. Driver not finishing fast
enough.
CAUSE: While processing a new blocking request (requiring a driver exit
and later reply) and scanning a table in which to save the request, the
driver found an unused entry, but an entry counter indicated the table
was full.
ACTION: This fatal software error is only caused by a bug, because the
in use flags and counters should match. After reporting this error, the
driver will die, then will either attempt an auto-reset or else require a
manual shutdown and restart. If the problem persists, take a memory
dump and reboot. See Appendix A , “Submitting a CR.”
151 ($97) MESSAGE: Out of internal comm frame resources.
CAUSE: While attempting to request action from its ISR module, the
driver found that no available communication frames were available on
the referenced queue. The number of available comm frames is not
configurable, and the driver cannot operate if frames run out.
ACTION: This is a fatal software error. After reporting this error, the
driver will attempt a driver dump, then will auto-reset and attempt to
continue. Typically followed by another error giving more information
about what kind of comm the driver was trying to send; check log data
for that error and look it up also. Collect binary copies of all
NETDMP##.PUB.SYS dump files on tape for analysis by Hewlett-Packard
and see Appendix A , “Submitting a CR.”
152 ($98) MESSAGE: Driver initialization failed.
CAUSE: While processing its very first startup message, the driver
encountered a problem. Probably the configured hardware is not
present, is not the correct kind of adapter card, or there was a problem
configuring the ISR into the I/O system or binding to the lower bus
manager. The link is unusable.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data for that
error and look it up also, for more actions to take. The driver will
attempt to send an error reply for the startup request. It then enters a
“broken” state and awaits a shutdown, which the module configurator
should attempt automatically.
154 ($9A) MESSAGE: Configuration failed.
CAUSE: This is a generic error, reported after successful or unsuccessful
completion of initial hardware startup, if the driver encountered an
error bringing up the adapter card, or when opening the link, or while
attempting to send the reply to a pending configuration request from its
module configurator.