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

268 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
8930 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: The driver received a utility I/O request from an upper level
tool program such as PVGUTIL, but encountered an error while trying
to construct the necessary data structure (“Cause” = 32-bit status from
the call to vg_isr_build_util_step). Probably no DMA step was
available.
ACTION: This problem most likely occurred while diagnosing some
previous problem. The driver logged the error, then attempted to send
an error reply message back to the sender and continue. DMA steps are
a well-controlled driver resource, and should not run out. If this
problem happens repeatedly, note whether you were trying to do a read
or a write, then see Appendix A , “Submitting a CR.”
8960 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: After completing a utility I/O request, the driver’s ISR then
encountered an error trying to notify the DVR module of the request
completion (“Cause” = 32-bit status from the call to
Vg_isr_copy_send_to_dvr). Probably no comm frame was available.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data and look up
that error also, for more actions to take. Most likely the previous error
was fatal and the driver is about to “die”, then will either attempt an
auto-reset or else require a manual shutdown and restart.
8990 CLAS0001 MESSAGE:
(Varies)
CAUSE: A general error occurred during processing of an input event by
the main driver ISR state machine, and the code where the error
occurred neglected to specify a sublocation code value, so the value 8990
was used.
ACTION: Note all logged error messages. The main problem is described
by whatever was logged. But the driver also needs to be fixed to specify
a unique sublocation for those errors. Please see Appendix A ,
“Submitting a CR.”
9020 CLAS0001 MESSAGE: Unimplemented operation attempted.
CAUSE: The main driver ISR state machine was passed an input event
for which there is no processing implemented. Either there is a driver
bug or some data corruption has occurred (“Cause” = 32-bit ordinal
value of the input event code: HP use only).
ACTION: Try to determine which operator or program actions led to this
error. Then see Appendix A , “Submitting a CR.”
After this problem occurs, the driver will enter a “broken” state where
is may not respond to further requests. If possible, run the VGPBA tool
program, and use it to force a driver dump, then forward the resulting
NETDMP##.PUB.SYS file to Hewlett-Packard for analysis. After a dump,