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

272 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
are probably now being dropped. Otherwise there may be a bug in the
link driver. If the problem happens often, see Appendix A , “Submitting
a CR.”
9440 CLAS0001 MESSAGE: Frame received when no queue entry was available.
CAUSE: When processing an interrupt for a received diagnostic loopback
data frame, the driver was not able to locate the adapter card data
memory frame containing the data (“Cause” is not used here).
ACTION: This error indicates a bug in the link driver. 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
is appears that either an out-of-sync condition exists, or the card has a
problem.
Note that exhausting all receive resources would be a highly unusual
condition, especially for loopback testing. If all receive resources have
really been exhausted, the HP-PB bus may be preventing frames from
being returned to the card in a timely manner. If the problem happens
repeatedly, see Appendix A , “Submitting a CR.”
The driver acknowledged and dropped the interrupt and the received
frame. The diagnostic should detect a timeout error then continue.
9470 CLAS0001 MESSAGE: Adapter card LAN controller reported a fatal error.
CAUSE: The link driver received an adapter check interrupt from the
LAN Controller chip on the adapter card, indicating a fatal error has
been detected (“Cause” = 32-bit hex value of the channel parameter
register in the chip: see the following list).
ACTION: This error typically indicates a driver bug has resulted in
incorrect use of the LAN Controller chip, however it could also indicate
an adapter card hardware problem. The driver will now attempt to
perform a dump of all host context data structures and adapter card
memory, then reset itself and continue. Decode the “Cause” to
determine the next action to take.
The “Cause” field is chip-specific, and is decoded as follows. At the time
of the failure:
• Bit 31 is the upper hex bit. Each hex digit is 4 bits long.
• Bit 21 is 1 if a high priority operation was in progress, 0 if normal
priority.
• Bit 20 is 1 if the controller was fetching an instruction, 0 if it was
transferring frames.
• Bit 19 is 1 if the controller was working on receiving inbound data, 0
if it was a transmitting outbound data.