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

Chapter 18 387
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
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.”
34 ($22) MESSAGE: Driver dump was forced.
CAUSE: A user is forcing a driver dump to occur, typically via the CI
prompt.
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.”
43 ($2B) MESSAGE: A received frame could not be delivered.
CAUSE: Just before delivering a received data frame to an upper layer
protocol, the driver found that the rendezvous table entry specified in
the buffer was not in the proper state.
ACTION: This is an internal error which detects a normal race
condition. Probably the protocol separated from the driver while a
frame destined for it was in motion. The frame was not delivered, and
the buffer was silently released. No action is required.
46 ($2E) MESSAGE: Link tracing is already enabled.
CAUSE: The driver received a request to turn link tracing on when it
was already on.
ACTION: This event is informational. No action is required. An error
reply was sent in response to the request. Trace was not started by this
request this time, but it remains on.
47 ($2F) MESSAGE: Link tracing is already disabled.
CAUSE: The driver received a request to turn link tracing off when it
was already off.
ACTION: This event is informational. No action is required. An error
reply was sent in response to the request. Trace was not stopped by this
request this time, but it remains off.
60 ($3C) MESSAGE: Driver encountered a hardware problem.
CAUSE: This is a generic hardware error, reported when any of the
driver's hardware access routines reports an error. By itself it is not
descriptive of the problem. This error is often seen as a result of
firmware crash.
ACTION: When this problem happens, driver will dump the card and
itself. If this problems happens repeatedly, then halt the system, take a
memory dump, and reboot. see Appendix A , “Submitting a CR.”