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

236 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
After this problem occurs, the driver will enter a “broken” state where
is may not respond to further requests. If possible, run the VGPBA tool
program, and use it to force a driver dump, then forward the resulting
NETDMP##.PUB.SYS file to Hewlett-Packard for analysis. After a dump,
the driver will attempt to auto-reset itself and continue. You may also
use VGPBA to attempt a manual reset of the driver, after which it may
be possible to continue.
MESSAGE: Driver received an unknown port message.
4510 CLAS0001 CAUSE: Some module on the system has sent the driver a message
having an unknown message descriptor. The driver does not implement
any messages having that descriptor (“Cause”= 32-bit value of the
message descriptor field).
ACTION: The driver took no action on the message, and dropped it.
However, if the problem occurs frequently, your system may not be set
up properly. The driver traces the message which it received. If you can
repeat the problem, first enable link tracing. Then reproduce the
problem, stop tracing, and save the resulting trace data file for analysis
by Hewlett-Packard. See Appendix A, “Submitting an SR.
MESSAGE: Cannot send a port message.
4730 CLAS0001 CAUSE: During ISR processing, an attempt by the ISR to wake up the
driver by sending a message to it failed (“Cause”= 32-bit status
returned by the call to send_msg).
ACTION: This error is likely an indication of a more serious system
software problem, and may be followed by a system abort. Probably all
message frames have been exhausted by some module running on the
system. Further recovery actions may not be possible; if the system
fails, take a memory dump and reboot.
The driver wakeup did not occur, so a link hang is now possible. It is
also possible that if a system abort does not occur, other activity, such as
transmissions by upper layer protocols, will awaken the driver, such
that normal operation continues. If the link hangs and a system abort
does not occur, try using VGPBA to attempt a manual reset, or try
stopping and restarting all networks using the link driver.
MESSAGE: Out of internal comm frame resources.
4760 CLAS0001 CAUSE: While attempting to request action from its DVR module, the
driver’s ISR found that no available communication frames were
available on the referenced queue (“Cause” is not used here).
ACTION: This is a fatal software error. The number of available comm
frames is not configurable, and the driver cannot operate if frames run
out. After reporting this error, the driver will attempt a driver dump,
then will auto-reset and attempt to continue. Typically followed by
another error giving more information about what kind of comm the
driver was trying to send; check log data for that error and look it up
also.