Brandon,

Just to re-iterate things:

1. Rescheduling Interrupts are not necessarily a problem - they are just show 
that the scheduler is working hard to distribute load across multiple cores to 
keep the processors evenly load and keep overall CPU power down. The main issue 
is if are they excessive (how many per second) and if so, what is causing them.
2. To find out what is causing them, it is good to look at the interrupt 
activity over a period of time, by looking at /proc/interrupts. For example, 
capturing /proc/interrupts in a log, sleeping for 10 seconds and capturing 
/proc/interrupts again. Take the 1st results from the 2nd and you will then see 
which interrupts may be causing the wakeups that cause the rescheduling 
interrupts activity.  This may show a mis-configured BIOS (very unlikely, but 
did happen in Barteq's case).
3. The next thing to look at is user space program activity. Some apps do 
excessing sleep/wakeups on many threads which cause the scheduler to try to 
load balance, which shows up a "rescheduling interrupts".  A good way to see 
system activity is use vmstat and look for context switch (cs) activity. If 
this is excessively high, then one needs to find out which application(s) are 
contributing to this. The top command is a quick way of seeing which processes 
are using a lot of CPU and possibly causing this activity. 

Hope this helps.

-- 
Kernel 2.6.24-2 causing ~1000 wakeups by "Rescheduling Interrupts"
https://bugs.launchpad.net/bugs/177895
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to