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

Chapter 17 339
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
4470 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_send_reply). Probably a port message could not be
sent.
ACTION: The driver allows 11 simultaneous opens. The open attempt by
the additional subsystem failed. Shut down any subsystems that are
not currently needed and try again.
A side-effect of this error may be that the driver becomes unusable; if
so, run VGPBA and execute the Reset function to see if that restores
normal operation.
4500 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: The driver received a new open from an upper layer subsystem,
at a time the driver was not able to process these requests, such as
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: The open failed. Check the system console; if the driver is
shutting down or doing a dump, wait until that completes. Retry the
operation. If the problem persists, the driver may be broken; run the
VGPBA diagnostic and attempt a Reset function. If the problem still
persists, run VGPBA, attempt a Dump function, and save the resulting
file (NETDMP##.PUB.SYS) for analysis by Hewlett-Packard. If the driver
still does not become usable after this, use Control-B at the console to
halt the system, take a memory dump, and reboot, see Appendix A ,
“Submitting a CR.”
4560 CLAS0001 MESSAGE: Bad message for current state.
CAUSE: Before attempting to forward a diagnostic 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 diagnostic request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
4590 CLAS0001 MESSAGE: Driver initialization failed.
CAUSE: While processing its very first startup message, the driver
encountered a problem (“Cause” = 32-bit status returned by the call to
pbt_dvr_chk_chard_type). Probably the configured hardware is not
present, is not the correct kind of adapter card, or there was a problem
configuring the ISR into the I/O system.