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

Chapter 17 371
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
register (data field) from the adapter card’s PCI configuration space.
(“Cause” = 32-bit status returned from io_pci-cfg_read_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI
backplane, or may not be responding. If the I/O slot has a power
indicator, verify it is on. Reseat the board, and if necessary call your
Hewlett-Packard representative for hardware assistance. If the
problem persists, the adapter card may be bad; try replacing the card.
8930 CLAS0001 MESSAGE: Unable to write to adapter card PCI configuration space.
CAUSE: While processing a request from an upper level tool program
such as LNKUTIL, the ISR encountered an error when trying to write
to a register (data field) in the adapter card’s PCI configuration space.
(“Cause = 32-bit status returned from io_pci-cfg_write_bit32).
ACTION: The adapter card may have been removed, moved to a
different slot, may not be making proper contact with the PCI
backplane, or may not be responding. If the I/O slot has a power
indicator, verify it is on. Reseat the board, and if necessary call your
Hewlett-Packard representative for hardware assistance. If the
problem persists, the adapter card may be bad; try replacing the card.
8960 CLAS0001 MESSAGE: (Varies)
CAUSE: A general error occurred during processing of an input event by
the main driver ISR state machine, and the code where the error
occurred neglected to specify a sublocation code value, so the value 8960
was used.
ACTION: Note all logged error messages. The main problem is described
by whatever was logged. But the driver also needs to be fixed to specify
a unique sublocation for those errors. Please see Appendix A ,
“Submitting a CR.”
9020 CLAS0001 MESSAGE: Unimplemented operation attempted.
CAUSE: The main driver ISR 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.