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

240 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. Otherwise, the MII
bus may have failed; replace the adapter card. If the same problem
persists, see Appendix A, “Submitting an SR.”
MESSAGE: Driver encountered a hardware problem.
5120 CLAS0001 CAUSE: While attempting to alter 100Base-T loopback mode during
diagnostic testing, the driver read from a loopback control register on
the PHY chip of the adapter card, but encountered an error. Most likely
the PHY has failed, but a power failure may have occurred (“Cause”=
32-bit status returned by the call to vg_mii_read16).
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. Otherwise, the MII
bus may have failed; replace the adapter card. If the same problem
persists, see Appendix A, “Submitting an SR.”
MESSAGE: Driver encountered a hardware problem.
5150 CLAS0001 CAUSE: While attempting to alter 10Base-T loopback mode during
diagnostic testing of a 100VG-AnyLAN adapter card, the driver read
from a PHY control register in the LAN controller chip of the card, but
encountered an error. Most likely the chip has failed, but a power
failure may have occurred (“Cause”= 32-bit status returned by the call
to vg_mii_read16).
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. Otherwise, the MII
bus may have failed; replace the adapter card. If the same problem
persists, see Appendix A, “Submitting an SR.”
MESSAGE: An unexpected transmit condition was encountered.
5180 CLAS0001 CAUSE: While attempting to initiate DMA to send some transmit data
to the adapter card, driver software found its data structures to be in an
unexpected state (“Cause” is not used here). The state of all transmit
queues was not one of the legal states predicted at design time.
ACTION: This is a fatal software error. The driver will not attempt to
continue. After reporting this error, the driver will die, then will either
attempt an auto-reset or else require a manual shutdown and restart. If
the problem persists, first activate link tracing, reproduce the problem,
stop tracing, and save the resulting link trace file. Then see Appendix
A, “Submitting an SR.”
MESSAGE: A data buffer is too long.
5210 CLAS0001 CAUSE: During diagnostic loopback testing, the driver was asked to
prepare a data block for transmission, but the block length or memory
allocation was beyond the driver’s DMA capabilities (“Cause”= 32-bit
total length of the requested transmission).