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

Chapter 17 335
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
4050 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: Before attempting to forward a diagnostic or LINKCONTROL
statistics 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 fro the statistics request. The ISR may also be “dead” as a
result of a serious previous error. A diagnostic reset action may clear
this condition.
4080 CLAS0001 MESSAGE: Unimplemented operation attempted.
CAUSE: The main driver DVR state machine was passed an input event
for which there is no processing implemented. Either there is a driver
bug or some data corruption has occurred (“Cause” = 32-bit ordinal
value of the input event code: Hewlett-Packard use only).
ACTION: Try to determine which operator or program actions led to
this error. Then see Appendix A , “Submitting a CR.”
After this problem occurs, the driver will enter a “broken” state where
is may not respond to further requests. If possible, run the VGPBA tool
program, and use it to force a driver dump, then forward the resulting
NETDMP##.PUB.SYS file to HP for analysis. After a dump, the driver will
attempt to auto-reset itself and continue. You may also use VGPBA to
attempt a manual reset of the driver, after which it may be possible to
continue.
4110 CLAS0001 MESSAGE: Cannot install interrupt handler.
CAUSE: During initial driver startup, the driver was unable to add its
ISR into the MPE I/O system, as an interrupt handler routine for any
adapter card interrupts on that EIR bit (“Cause” = 32-bit status
returned by the call to io_config_int).
ACTION: The driver did not start up. There is probably an MPE
software installation problem, with incomplete or incompatible O/S
software. Verify the system is running an MPE release which supports
PCI 100Base-T link drivers. The only other cause is a software bug; see
Appendix A , “Submitting a CR.”
4140 CLAS0001 MESSAGE: Internal driver error.
CAUSE: During initialization, the driver attempted to obtain
information about the PCI device (BAR information) from the I/O
system but encountered an error (“Cause” = 32-bit status returned from
io_get_pci_dev_info).
ACTION: The driver did not start up. Check that the 100Base-T adapter
card is properly seated in its PCI slot and that the I/O path has been
properly configured. If the problem persists, it may indicate a problem