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

300 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
“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
descriptive of the problem. This error is often seen as a result of
previous errors from intrinsics, reply messages, or validity checks.
ACTION: When this error occurs as a result of previous errors, it mainly
serves as a way to track the sequence of the failure back to what was
happening at the time. Check for those errors and look them up for an
additional explanation of the problem.
116 ($74) MESSAGE: Internal driver error.
CAUSE: While processing a request, the link driver encountered a
problem indicating there is something internally wrong with some
other module of system software. Specific instances include: range or
bounds violation errors while storing or clearing a statistics buffer.
ACTION: This is an indication of a bug in the link software. If possible,
note exactly what actions caused the error to occur, then see Appendix
A , “Submitting a CR.”
117 ($75) MESSAGE: A driver request failed.
CAUSE: This is a generic software error, used when the driver receives a
new request but cannot process it because of an earlier failure. It is
used in the reply to the outside module which requested the operation,
to indicate it could not be processed.
ACTION: If this status is reported, it is because of some earlier failure.
Check log files and locate any previous errors for this link, to try to find
the reason this error is now occurring. By running the VGPBA
diagnostic and trying the Reset function, you may be able to clear the
error.
118 ($76) MESSAGE: Serious error encountered while trying to start
heartbeats.
CAUSE: During startup, the link driver was unable to obtain a system
timer resource for use in periodic monitoring of the health of the
adapter card and link connection. This is either caused by exhausting