Bug 373183 - CPU load is reported as more than 100%
Summary: CPU load is reported as more than 100%
Status: RESOLVED WORKSFORME
Alias: None
Product: ksysguard
Classification: Unmaintained
Component: ksysguard (other bugs)
Version First Reported In: 5.7.5
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KSysGuard Developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-12-02 12:30 UTC by Lastique
Modified: 2018-10-29 02:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
The screenshot illustrating the problem (104.39 KB, image/png)
2016-12-02 12:30 UTC, Lastique
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lastique 2016-12-02 12:30:49 UTC
Created attachment 102578 [details]
The screenshot illustrating the problem

The System Monitor application occasionally shows more than 100% CPU load for some processes that actually load all cores (in my case, it's ffmpeg compressing a 1080p video with libx265). Other utilities, such as top and htop, never exceed 100% load for the process (top maxes at 800.0% on an 8-thread CPU, htop never exceeds 100% on the CPU load bars).

To reproduce you have to run a process that puts CPU under a heavy load on all threads, like video encoding. Liquorix kernel (or a kernel with MuQSS/BFS) may be a significant pre-requisite as well, I'm not sure it can be reproduced with the stock Ubuntu kernel.

Kubuntu 16.10, x86_64, liquorix kernel:

uname -a
Linux lastique-pc 4.8.0-11.1-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.8-16 (2016-11-29) x86_64 x86_64 x86_64 GNU/Linux

CPU: Core i7 2600K (4-core, 8-thread).
Comment 1 Gregor Mi 2018-03-25 18:08:04 UTC
This is odd, indeed. Can you still reproduce this bug?
Comment 2 Lastique 2018-03-25 19:23:06 UTC
I have since moved away from Liquorix kernel, so I cannot verify. On the stock Kubuntu 17.10 kernel CPU load indicator never reaches 100%.
Comment 3 Gregor Mi 2018-03-25 19:37:37 UTC
I would say we wait for someone who can reproduce the issue. Or - since you reported the bug - close the issue.
Comment 4 Andrew Crouthamel 2018-09-28 03:18:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Andrew Crouthamel 2018-10-29 02:20:02 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!