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

590 Chapter22
Logging Location Codes Continued
Net Timers Logging Location Codes
associated with that net timer and others. A timer list’s system timer is
normally reset whenever insertion of the new net timer changed the
first interval in the list. (PORT = net timer ID).
ACTION: Review information regarding the previous errors, for possible
hints as to the cause. If necessary, submit an CR, noting this and
previous Net Timers errors.
1220 CLAS0002 MESSAGE: Cannot start a timeout
CAUSE: This is supplemental logging to a previous Net Timers error.
While attempting to reschedule a running net timer, the timer was
successfully removed from the old interval it was running in, but there
was a problem restarting it. To get the net timer running again, all
steps necessary to attach it to a new interval must succeed. (PORT =
net timer ID).
ACTION: Review information regarding the previous errors, for possible
hints as to the cause. If necessary, submit an CR, noting this and
previous Net Timers errors.
2020 CLAS0002 MESSAGE: Not up for processing
CAUSE: An attempt was made to free a net timer before or during Net
Timers startup, or during or after shutdown. Timers cannot be freed
unless Net Timers is completely up. (PORT = net timer ID).
ACTION: If this occurs during network shutdown, it can probably be
ignored. If it occurs at any other time, submit an CR. Whether the net
timer ID being freed was valid or not is not known.
2030 CLAS0002 MESSAGE: Bad timer ID specified
CAUSE: An attempt was made to free a net timer having an ID of zero
(PARM = 0).
ACTION: There is a bug in the calling module. Probably that module
previously attempted to get a timer, but ignored an error reported by
Net Timers and saved the returned ID of zero for later use. It is now
attempting to free that nonexistent timer. This may lead to other errors
or hangs in the calling module. Submit an CR.
2040 CLAS0002 MESSAGE: Accessed a freed timer
CAUSE: An attempt was made to free a net timer for which a deferred
release has already been posted. Deferred release is used only during
the pop of a timer, since it cannot be freed until the trap routine exits,
completing the pop. Since freed net timers can be immediately
reallocated to anyone, they cannot be safely freed twice. (PORT = net
timer ID).
ACTION: This probably means a Transport timer trap routine has
accidentally re-freed a timer it already freed. Another possibility is that
a second processor has attempted to free the same timer while that trap
routine was still executing; this might be unlikely due to timing