Cisco Cisco IOS Software Release 12.0(1)T 故障排查指南
The scheduler has been changed in later Cisco IOS software code. In order to keep track of whether the
queues have been changed (so it can better determine whether or not the process is thrashing), the scheduler
now notes whenever an item is removed from the queue, and only prints the thrashing message if nothing gets
removed for a while.
queues have been changed (so it can better determine whether or not the process is thrashing), the scheduler
now notes whenever an item is removed from the queue, and only prints the thrashing message if nothing gets
removed for a while.
Most of the time, the queue thrashing message is cosmetic.
These messages are not always caused by a software bug. They can be issued in response to either
instantaneous or sustained demand on the router. Increased or persistent messages can indicate that the traffic
load needs to be reviewed.
instantaneous or sustained demand on the router. Increased or persistent messages can indicate that the traffic
load needs to be reviewed.
Note: These code changes are reported under Cisco bug ID CSCdj68470 (registered customers only) .
SCHED−3−UNEXPECTEDEVENT
This message appears whenever a process receives an event that it does not know how to handle. For
example:
example:
%SCHED−3−UNEXPECTEDEVENT: Process received unknown event (maj 10, min 0).
−Process= "IP SNMP", ipl= 0, pid= 23
−Traceback= 602842B8 6017CFB8 6017CFA4
There are several possible causes of this problem:
The most likely cause is that one process directly wakes up another process, and passes major and
minor event numbers to the process. If the sending process wakes up the wrong process, the receiving
process does not know how to handle the received major and minor event numbers. The process
might perform the wrong action if it expects an event with matching major and minor event numbers,
or it might print this message. Use the output of the show process command to help determine which
process(es) might have sent a direct wakeup to a process.
minor event numbers to the process. If the sending process wakes up the wrong process, the receiving
process does not know how to handle the received major and minor event numbers. The process
might perform the wrong action if it expects an event with matching major and minor event numbers,
or it might print this message. Use the output of the show process command to help determine which
process(es) might have sent a direct wakeup to a process.
•
Another possible cause of this problem is that a development engineer has added code to register for
an event, but has not added the code to handle the event.
an event, but has not added the code to handle the event.
•
A subroutine called by the process may have registered for a new event, but has not deregistered the
event before it exits.
event before it exits.
•
These messages are always due to a software bug. Based on the process that did not know how to handle an
event, you can run into different bugs in the Cisco IOS software.
event, you can run into different bugs in the Cisco IOS software.
If the process is equal to either Exec or Virtual Exec, you are most likely to run into these issues:
%SCHED−3−UNEXPECTEDEVENT: Process received unknown event (maj 80, min 0).
−Process= "Exec", ipl= 0, pid= 20
−Traceback= 604A0D68 6049B400 6049C974 601B2F5C 601B338C 601CC384 601CC9E0 601F5628
602383EC 602383D8
or
%SCHED−3−UNEXPECTEDEVENT: Process received unknown event (maj 80, min 0).
−Process= "Virtual Exec", ipl= 0, pid= 2
−Traceback= 60479FA0 60474638 60476474 601B0E20 601B0A38 601E5088 601E5B08 601F0A54
60231324 60231310
This error message is caused by debug code that was accidentally left in some older versions of code. It has
reappeared in the Cisco IOS Software 12.0 mainline release. The error message is likely to occur if you have
TACACS configured and you execute the show line command on the command line interface (CLI) of the
router. The error message has no affect on the functionality of the router, so this can be considered as a
reappeared in the Cisco IOS Software 12.0 mainline release. The error message is likely to occur if you have
TACACS configured and you execute the show line command on the command line interface (CLI) of the
router. The error message has no affect on the functionality of the router, so this can be considered as a