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

334 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
3960 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: Before attempting to forward a diagnostic or LINKCONTROL
statistics request to its ISR, the driver discovered the ISR was already
in a “dead” state and unable to process requests (“Cause” = 32-bit
status stating the driver is “dying”).
ACTION: If the operator already knows the driver is in the process of
being closed, this error can be ignored. The driver attempted to send an
error reply for the statistics request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
3990 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: Before attempting to forward a diagnostic or LINKCONTROL
statistics request to its ISR, the driver discovered the ISR was already
in a “dead” state and unable to process requests (“Cause” = 32-bit
status stating the driver is “dying”).
ACTION: If the operator already knows the driver is in the process of
being closed, this error can be ignored. The driver attempted to send an
error reply for the statistics request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
4020 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: Before attempting to forward a diagnostic hardware-control
request to its ISR, the driver discovered the ISR was already in a “dead”
state and unable to process requests (“Cause” = 16-bit encoded value,
giving driver input event code and current state: Hewlett-Packard use
only).
ACTION: If the operator already knows the driver is in the process of
being closed, this error can be ignored. The driver attempted to send an
error reply for the statistics request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
4030 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received a release-memory reply message it was not
expecting (“Cause” = 16-bit encoded value, giving driver input event
code and current state: HP use only).
ACTION: The driver may already have changed state because of a
shutdown or another problem, in which case this message can be
ignored. Otherwise, the I/O system may be confused. The driver will
drop this message without further action. If the problem occurs
repeatedly, see Appendix A , “Submitting a CR.