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

Chapter 16 183
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
90 ($5A) MESSAGE: Did not receive an expected port message.
CAUSE: This is a generic error that during a link-open or some other
operation by an upper level subsystem, link software sent a port
message to the driver, then encountered an error while awaiting the
correct reply message.
ACTION: Severity and side effects of this error are dependent upon the
purpose of the message that was not received. There may be a system
problem with message ports, or the link driver may have sent the wrong
reply message. If this happens every time, see Appendix A ,
“Submitting a CR.”
106 ($6A) MESSAGE: General error trying to get a buffer.
CAUSE: When attempting to directly obtain a new buffer manager
buffer from a read pool, to replenish the inbound buffer cache for one of
its bound protocols, the driver’s ISR encountered an error that was not
one of the few legal errors it expected, or was able to handle.
ACTION: The problem could indicate some serious internal problems
within the buffer manager or its data structures, or with the way the
system is configured. Note all log messages, especially the “Cause”
status for this error, and see Appendix A , “Submitting a CR.” If the
problem persists, take a system memory dump immediately after the
problem has occurred.
107 ($6B) MESSAGE: Cannot create a buffer pool.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator encountered an error while trying to create an
outbound buffer pool or control buffer pool.
ACTION: The system may be low on available memory. Try stopping
some applications or sessions and retry the operation. If the problem
persists, stop all networking and restart it, or restart the system. The
buffer size and pool size are not configurable. If the problem still occurs,
there could be a problem with the buffer manager. See Appendix A ,
“Submitting a CR.”
108 ($6C) MESSAGE: Cannot delete a buffer pool.
CAUSE: During a link-close operation by an upper level subsystem, the
link module deconfigurator encountered an error while trying to delete
an outbound buffer pool or control buffer pool.
ACTION: This is an informational warning that some system memory
resources may have been lost. Probably not all buffers were freed before
the pool was deleted. If this happens every time, see Appendix A ,
“Submitting a CR.”
115 ($73) MESSAGE: Driver encountered a software problem.
CAUSE: This is a generic software error, reported when any of the
driver’s non-hardware routines reports an error. By itself it is not