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

186 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: An unexpected transmit condition was encountered.
126 ($7E) 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. The state of all transmit queues was not one of the
legal states predicted at design time.
ACTION: This is a fatal software error. 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, take a link trace
of the problem, then see Appendix A, “Submitting an SR.”
MESSAGE: Illegal access to saved port message area.
128 ($80) CAUSE: While completing an old blocking request (requiring a driver
exit and later reply), the driver found that the entry in the pending
message save area, where the request was supposedly saved, was no
longer in use, or was not within the range of legal table indexes.
ACTION: This fatal software error is only caused by a bug or memory
corruption, because the driver should never be trying to complete the
same message twice, or passing an illegal index. 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, take a
link trace of the problem, then see Appendix A, “Submitting an SR.”
MESSAGE: Frame received when no queue entry was available.
129 ($81) 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. 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.
ACTION: The driver acknowledged and dropped the interrupt and the
received packet. Many upper layer protocols typically retransmit lost
packets, so operation of the system and applications may continue with
only minimal degradation. Exhausting all receive resources would be a
highly unusual condition. If all receive resources have really been
exhausted, network load may be extremely high, and/or the HP-PB bus
may be preventing frames from being returned to the card in a timely
manner; incoming frames are probably now being dropped. Otherwise
there may be a bug in the link driver. If the problem happens often, see
Appendix A, “Submitting an SR.”
MESSAGE: Cannot read current multicast list.
130 ($82) CAUSE: During a link-open or close operation by an upper level
subsystem, the link module configurator tried to read the current list of
multicast addresses produced by the subsystem, but encountered an
error on the read.