I've attached a trace of irqbalance while my benchmark test is underway.
Also, I should a detail to the original bug: Killing irqbalance only
works if you kill it before the benchmark has ever run. If you kill it
later on (e.g. before running another benchmark run) then the damage is
done and you get ksoftirqd processes spinning as before.


** Attachment added: "strace of irqbalance-0.55 while the test is running"
   http://launchpadlibrarian.net/19588979/irqbalance-trace

-- 
irqbalance causes ksoftirqd to use 100% CPU
https://bugs.launchpad.net/bugs/297121
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to