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

432 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
appropriate operator command (for example, :NETCONTROL STOP) and
then restart it.
6040 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 after 3 dumps, to avoid uncontrollably filling disk
space with driver dumps, additional dumps are automatically
suppressed. No attempt is made to determine whether the dumps are
duplicates of the same problem. The driver did not dump, but will still
attempt to auto-reset itself, up to a total of 12 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.”
6080 CLAS0001 MESSAGE: Internal error while initiating a dump. Dump failed.
CAUSE: During processing of a fatal driver error, the driver attempted a
driver dump, but encountered an error while trying to get or reset a
timer (“Cause” = 32-bit status returned by the call to
lnk_timer_start). This timer was to be used to avoid deadlock in case
the dump process did not respond; the driver cannot attempt a dump if
a dump timer cannot be started. If this error is reported, it is because
the driver has already encountered some other error.
ACTION: Typically preceded by another error message giving better
information about the original cause; check log data for that error and
look it up also. The driver did not dump, but will still attempt to
auto-reset itself, up to a total of 12 times or more.
6120 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During final processing of a fatal driver error, the driver
attempted a driver dump, but was unable to send a dump event to the
dump process (“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: The driver did not dump, but will still attempt to auto-reset
itself, up to a total of 12 times or more.