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

Chapter 17 367
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
8360 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: While processing a restart request, the ISR attempted to stop
the previously enabled heartbeat timer, but was returned an error
(“Cause” = 32-bit status from lnk_timer_stop).
ACTION: The restart can not be completed if the driver can not
successfully reinitialize the heartbeat timer. The driver may do an
MESSAGE: auto-reset. If the driver appears to hang, try a manual
shutdown and restart of the network link.
If the problem persists, it could indicate a system software error or
possible data corruption of system data structures. In that case, try to
halt the system and generate a dump as soon as possible after the
problem is detected; see Appendix A , “Submitting a CR.”
8540 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: After completing a start or restart operation, the driver’s ISR
then encountered an error trying to notify the DVR module of the
restart completion (“Cause” = 32-bit status from the call to
Pbt_isr_copy_send_to_dvr). Probably no comm frame was available.
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log data and look up
that error also, for more actions to take. Most likely the previous error
was fatal and the driver is about to “die”, then will either attempt an
auto-reset or else require a manual shutdown and restart.
8570 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received a new bind (rendezvous) from an upper
layer protocol, at a time when the driver was not able to process these
requests, such as before receiving its initial configuration data, 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: This problem most likely occurred while starting a new
network subsystem. Attempt to determine which subsystem was being
started when the error occurred and, if possible, which upper layer
protocol was binding. The bind failed. The driver logged the error, then
attempted to send an error reply message back to the protocol module
and continue.
Check the system console; if the driver is shutting down or doing a
dump, wait until that completes. In these cases, several protocols may
experience this same error. If the driver is not shutting down or dying,
the protocol may be sending binds to the driver at the wrong time. See
Chapter A , “Submitting a CR,” and file an CR against the network
subsystem being started.