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

386 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
before.
25 ($19) MESSAGE: Cannot release a system plabel.
CAUSE: During the final link-close operation by an upper level
subsystem, the link module deconfigurator encountered an error while
trying to release the link's write initiator procedure.
ACTION: This is an informational warning that some system memory
resources may have been lost. The module deconfigurator reported an
error, but attempted to continue with the close. If this happens every
time, see Appendix A , “Submitting a CR.”
27 ($1B) MESSAGE: Late dump-done message received. Dump took too long.
CAUSE: The driver received a driver-dump completion message when it
was not working on a dump.
ACTION: This error is informational only. Probably the Network Dump
Process was delayed by other system processing, such that it exceeded
the time limit set by the driver. The resulting dump file may or may not
be incomplete. A more serious driver problem has already occurred,
after which the driver will now attempt to auto-reset and continue. If
you are trying to reproduce a specific problem but this error occurs
every time, reduce the CPU or disc activity load before the next
attempt. If load is not the problem, see Appendix A , “Submitting a CR.”
28 ($1C) MESSAGE: A driver dump is starting.
CAUSE: During driver dumping, Dump Surrogate tried to open the
dump file.
ACTION: This error is informational only. The dump is probably being
forced because the system operator suspects a link driver problem.
Forward the resulting NETDMP##.PUB.SYS file to Hewlett-Packard for
analysis if necessary, and see Appendix A , “Submitting a CR.”
32 ($20) MESSAGE: A driver dump was suppressed. Too many dumps already.
CAUSE: During processing of some other fatal driver error, the driver
attempted a driver dump, but encountered an error.
ACTION: This error is mainly informational, since the driver did not
dump, but may be indicative of other, possibly-related problems. The
driver will still attempt to auto-reset itself, up to a total of 12 times or
more.
33 ($21) MESSAGE: Driver is out of DMA resources.
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.
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