mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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, 29 Sep 2026 15:50:31 +0200	[thread overview]
Message-ID: <arvCJzz35oBW3AjY@localhost.localdomain> (raw)
In-Reply-To: <CAORRHKj1EUum3O6ToGek0A-tuUf7HsCUwFHiXUc+53ZLKOrSFw@mail.gmail.com>

Le Tue, Sep 22, 2026 at 07:53:23PM +0400, Ahmed Shaltout a écrit :
> Hi Frederic,
> 
> Le Mon, Sep 21, 2026, Frederic Weisbecker a écrit :
> > I can't manage to reproduce that, neither on latest mainline nor on 7.2.7
> >
> > Can you share your whole .config file?
> 
> Attached: config-7.2.5-1-default, taken from /boot/config-$(uname -r) on an
> affected node. It is the stock openSUSE Tumbleweed/MicroOS package
> kernel-default-7.2.5-1.1.x86_64, unmodified, no custom build. It differs
> from
> config/x86_64/default in openSUSE:Factory/kernel-source at the 7.2.5 source
> revision only in toolchain-detection and build-metadata lines (CC/AS/LD
> version, LOCALVERSION, MODULE_SIG_KEY, CC_HAS_*), no functional option:
> https://api.opensuse.org/public/source/openSUSE:Factory/kernel-source/config.tar.bz2?rev=4dabae0b715184e35b05b9a168bde6b7

I fear I still can't reproduce with the config in attachment.

> 
> The unaffected control box runs kernel-default-7.1.8-1.1.x86_64 from the
> same
> distribution, also stock, same VM type, same command line. Between the two
> configs the only change among the scheduler, tick, accounting, preemption
> and
> RCU options is CONFIG_SCHED_CACHE=y appearing in 7.2.5.
> 
> Environment, in case it is what your test box does not share:
> 
>   - Every node is a KVM guest (Hetzner Cloud, QEMU, "AMD EPYC-Rome
> Processor",
>     8 vCPUs, one with 4), clocksource kvm-clock.
>   - No steal-time accounting at all: there is no kvm-stealtime line in the
>     boot log and the steal column has read exactly 0 on every node for the
>     75 hours since boot, so the hypervisor does not seem to expose the MSR.
>   - CONFIG_VIRT_CPU_ACCOUNTING_GEN=y, CONFIG_CONTEXT_TRACKING_IDLE=y and
>     CONFIG_NO_HZ_FULL=y are built in (SUSE default) with nohz_full= empty,
>     so the CPUs run idle dynticks, not full.
>   - CONFIG_HZ=1000, CONFIG_PREEMPT_DYNAMIC=y, psi=1 on the command line:
>     BOOT_IMAGE=/boot/vmlinuz-7.2.5-1-default root=UUID=... rd.timeout=60
>     rd.retry=45 quiet systemd.show_status=yes console=ttyS0,115200
>     console=tty0 ignition.platform.id=openstack security=selinux selinux=1
>     psi=1

I ran on KVM too, overcommiting the vcpus like you did (16 vCPUs on 8 CPUs)
and still nothing wrong.

I'm wondering if this is specific to opensuse somehow. Can you try to build
the latest upstream kernel?

Thanks.

-- 
Frederic Weisbecker
SUSE Labs

  reply	other threads:[~2026-09-29 13:50 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
2026-09-22 15:53   ` Ahmed Shaltout
2026-09-29 13:50     ` Frederic Weisbecker [this message]
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=arvCJzz35oBW3AjY@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®