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

Chapter 17 375
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: This error is informational. The driver will continue to
shutdown. However, if the error persists, there could be data corruption
in the driver or the I/O system. Depending on how frequently the error
is seen, or if other similar errors are noted, this may require a system
dump file to diagnose; see Appendix A , “Submitting a CR.”
9780 CLAS0001 MESSAGE: Could not unmap and I/O virtual address.
CAUSE: Most likely during a shutdown of the driver (normal shutdown
or because of an auto-reset precipitated by an earlier error), the ISR
was attempting to release its data structures, including previously
allocated I/O virtual addresses. However, an error was returned.
(“Cause” = 16-bit SDI status returned from Lnk_unload_io_addr).
ACTION: This error is informational. The driver will continue to
shutdown. However, if the error persists, there could be data corruption
in the driver or the I/O system. Depending on how frequently the error
is seen, or if other similar errors are noted, this may require a system
dump file to diagnose; see Appendix A , “Submitting a CR.”
9810 CLAS0001 MESSAGE: Abnormal interrupts detected by adapter cards.
CAUSE: The adapter card generated an abnormal interrupt that was
detected by the ISR. (“Cause” = 32-bit status containing the contents of
the adapter card’s status register).
ACTION: This error message is informational; the driver may be able to
continue processing and recover from the abnormal interrupt, after
updating statistics and logging the event. However, if the problem
persists, it could indicate a hardware problem on the network or with
the network configuration. The “cause” field (adapter card status
register contents) may indicate which type(s) of abnormal condition
were detected by the adapter card:
• Bit 1: Transmit process stopped (this may be in response to a
specific request from the driver, depending on recent events/requests
processed by the driver).
• Bit 3: Transmit jabber timeout.
• Bit 5: Transmit underflow.
• Bit 7: Receive buffer unavailable.
• Bit 8: Receive process stopped (this may be in response to a specific
request from the driver, depending on recent events/requests
processed by the driver).
• Bit 9: Receive watchdog timeout.
• Bit 13: Fatal bus error.