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

212 Chapter16
100VG-AnyLAN and 100Base-T Error Messages
SDI Driver Specific Status Values
MESSAGE: Cannot delete a buffer pool.
1980 CLAS0001 CAUSE: During a link-close operation by an upper level subsystem, the
link module deconfigurator encountered an error while trying to delete
a control buffer pool (“Cause”= 32-bit status from the call to
bmgr_delete_pool).
ACTION: This is an informational warning that some system memory
resources may have been lost. Probably not all buffers were freed before
the pool was deleted. The module deconfigurator reported an error, but
attempted to continue with the close. If this happens every time, see
Appendix A, “Submitting an SR.”
MESSAGE: Cannot send a port message.
2030 CLAS0001 CAUSE: During final processing of a fatal driver error, the driver
attempted a standard auto-reset instead of dying. However, its attempt
to send a reset message to itself failed (“Cause”= 32-bit status returned
by the call to send_msg). If this error is reported, it is because the
driver has already encountered some other error.
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.
Otherwise, since the auto-reset failed, the driver dies instead, notifying
upper layer software via an asynchronous event message if possible.
The network and/or link must now be stopped and restarted. Some
upper layers may stop the link on their own in response to an event
message. If not, manually stop the network and/or link via the
appropriate operator command (for example, :NETCONTROL STOP) and
then restart it.
MESSAGE: Cannot send a port message.
2060 CLAS0001 CAUSE: While notifying upper level subsystems that the driver
detected a serious error, powerfail, or reset, an attempt to send an
asynchronous event message to one of those subsystems failed
(“Cause”= 32-bit status returned by the call to send_msg).
ACTION: This is a warning that one or more subsystems may not be
aware the link has had a problem. The subsystem(s) may have failed to
close the driver as part of their shutdown. The driver will continue with
its error recovery actions, and no user action is required. If this
happens every time, see Appendix A, “Submitting an SR.”