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

Chapter 16 273
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: Error from upper layer protocol read completor.
9200 CLAS0001 CAUSE: The driver finished transferring a data frame, but encountered
an error while trying to send the frame to an upper layer protocol via a
port message (“Cause”= 32-bit status returned by the call to
vg_send_msg).
ACTION: This is an informational error only. The driver has
incremented a statistic, logged the error, and will now attempt to free
the receive buffer and continue. However, the protocol may not have
received the inbound frame, therefore some applications could be hung.
There is probably a problem in the upper layer protocol. Also, if the
protocol had already freed the buffer, this may have resulted in a
SysAbort from the Buffer Manager. If the problem occurs frequently,
start link tracing, reproduce the problem, then stop link tracing and
save the resulting NMTC####. PUB.SYS file for analysis by
Hewlett-Packard, and see Appendix A, “Submitting an SR.”
MESSAGE: Bad message for current state.
9230 CLAS0001 CAUSE: The driver finished transferring a diagnostic loopback data
frame, but then discovered it was either not in loopback mode anymore,
or there was no pending diagnostic request message (“Cause”= 32-bit
encoded value, giving driver current state: HP use only).
ACTION: This problem most likely occurred while diagnosing some
previous problem. It an informational error only, and the driver will log
it and attempt to continue. If this happens frequently, see Appendix A,
“Submitting an SR.”
MESSAGE: Driver encountered a software problem.
9260 CLAS0001 CAUSE: During a diagnostic loopback test, the driver finished
transferring a diagnostic loopback data frame,but encountered an error
while trying to stop and release a timer (“Cause”= 32-bit status from
the call to vg_stop_timer). This timer was used to verify loopback
data arrives. If this error is reported, it is because the driver has
already encountered some other error.
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: Driver has detected data corruption.
9290 CLAS0001 CAUSE: A driver receive-frame DMA operation completed, but in doing
a quick check of the DMA’ed data, the driver found all ones in the first
4 words, indicating some kind of driver/adapter card bug has occurred