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

Chapter 17 333
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
request this time, but it remains off.
3870 CLAS0001 MESSAGE: A driver request failed.
CAUSE: While processing a request to turn link trace on, the driver was
unable to locate a free storage element in which to save reply
information (“Cause” = 32-bit status returned by the call to
pbt_dvr_save_msg).
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.
3900 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: Before attempting to forward a protocol rendezvous (bind)
request to its ISR, the driver discovered the ISR was already in a “dead”
state and unable to process requests (“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. The driver attempted to send an
error reply for the rendezvous request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
3910 CLAS0001 MESSAGE: Cannot get ADA memory object.
CAUSE: During initial startup, the driver attempted to obtain a memory
object via the I/O system, but received a bad status in the reply for that
request (“Cause” = 32-bit status from the reply message).
ACTION: The link did not start, and the driver attempted to send back
an error reply in response the configuration request from the module
configurator. Probably the amount of frozen memory on the system is
very high; if you have the GLANCE tool you can try to check memory
usage. Try retrying the operation again later, or first terminate some
applications and then retry.
3930 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: Before attempting to forward a protocol separate (unbind)
request to its ISR, the driver discovered the ISR was already in a “dead”
state and unable to process requests (“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. The driver attempted to send an
error reply for the separate request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.