From: Frederic Weisbecker <frederic@kernel.org>
To: Ahmed Shaltout <ahmedshaltout.payment@gmail.com>
Cc: tglx@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] /proc/stat idle time exceeds wall clock since v7.2
Date: Tue, 22 Sep 2026 14:53:10 +0200 [thread overview]
Message-ID: <arJ6NjfdHUPjN2Kc@localhost.localdomain> (raw)
In-Reply-To: <E76BE609-83E4-4FB6-88B8-191F7816EFD6@gmail.com>
Hi Ahmed,
Le Sun, Sep 20, 2026 at 03:14:22AM +0400, Ahmed Shaltout a écrit :
> Hello,
>
> Since moving from 7.1.8 to 7.2.5 (openSUSE MicroOS kernel-default), the idle
> time reported in /proc/stat exceeds the wall-clock time the CPUs have been up
> for. Idle alone accrues ~103% of the ceiling, and user+nice+system+idle+iowait
> +irq+softirq+steal sums to ~108% of it.
>
> This breaks the common `100 - rate(idle)` derivation of CPU utilisation, which
> goes negative on an idle-but-working machine. node_exporter, and anything built
> on it, is affected.
>
> #regzbot introduced: v7.1..v7.2
>
> Reproducer
> ==========
>
> No tooling needed; /proc/uptime shows it directly, since its second field is
> idle time and cannot legitimately exceed uptime x nr_cpus:
>
> read -r up idle < /proc/uptime && awk -v u="$up" -v i="$idle" -v c="$(nproc)" \
> 'BEGIN{printf "idle %.2f%% of ceiling\n", 100*i/(u*c)}'
>
> 7.2.5: idle 103.10% of ceiling
> 7.1.8: idle 89.13% of ceiling
I can't manage to reproduce that, neither on latest mainline nor on 7.2.7
Can you share your whole .config file?
Thanks.
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2026-09-22 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 23:14 Ahmed Shaltout
2026-09-22 12:53 ` Frederic Weisbecker [this message]
2026-09-22 15:53 ` Ahmed Shaltout
2026-09-29 13:50 ` Frederic Weisbecker
2026-09-30 4:58 ` Ahmed Shaltout
2026-09-30 12:35 ` Frederic Weisbecker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=arJ6NjfdHUPjN2Kc@localhost.localdomain \
--to=frederic@kernel.org \
--cc=ahmedshaltout.payment@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®