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
Public bug reported:
Binary package hint: irqbalance
irqbalance-0.55-2 seems to misconfigure my Linux box. I have a Sun
4100M2 (2xdual core AMD Opteron 2216) running Ubuntu Hardy (64 bit). I
have been benchmarking software that performs lots of network I/O, using
8 network cards on the box
Public bug reported:
Binary package hint: gnome-screensaver
gnome-screensaver on my machine is configured to just blank the screen
after 10 minutes. No animations, no pretty pictures, nothing.
Yet, over an uptime of 20 days, the gnome-screensaver process shows 225 minutes
of CPU time.
For
I hit (what I think was) this problem with a fresh install of Hardy
AMD64. My SATA controller is:
00:05.0 IDE interface: nVidia Corporation MCP55 SATA Controller (rev a3)
(prog-if 85 [Master SecO PriO])
Subsystem: Hewlett-Packard Company Unknown device 1714
I found that only my *second*
