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

340 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: This informational error should be preceded by another error
giving a more specific reason for the failure; check log for that error and
look it up also, for more actions to take. The driver will attempt to send
an error reply for the startup request. It then enters a “broken” state
and awaits a shutdown, which the module configurator should attempt
automatically.
4620 CLAS0001 MESSAGE: Driver initialization failed.
CAUSE: The driver was unable to successfully bind to its lower
manager; the lower manager’s port number supplied by the I/O system
is nil.
ACTION: The link did not start, because erroneous information was
passed to the driver by the I/O system. This could indicate a serious
problem with the system software, or a problem with the I/O system. If
the problem persists, halt the system as soon as possible after the error
occurs and generate a dump; see Appendix A , “Submitting a CR.”
4650 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During initialization, the driver was unable to successfully bind
to its lower manager. Probably an underlying call to send_msg failed.
ACTION: The link did not start. This error may be preceded by other
errors in the log file giving a more specific reason for the failure. Check
the log data and look up additional errors for more possible actions. You
may retry the operation (try starting the link again), but the hardware
path may be unusable. If the problem persists, halt the system and
generate a dump; see Appendix A , “Submitting a CR.”
4680 CLAS0001 MESSAGE: Driver initialization failed.
CAUSE: The driver was unable to successfully bind to its lower
manager; an error occurred when attempting to send a bind request
message to the lower.
ACTION: The link did not start. This error may be preceded by other
errors in the log file giving a more specific reason for the failure. Check
the log data and look up additional errors for more possible actions. You
may retry the operation (try starting the link again), but the hardware
path may be unusable. If the problem persists, halt the system and
generate a dump; see Appendix A , “Submitting a CR.”
4710 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: The driver received a second copy of the first initialization
message it would ever get, indicating a second attempt to start the
driver.
ACTION: The driver sent an error reply in response to the message.
Further action may not be required. If the problem occurs frequently,
try to determine what operator commands or actions trigger the error,
then see Appendix A , “Submitting a CR.”