After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732305 - Incorrect CPU load and CPU count when a core is offline
Incorrect CPU load and CPU count when a core is offline
Status: RESOLVED DUPLICATE of bug 352807
Product: system-monitor
Classification: Core
Component: resources
3.8.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-26 23:36 UTC by seb.meinhardt
Modified: 2014-06-27 01:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshots: Before deactivating a CPU, after deactivatiing a CPU, after restarting system monitor. Output of the "top" command for comparison. (208.13 KB, image/png)
2014-06-26 23:36 UTC, seb.meinhardt
Details

Description seb.meinhardt 2014-06-26 23:36:59 UTC
Created attachment 279350 [details]
Screenshots: Before deactivating a CPU, after deactivatiing a CPU, after restarting system monitor. Output of the "top" command for comparison.

In the resources tab, if a CPU in a multi-CPU system is taken offline (by setting the value in the file /sys/devices/system/cpu/cpu?/online to 0), the system monitor will report a zero load for all CPUs following the offline CPU. For example, if you deactivate CPU5 in a system with 8 CPUs, the CPUs 5-7 will show 0% load. This is incorrect, as can be seen with other CPU monitors (for example "top"). Furthermore, if you restart the system monitor, it will only show CPUs up to the first offline-CPU. In the example above, it would only show CPUs 0-4.

Steps to reproduce:
-Have a multi-CPU system :-)
-Generate load for all CPUs, for example using the "stress" tool
-Open system monitor
-Deactivate a CPU: "echo 0 | sudo tee /sys/devices/system/cpu/cpuX/online", replacing "X" with an appropriate number

Expected result:
System monitor still shows load for all CPUs != X

Actual result:
System monitor only reports load for CPUs < X

See attached screenshots.
Comment 1 Robert Roth 2014-06-27 01:22:59 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 352807 ***