| Summary: | 100% cpu occupied by kworker even when the application is closed | ||
|---|---|---|---|
| Product: | [Unmaintained] ksysguard | Reporter: | aldo andreani <aldoandr> |
| Component: | ksysguard | Assignee: | KSysGuard Developers <ksysguard-bugs> |
| Status: | RESOLVED UNMAINTAINED | ||
| Severity: | critical | CC: | cfeck, joco.hu, ostap.tymchenko |
| Priority: | NOR | ||
| Version First Reported In: | 4.11.10 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | attachment-29061-0.html | ||
|
Description
aldo andreani
2014-09-05 06:57:36 UTC
Did you double-check with "top" in Konsole? It might be the processes are just displayed wrong in ksysguard. Created attachment 88575 [details] attachment-29061-0.html bug-control@bugs.kde.org [5] cc christoph@maxiom.de sorry, i can't use the console, but if you mean that kworker is correct and the bug is that ksysguard reports it as wrong, this is impossible since the cpu is really engaged and the fan is at the maximum speed even if no programs have been started; under this conditions the pc is useless and the only thing to do is to restart it with the hope that the problem doesn't occur again Il 05.09.2014 13:37 Christoph Feck ha scritto: > https://bugs.kde.org/show_bug.cgi?id=338817 [1] > > Christoph Feck changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |christoph@maxiom.de [3] > > --- Comment #1 from Christoph Feck --- > Did you double-check with "top" in Konsole? It might be the processes are just > displayed wrong in ksysguard. > > -- You are receiving this mail because: You reported the bug. Scopri istella, il nuovo motore per il web italiano. Istella garantisce risultati di qualità e la possibilità di condividere, in modo semplice e veloce, documenti, immagini, audio e video. Usa istella, vai su http://www.istella.it?wtk=amc138614816829636 in my first message i wrote "i can't guarantee that the situation is completely resolved but at the moment it's ok"; now i can confirm that the situation is better but the problem is not completely resolved, therefore i believe that there are additional programs "exciting" kworker. i believe it would be useful to stop all the processes/services running automatically when the computer starts up, except those really important (the net?): could you tell me the names of these processes? moreover i don't know how this can be done: i was a windows user and i could do it with ccleaner or with msconfig now i can tell you that there is a situation more important than the installed programs: the pc is a toshiba satellite sm30-154 with pentium-m and 0.5 gb ram where also windows xp is installed therefore when you switch it on, the first thing you see is a menu asking if you wish to load lubuntu or xp; if you press "enter" you go at once to lubuntu and the same happens (but after 10 sec.) if you don't press any key: in the first case lubuntu doesn't starts correcly (100% cpu occupied by kworker) whereas, if you don't press "enter", lubuntu starts correctly. so i believe now that your program doesn't have any bug; if you wish you may take into account what i wrote about a clean uninstall Thanks for the update. I am closing this report, unless there is more evidence that the Linux kernel threads are running havoc because of ksysguard. of course you can close it, thanks Hi, I see that this bug is closed, but I have been experiencing the same issue, so I would like to reopen it. At random times, my computer's overall FPS will drop below ~1, and when opening btop I see "kworker" using 95%+ of cpu. The only fix is restarting. This ticket is for KDE 4, which is long unmaintained. If you can reproduce this issue with Plasma 6, please report a new ticket. Additionally, "kworker" is an abbreviation for "kernel work thread". If such a process consumes CPU, please report this issue to Linux kernel developers. |