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

212 Chapter16
100VG-AnyLAN and HP-PB 100Base-T Error Messages
SDI Driver Specific Status Values
2120 CLAS0001 MESSAGE: Internal error while initiating a dump. Dump failed.
CAUSE: During processing of a fatal driver error, the driver attempted a
driver dump, but encountered an error while trying to get or reset a
timer (“Cause” = 32-bit status returned by the call to vg_start_timer).
This timer was to be used to avoid deadlock in case the dump process
did not respond; the driver cannot attempt a dump if a dump timer
cannot be started. If this error is reported, it is because the driver has
already encountered some other error.
ACTION: Typically preceded by another error message giving better
information about the original cause; check log data for that error and look it
up also. The driver did not dump, but will still attempt to auto-reset itself, up
to a total of 12 times or more.
2150 CLAS0001 MESSAGE: Cannot send a port message.
CAUSE: During final processing of a fatal driver error, the driver
attempted a driver dump, but was unable to send a dump event to the
dump process (“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: The driver did not dump, but will still attempt to auto-reset itself,
up to a total of 12 times or more.
2180 CLAS0001 MESSAGE: Internal error while initiating a dump. Dump failed.
CAUSE: During processing of some other fatal driver error, the driver
attempted a driver dump, but encountered an error. It then
encountered this second error while trying to clean up, when
attempting to release a dump timer it had obtained (“Cause” = 32-bit
status returned by the call to vg_stop_timer).
ACTION: Typically precededbyanother errorgiving betterinformationabout
the original cause; check log data for that error and look it up also. This error
is mainly informational, since the driver did not dump, but may be indicative
of other, possibly-related problems. The driver will still attempt to auto-reset
itself, up to a total of 12 times or more.
2210 CLAS0001 MESSAGE: Cannot get a system timer.
CAUSE: The driver attempted to get a system timer from I/O Services
but encountered an error (“Cause” = 32-bit status returned by the call
to io_get_timer). This is either caused by exhausting all timers due to
heavy system load, or by system software either failing to release
timers, or having some other bug.
ACTION: This is a fatal software error. The number of available timers is not
configurable, and the driver cannot operate without the necessary timers.
After reporting this error, the driver will die, then will either attempt an
auto-reset or else require a manual shutdown and restart. Typically followed
by another error giving more information about what kind of timer the driver
needed; check log data for that error and look it up also.