We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
Hi,
I was wondering if you were still having this problem?
Regards
chuck
** Changed in: irqbalance (Ubuntu)
Importance: Undecided = Low
** Changed in: irqbalance (Ubuntu)
Status: New = Incomplete
--
irqbalance causes ksoftirqd to use 100% CPU
https://bugs.launchpad.net/bugs/297121
I've got a couple potentially more useful traces.
The first is a strace of irqbalance-0.12, starting from a fresh reboot
with the irqbalance init script disabled (so the trace shows the first
time that irqbalance started messing with the IRQs). The trace continues
while the benchmark is run.
I
** Attachment added: strace of irqbalance-0.55 from startup
http://launchpadlibrarian.net/19589900/irqbalance-0.55.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
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
