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

Chapter 16 211
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
2030 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During final processing of a fatal driver error, the driver
attempted a standard auto-reset instead of dying. However, its attempt
to send a reset message to itself failed (“Cause” = 32-bit status returned
by the call to send_msg). If this error is reported, it is because the driver
has already encountered some other error.
ACTION: This error is likely an indication of a more serious system software
problem, andmay befollowed by asystem abort. Probablyall message frames
have been exhausted by some module running on the system. Further
recovery actions may not be possible; if the system fails, take a memory dump
and reboot.
Otherwise, since the auto-reset failed, the driver dies instead, notifying
upper layer software via an asynchronous event message if possible.
The network and/or link must now be stopped and restarted. Some
upper layers may stop the link on their own in response to an event
message. If not, manually stop the network and/or link via the
appropriate operator command (for example, :NETCONTROL STOP) and
then restart it.
2060 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: While notifying upper level subsystems that the driver detected
a serious error, powerfail, or reset, an attempt to send an asynchronous
event message to one of those subsystems failed (“Cause” = 32-bit
status returned by the call to send_msg).
ACTION: This is a warning that one or more subsystems may not be aware
the link has had a problem. The subsystem(s) may have failed to close the
driver as part of their shutdown. The driver will continue with its error
recoveryactions,andnouseractionisrequired.Ifthishappenseverytime,see
Appendix A , “Submitting a CR.”
2090 CLAS0001 MESSAGE: A driver dump was suppressed. Too many dumps already.
CAUSE: During processing of a fatal driver error, the driver attempted a
driver dump, but determined it had already dumped too many times
since it was initially started (“Cause” is not used here). If this error is
reported, it is because the driver has already encountered some other
error.
ACTION: By design, the driver attempts to auto-reset itself after any driver
dump.But after3 dumps, toavoid uncontrollablyfilling diskspace withdriver
dumps, additional dumps are automatically suppressed. No attempt is made
to determine whether the dumps are duplicates of the same problem. The
driverdid notdump,butwillstillattemptto auto-resetitself, uptoa totalof12
times or more.
There is apparently something wrong, since many driver dumps are
occurring. Collect binary copies of all dump files (NETDMP##.PUB.SYS)
on tape for analysis by Hewlett-Packard and see Appendix A ,
“Submitting a CR.”