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

338 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
clears the problem.
4350 CLAS0001 MESSAGE: Configuration failed.
CAUSE: During initial driver startup, the driver encountered an error
during configuration (“Cause” = 32-bit status returned by the call to
pbt_dvr_port_msg_exec). Probably there are already too many opens
against the driver.
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. This error can only be caused
by a bug, a mismatch between driver’s state and open table.
4380 CLAS0003 MESSAGE: Driver is starting up.
CAUSE: The driver has just completed initial configuration and is now
starting up (“Vers” = driver version number, “Pda” = 64-bit pointer to
driver context area: HP use only). This event only occurs on initial
startup, not on restarts after resets, etc.
ACTION: This event is informational. No action is required.
4410 CLAS0001 MESSAGE: Configuration failed.
CAUSE: During initial driver startup, the driver encountered an error
during configuration, while attempting to request ADA memory from
the MPE I/O system (“Cause” = 32-bit status returned by the call to
pbt_dvr_port_msg_exec). Probably a port message could not be sent.
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.
The open request failed. The driver will now “die” and must be shut
down; the module configurator should do this automatically.
4440 CLAS0001 MESSAGE: Configuration failed.
CAUSE: While processing a driver open from an upper layer subsystem,
which was not the first open against the driver, the driver encountered
an error during configuration (“Cause” = 32-bit status returned by the
call to pbt_dvr_port_msg_exec). Probably there are already too many
opens against the driver.
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.
The driver returned a bad result to the subsystem, and the open
request failed. The driver will continue to operate all other subsystems
as before.