On 01/08/12 20:17, Henrik Carlqvist wrote:
> Blumf <bl...@hotSPAMmail.com> wrote:
>> Recently my system (Slack64 13.37) seems to be spinning its wheels.
>>
>> Check this example from top:
>>
>> PID USER %CPU %MEM TIME+ COMMAND
>> 18671 scott 95 3.0 1534:23 firefox
>> 12606 scott 53 1.7 1639:36 thunderbird-bin
>> 3 root 16 0.0 1722:03 ksoftirqd/0
>> 13 root 14 0.0 1564:45 ksoftirqd/2
>> 9 root 14 0.0 1707:23 ksoftirqd/1
>> 4307 scott 3 0.2 141:31.75 audacious2
>>
>> What's going on? I can't figure out what the best course of action is to
>> diagnose this.
>
> If you want to dig deeper into this you might get some clue from the
> output from strace:
>
> strace -p 18671
>
> However, strace usually gives a lot of output. It does not show heavy CPU
> usage like calculations, but system calls like opening files and stuff
> like that.
Now that's interesting, when I attach and detach strace to firefox and
thunderbird, they calm down and no longer hog the CPU.
I think this may be down to qbittorrent (which wasn't present in the
example as I had killed it already), that's taking up ~150% (3 core
chip). strace on that is showing mostly futex calls, constantly. e.g.:
futex(0xcfd768, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0xcfd76c, FUTEX_WAIT_PRIVATE, 212720197, NULL) = -1 EAGAIN
(Resource temporarily unavailable)
> The next step would be to recompile the hogging application with the -g
> switch to gcc and then run it in a debugger like gdb or, maybe more
> userfriendly interface, ddd. Valgrind with --tool=callgrind together with
> kcachegrind is also useful to see were applications spend their CPU
> cycles, but again, this requires that the application was compiled with
> the -g switch.
I'll have a fiddle with this, but qbittorrent was working okay
originally. I have a feeling something is wrong with an update I've
applied elsewhere, been having nothing but trouble with Slack 13.37 from
day one so I may end up just nuking the install as soon as 14.0 comes
out (soon I hope).
> I don't have much ideas for those ksoftirq processes. Maybe it could be
> that it is your CPU that has become slow rather than the processes
> demanding more CPU power? Check with dmesg if you see any odd messages
> like CPU cache disabled or anything else that would explain a slower CPU.
Yeah, I get the feeling that they're a symptom of stuff being overloaded
rather than a cause.
Blumf