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

426 Chapter18
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
If upper level network subsystems appear hung, try shutting them
down manually, or shutting down and restarting the network link; if
the problem persists, see Appendix A , “Submitting a CR.”
3240 CLAS0001 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.”
3280 CLAS0001 MESSAGE: Driver received an unknown port message.
CAUSE: Some module on the system has sent the driver a message
having an unknown message descriptor. The driver does not implement
any messages having that descriptor (“Cause” = 32-bit value of the
message descriptor field).
ACTION: The driver took no action on the message, and dropped it.
However, if the problem occurs frequently, your system may not be set
up properly. The driver traces the message which it received. If you can
repeat the problem, first enable link tracing. Then reproduce the
problem, stop tracing, and save the resulting trace data file for analysis
by Hewlett-Packard, see Appendix A , “Submitting a CR.”
3400 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received a new open from an upper layer subsystem,
at a time the driver was not able to process these requests, such as
during shutdown or after a fatal software error (“Cause” = 16-bit
encoded value, giving driver input event code and current state;
Hewlett-Packard use only).
ACTION: The open failed. Check the system console; if the driver is
shutting down or doing a dump, wait until that completes. Retry the
operation. If the problem persists, the driver may be broken. If the
driver still does not become usable after this, use Control-B at the
console to halt the system, take a memory dump, and reboot, see
Appendix A , “Submitting a CR.”
3580 CLAS0001 MESSAGE: Driver initialization failed.
CAUSE: While processing its very first startup message, the driver
encountered a problem (“Cause” = 32-bit status returned by the call to
acc_initialize). Probably the configured hardware is not present, is
not the correct kind of adapter card, or there was a problem configuring
the ISR into the I/O system.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log for that error and