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

Chapter 18 431
PCI LAPBMUX Link Error Messages
SDI Driver Specific Status Values
(bring level-1 down) on the ports. By itself it is not descriptive of the
problem. This error is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see Appendix A , “Submitting a CR.”
5280 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: This is a generic hardware error, reported by firmware when
any of the driver’s hardware interface routines tries to bring down the
ports on the card. By itself it is not descriptive of the problem. This
error is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see Appendix A , “Submitting a CR.”
5320 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: This is a generic hardware error, reported by firmware when
any of the driver’s hardware interface routines tries to start the
protocol (level-2) on the ports. By itself it is not descriptive of the
problem. This error is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see Appendix A , “Submitting a CR.”
5360 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: This is a generic hardware error, reported by firmware when
any of the driver’s hardware interface routines tries to stop the protocol
(bring level-2 down) on the ports. By itself it is not descriptive of the
problem. This error is often seen as a result of firmware crash.
ACTION: If this problems happens repeatedly, then halt the system,
take a memory dump, and reboot, see Appendix A , “Submitting a CR.”
6000 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During final processing of a fatal driver error, the driver
attempted a standard auto-reset instead of dying. However, its attempt
to send a reset message to itself failed (“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: This error is likely an indication of a more serious system
software problem, and may be followed by a system abort. Probably all
message frames have been exhausted by some module running on the
system. Further recovery actions may not be possible; if the system
fails, take a memory dump and reboot.
Otherwise, since the auto-reset failed, the driver dies instead, notifying
upper layer software via an asynchronous event message if possible.
The network and/or link must now be stopped and restarted. Some
upper layers may stop the link on their own in response to an event
message. If not, manually stop the network and/or link via the