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

366 Chapter17
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: This informational error is typically preceded by another error
message giving better information about the original cause; check log
data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.
8100 CLAS0001 MESSAGE: Driver encountered a software problem.
CAUSE: During a link connect attempt, the driver received an interrupt
from the PHY chip on the adapter card and passed that to a lower level,
but the lower level returned an error (“Cause” = 32-bit status from the
call to pbt_isr_call_phy_state_machine).
ACTION: This informational error is typically preceded by another error
message giving better information about the original cause; check log
data for that error and look it up also. At this level, the error is just
logged, then the driver will attempt to continue, if the lower level error
was not already fatal.
8300 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: While attempting to process a restart request, the ISR first
tried to stop the transmit processing on the adapter card, but received
an error. (“Cause” = 32-bit status from pbt_isr_stop_tx). Additional
errors may have been logged with more information about the failure.
ACTION: The driver may become unusable or attempt an auto-reset. If
the driver appears to hang, try to shutdown the network manually and
then restart it. Most likely, once the reset is complete and the driver has
“reinitialized” the hardware (card), the driver can resume operating
normally.
If the problem persists, it may indicate a bad adapter card; try
replacing the card.
8330 CLAS0001 MESSAGE: Driver encountered a hardware problem.
CAUSE: While attempting to process a restart request, the ISR first
tried to stop the receive processing on the adapter card, but received an
error. (“Cause” = 32-bit status from pbt_isr_stop_rx). Additional
errors may have been logged with more information about the failure.
ACTION: The driver may not be able to complete the restart. If the
driver appears to hang, try to shut down the network manually and
then restart it. Most likely, once the reset is complete and the driver has
“reinitialized” the hardware (card), the driver can resume operating
normally.
If the problem persists, it may indicate a bad adapter card; try
replacing the card.