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

Chapter 16 175
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
transmission, on the assumption some extra quads will free up.
35 ($23) MESSAGE: Driver is out of card memory resources.
CAUSE: The driver attempted to dequeue a card memory buffer entry
from a specific queue, but the queue was empty.
ACTION: None. This is an internal error used to detect the empty queue
condition. In most cases, the driver already knows the queue is not
empty, and does not check for this error. If this error occurs as part of
some other problem, see Appendix A , “Submitting a CR.”
39 ($27) MESSAGE: The link is already started.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator attempted to create a new instance of the link
driver, but discovered the driver was already created.
ACTION: This event is informational. No action is required. The module
configurator will ignore this warning and continue to bring the link
driver up, so that the number of users may be checked.
39 ($27) MESSAGE: The link is already started.
CAUSE: During a link-open operation by an upper level subsystem, the
link module configurator attempted to create a new instance of the link
driver, but discovered the driver was already created.
ACTION: This event is informational. No action is required. The module
configurator will ignore this warning and continue to bring the link
driver up, so that the number of users may be checked.
41 ($29) MESSAGE: Driver received an unknown port message.
CAUSE: The driver received a port message which it does not
implement, or containing a function code which it does not implement.
ACTION: This is an informational error only. If this error occurred as
part of a driver reset operation, it may be ignored. The driver did not
attempt to return an error reply to the message sender. That sender
may now be hung, awaiting a reply. Attempt to determine what action
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 a CR.”
43 ($2B) MESSAGE: A received frame could not be delivered.
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.