Your message dated Sun, 23 May 2021 02:53:32 -0700 (PDT)
with message-id <[email protected]>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #888465,
regarding CPU usage reporting issues
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
888465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888465
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-image-4.9.0-5-amd64
Version: 4.9.65-3+deb9u2
Severity: normal
Hi,
I'm having an issue with CPU usage reporting, tested on kernels 4.9.0-3
and 4.9.0-5. The machines are running on Amazon EC2, which could be
related. With the "sar" utility, after some time, the system's "steal"
value periodically is 100%, and the normal CPU user/system values,
including idle, are always 0. When running a cpu-intensive app and
using the "top" utility, the user and system values are always 0, the
"idle" field stays at 100%, and only the "wait" field increases.
The attached file shows the "sar" output around the time the issue
started. This has happened on 2 separate machines (started at different
times on each), and a reboot appears to (temporarily) fix the issue.
I'm wondering if anyone else has this issue, and if it could be
something to do with the hypervisor.
--
Ryan Thoryk
[email protected]
[email protected]
11:05:01 AM all 0.01 0.00 0.02 0.00 0.00 99.97
11:15:01 AM all 0.01 0.00 0.02 0.00 0.00 99.97
11:25:01 AM all 0.01 0.00 0.02 0.00 0.00 99.97
11:35:01 AM all 0.01 0.00 0.02 0.00 0.00 99.97
11:45:01 AM all 0.01 0.00 0.02 0.00 0.00 99.97
11:55:01 AM all 0.01 0.00 0.02 0.00 0.00 99.97
12:05:01 PM all 0.01 0.00 0.01 0.00 0.00 99.97
12:15:01 PM all 0.01 0.00 0.01 0.00 0.00 99.97
12:25:01 PM all 0.01 0.00 0.02 0.00 0.00 99.97
12:25:01 PM CPU %user %nice %system %iowait %steal %idle
12:35:01 PM all 0.01 0.00 0.02 0.00 0.00 99.97
12:45:01 PM all 0.01 0.00 0.02 0.00 0.00 99.97
12:55:01 PM all 0.02 0.00 0.02 0.00 0.00 99.96
01:05:01 PM all 0.01 0.00 0.02 0.00 0.00 99.97
01:15:01 PM all 0.00 0.00 0.00 0.00 100.00 0.00
01:25:01 PM all 0.00 0.00 0.00 0.00 0.00 0.00
01:35:01 PM all 0.00 0.00 0.00 0.00 0.00 0.00
01:45:01 PM all 0.00 0.00 0.00 0.00 100.00 0.00
01:55:01 PM all 0.00 0.00 0.00 0.00 0.00 0.00
02:05:01 PM all 0.00 0.00 0.00 0.00 0.00 0.00
02:15:01 PM all 0.00 0.00 0.00 0.00 100.00 0.00
02:25:01 PM all 0.00 0.00 0.00 0.00 0.00 0.00
02:35:01 PM all 0.00 0.00 0.00 0.00 0.00 0.00
02:45:01 PM all 0.00 0.00 0.00 0.00 100.00 0.00
02:55:01 PM all 0.00 0.00 0.00 0.00 0.00 0.00
--- End Message ---
--- Begin Message ---
Hi
This bug was filed for a very old kernel or the bug is old itself
without resolution.
If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from backports
please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.
Regards,
Salvatore
--- End Message ---
