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

Chapter 18 423
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
If any errors occur as a result of the unbind, they will appear after, not
before, this log event; the unbind will still complete, and the protocol
will be successfully unbound.
2840 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: When attempting to separate during a protocol separate
(unbind), the driver gets an error from its state machine
(“Cause” = 32-bit status stating the driver is “dying”).
ACTION: If the operator already knows the driver is in the process of
being closed, this error can be ignored.
2860 CLAS0001 MESSAGE: Bad hardware ID or path.
CAUSE: During initial driver startup, a supported Sync MUX adapter
card was not found at the hardware path specified in NMCONFIG.
ACTION: The driver did not start up. Verify the path in NMCONFIG is
correct and complete, and matches the path where a Sync MUX adapter
card is installed in the computer backplane. Verify the Power LED is lit
on that adapter. If necessary, contact your Hewlett-Packard
Representative for hardware assistance.
2880 CLAS0001 MESSAGE: Driver is starting adapter card.
CAUSE: The driver has completed initial startup of the adapter card, or
a restart following a reset, powerfail, dump, or other recoverable
condition (“Status” = 32-bit status giving the result of the startup
attempt, 0 = successful).
ACTION: This event is informational. No action is required unless the
status is nonzero. Nonzero status indicates the startup failed; this may
be preceded by other specific errors.
2890 CLAS0001 MESSAGE: Cannot install interrupt handler.
CAUSE: During initial driver startup, the driver was unable to add its
ISR into the MPE I/O system, as an interrupt handler routine for any
adapter card interrupts on that EIR bit (“Cause” = 32-bit status
returned by the call to io_config_pci_int).
ACTION: The driver did not start up. There is probably an MPE
software installation problem, with incomplete or incompatible O/S
software. Verify the system is running an MPE release which supports
WAN Sync MUX link drivers. The only other cause is a software bug;
see Appendix A , “Submitting a CR.”
2920 CLAS0001 MESSAGE: Powerfail detected.
CAUSE: During a LAPBMUX link connect attempt, the driver detected
all 1's on a hardware register read, and, upon checking further, saw
that its hardware I/O address space was disabled, indicating a
powerfail had already occurred.