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

184 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
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.
119 ($77) MESSAGE: Driver dump was forced.
CAUSE: A user is forcing a driver dump to occur, typically via the
VGPBA diagnostic tool program.
ACTION: This error is informational only. The dump is probably being
forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see Appendix A , “Submitting a CR.”
121 ($79) MESSAGE: Driver is going down.
CAUSE: A request to the driver failed because the driver is in the
process of shutting down, or because it has encountered a fatal software
error and has not yet been shut down.
ACTION: If this status is reported during a shutdown operation, it may
be ignored. Otherwise this should be a signal to the operator that the
link driver has a problem and needs to be shut down, or dumped and/or
reset.