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

Chapter 17 291
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
suppressed. No attempt is made to determine whether the dumps are
duplicates of the same problem. The driver did not dump, but will still
attempt to auto-reset itself, up to a total of 12 times or more. There is
apparently something wrong, since many driver dumps are occurring.
Collect binary copies of all dump files (NETDMP##.PUB.SYS) on tape for
analysis by Hewlett-Packard and see Appendix A , “Submitting a CR.”
34 ($22) MESSAGE: Low on transmit descriptor resources.
CAUSE: This status should not normally be logged externally. It is
designed for internal use by the driver to signal that either no transmit
descriptor was available when one was requested for a transmit, or that
a given transmit was segmented in too many places and needs to be
compacted prior to transmission.
ACTION: This status should not be logged externally, so if it is seen, see
Appendix A , “Submitting a CR.”
35 ($23) MESSAGE: Received and discarded a long frame.
CAUSE: When processing a frame reception, the link driver found that
the adapter has indicated the frame data spanned more than a single
descriptor, which is not allowed.
ACTION: This is a warning only; the driver automatically reset the
receive descriptors and continued. However, some frames may have
been lost. If the problem occurs often, use link tracing to determine the
source of the long frame transmissions.
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