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

Chapter 17 289
PCI 100Base-T Error Messages
SDI Driver Specific Status Values
18 ($12) MESSAGE: Cannot close NM logging.
CAUSE: The link module configurator or deconfigurator attempted to
close access to the NM logging facility, but encountered an error.
ACTION: This is an informational warning that the logfile may still be
open. Use of the :SWITCHNMLOG command should not be affected,
however there may be a delay at system shutdown time. If this happens
every time, see Appendix A , “Submitting a CR.”
19 ($13) MESSAGE: Cannot unfreeze a memory area.
CAUSE: After previously freezing a data structure into system memory,
software encountered an error trying to unfreeze the same memory.
ACTION: This is an informational warning that some system memory
resources may have been lost. Software probably continued, ignoring
the error. Software may be confused, or the pointer to the memory area
may have been changed. If this happens every time, see Appendix A ,
“Submitting a CR.”
20 ($14) MESSAGE: Abnormal interrupts detected by adapter card.
CAUSE: While checking the cause of an adapter card interrupt, an
abnormal interrupt was found, such as transmit underflow, transmit
jabber timeout, receive buffer unavailable, or transmit or receive
process stopped.
ACTION: This event is informational. No action is required. The driver
will attempt to recover and continue, sometimes with some frame loss
which the upper layer protocols may attempt to recover, depending on
which abnormal interrupts occurred. However, most of these interrupts
should not occur during normal operation, so if they are occurring
frequently, see Appendix A , “Submitting a CR.”
22 ($16) MESSAGE: No DMA buffer was available for a received frame.
CAUSE: On receipt of an inbound data frame, the driver attempted to
dequeue a buffer from the inbound buffer cache for one of the bound
protocols, but the cache was empty.
ACTION: This is an internal warning. The driver may use it to detect
the need to request more buffers. Typically the inbound frame is
discarded in this case for flow control reasons, instead of being queued.
25 ($19) MESSAGE: Cannot initiate a dump. Already dumping.
CAUSE: A user attempted to force a driver dump while a previous driver
dump was still occurring.
ACTION: A dump of your problem is already being produced. Wait a
minute or two for the dump to finish. Forward the resulting
NETDMP##.PUB.SYS to Hewlett-Packard for analysis if necessary, and
see Appendix A , “Submitting a CR.”