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

176 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
caused the error. Activate link tracing, reproduce the problem, then
stop link tracing and save the resulting NMTCnnnn.PUB.SYS trace data
file. See Appendix A, “Submitting an SR.”
MESSAGE: A received frame could not be delivered.
43 ($2B) CAUSE: Just before delivering a received data frame to an upper layer
protocol, the driver found that the rendezvous table entry specified in
the buffer was not in the proper state.
ACTION: This is an internal error which detects a normal race
condition. Probably the protocol separated from the driver while a
frame destined for it was in motion. The frame was not delivered, and
the buffer was silently released. No action is required.
MESSAGE: A received frame could not be delivered.
43 ($2B) CAUSE: Just before delivering a received data frame to an upper layer
protocol, the driver found that the rendezvous table entry specified in
the buffer was not in the proper state.
ACTION: This is an internal error which detects a normal race
condition. Probably the protocol separated from the driver while a
frame destined for it was in motion. The frame was not delivered, and
the buffer was silently released. No action is required.
MESSAGE: Link tracing is already enabled.
46 ($2E) CAUSE: The driver received a request to turn link tracing on when it
was already on.
ACTION: This event is informational. No action is required. An error
reply was sent in response to the request. Trace was not started by this
request this time, but it remains on.
MESSAGE: Link tracing is already disabled.
47 ($2F) CAUSE: The driver received a request to turn link tracing off when it
was already off.
ACTION: This event is informational. No action is required. An error
reply was sent in response to the request. Trace was not stopped by this
request this time, but it remains off.
MESSAGE: Driver encountered a hardware problem.
50 ($32) CAUSE: This is a generic hardware error, reported when any of the
driver’s hardware access routines reports an error. By itself it is not
descriptive of the problem. This error is often seen as a result of
previous power failures, MII or EEPROM read/write errors, or other
low-level hardware problems.
ACTION: When this error occurs as a result of previous errors, it mainly
serves as a way to track the sequence of the failure back to what was
happening at the time. Check for those errors and look them up for an
additional explanation of the problem.