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

298 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: The driver will attempt to continue, and it will attempt to log
the error unless a system abort occurs first. If the problem occurs
repeatedly, too many system I/O resources may become lost; take a
memory dump and see Appendix A , “Submitting a CR.”
95 ($5F) MESSAGE: Could not allocate or reassign an I/O virtual address.
CAUSE: The driver attempted to allocate a new I/O virtual address (to
describe a temporary data buffer in memory which would be referenced
by the adapter card), or reassign an I/O virtual address previously
allocated to a different block of memory, but the I/O system reported an
error.
ACTION: If this error was logged, it means that I/O virtual address was
required for normal operation so acquisition cannot be delayed. The
driver cannot continue, but will attempt to log the error unless a system
abort occurs first. Probably the system is out of I/O virtual addresses.
You may need to start fewer links and/or mass storage devices, move
some adapter cards onto different I/O buses, or add more I/O buses to
the system.
96 ($60) MESSAGE: Unable to autoconfigure underlying I/O paths.
CAUSE: During startup, the driver asked the I/O system to start I/O
drivers for each higher-level bus component leading to the configured
path of the 100Base-T adapter card, but encountered an error.
ACTION: Check the cardcage and/or run an I/O map utility to verify the
correct 100Base-T I/O path was specified in the NMCONFIG file.
Ensure the 100Base-T path ends in “/0/0”. Run SYSGEN and check
entry I/O context. Verify the I/O path is not already configured for a
different kind of device; if so, modify and save the configuration, and
reboot the system. If none of this helps, contact your Hewlett-Packard
Representative for assistance.
98 ($62) MESSAGE: Link common reported an inbound buffering problem.
CAUSE: Varies. Usually related to an underlying error condition or
resource contention problem in the buffer manager.
ACTION: See Appendix A , “Submitting a CR.”
99 ($63) MESSAGE: Link common reported a receive processing problem.
CAUSE: Varies. The driver encountered an error condition when
attempting to bind with an upper layer protocol.
ACTION: Check the log file for additional errors related to a specified
sublocation in the code, and look up those sublocation errors for more
specific information, see Appendix A , “Submitting a CR.”
100 ($64) MESSAGE: Link common reported a protocol bind problem.
CAUSE: Varies. The driver encountered an error condition when
attempting to bind with an upper layer protocol.