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

266 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
8690 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: After completing a trace enable 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.
8720 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: After completing a trace disable 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.
8780 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While initializing for 100VG-AnyLAN link training, the driver’s
ISR attempted to copy a training frame into adapter card memory, 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 is a fatal error. The link may require a manual shutdown
and restart to recover from this error. In later versions, the driver may
“die”, then will either attempt an auto-reset or else require a manual
shutdown and restart. DMA steps are a well-controlled driver resource,
and should not run out. If this problem happens repeatedly, see
Appendix A , “Submitting a CR.”
8810 CLAS0001 MESSAGE: Driver received an unknown port message.
CAUSE: The driver received a port message which it does not
implement, or containing a function code which it does not implement
(“Cause” = 32-bit ISR state machine input event tag value (HP use
only).
ACTION: This is an informational error only. If this error occurred as
part of a driver reset operation, it may be ignored.
The driver traced the unknown message then ignored it. The driver did
not attempt to return an error reply to the message sender. That sender
may now be hung, awaiting a reply. Attempt to determine what action