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

274 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
(“Cause”= 32-bit address of the DMA step against which the corruption
was detected). Probably the driver attempted to perform a DMA
transfer which was not a 4-byte multiple in length.
ACTION: This is a warning that some timer resources may have been
lost. The link did not connect. Typically preceded by another error
message giving better information about the original cause; check log
data for that error and look it up also. Unless this happens constantly,
the system should continue to run, and the driver will probably retry
the connect. If the problem happens every time, see Appendix A,
“Submitting an SR.”
MESSAGE: Powerfail detected.
9320 CLAS0001 CAUSE: A driver DMA operation completed, but when the driver read
from an adapter card register (io_dma_link) to determine where DMA
ended, it found all ones. The driver has decided this indicated a power
failure has occurred (“Cause” is not used here).
ACTION: If a power failure has actually occurred, this error can be
ignored; the driver should recover automatically. But if the same
problem happens all the time, see Appendix A, “Submitting an SR.”
MESSAGE: Driver is out of DMA resources.
9380 CLAS0001 CAUSE: When processing a received data frame, the driver successfully
obtained a new buffer, then was unable to obtain a DMA step to
transfer the frame into that buffer (“Cause”= 32-bit value of the ring
number which was out of steps: HP use only).
ACTION: This error indicates a bug in the link driver. The driver is
designed to avoid this situation through use of various queues and
checks. If the problem happens often, see Appendix A, “Submitting an
SR.”
The driver reused the buffer and dropped the received packet. Upper
layer protocols typically retransmit lost packets, so operation of the
system and applications should continue with only minimal
degradation.
MESSAGE: Frame received when no queue entry was available.
9410 CLAS0001 CAUSE: When processing an interrupt for a received data frame, the
driver was not able to locate the adapter card data memory frame
containing the data (“Cause” is not used here). The driver thinks there
are no more adapter card memory frames in which to receive incoming
frames, yet the card has reported another frame anyway. The driver is
designed to maintain synchronization with the card, therefore it
appears that either an out-of-sync condition exists, or the card has a
problem.