From: Chaoyi Chen <chaoyi.chen@rock-chips.com>
To: No SPAM here <nospam@gdead.co.uk>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [BUG?] Possible scheduler bug on Rock 5B RK3588 on 7.2.5
Date: Fri, 18 Sep 2026 09:21:48 +0800 [thread overview]
Message-ID: <11cdc24a-962a-4f44-b91c-445c2ac80c02@rock-chips.com> (raw)
In-Reply-To: <iENNazJ40aK7PPjVcvf8KUzlTm4HMyT85UPc2ez-MfyeJjE2HWX1ujGXIA3BGRwegyOJEZQ86kV7UElMjyBc6V5uCkGyK4NRCdw74ZfJwI8=@gdead.co.uk>
On 9/18/2026 3:15 AM, No SPAM here wrote:
> Hi
>
> On Thursday, 17 September 2026 at 03:37, Chaoyi Chen <chaoyi.chen@rock-chips.com> wrote:
>
>> Hello Trevor,
>>
>> On 9/17/2026 9:21 AM, No SPAM here wrote:
>>>> Would you mind trying to disable `CONFIG_SCHED_CLUSTER` and checking whether
>>>> the problem still reproduces?
>
> trevor@rock-5b:~$ uname -a
> Linux rock-5b 6.18.52-current-rockchip64 #1 SMP PREEMPT Mon Sep 14 11:36:19 UTC 2026 aarch64 GNU/Linux
> trevor@rock-5b:~$ grep CONFIG_SCHED_CLU /boot/config-6.18.52-current-rockchip64
> # CONFIG_SCHED_CLUSTER is not set
> trevor@rock-5b:~$ sar | tail -5
>
> 18:50:15 CPU %user %nice %system %iowait %steal %idle
> 19:00:15 all 99.89 0.00 0.11 0.00 0.00 0.00
> 19:10:15 all 99.89 0.00 0.11 0.00 0.00 0.00
> Average: all 99.89 0.00 0.11 0.00 0.00 0.00
>
> Been running stress --cpu 8 since 18:47 and so far it is using all 8 cores at 100%. It would normally have shown the 7/8ths problem after 20s or so, maybe 2 or 3 minutes at max. So I'd say this setting is definitely involved.
>
Thank you very much for testing. I'm not a scheduler expert, but I see
that CONFIG_SCHED_CLUSTER is enabled by default on arm64 [0].
Peter is the maintainer and author of this series.
@Peter, do you have any further insights? Thank you!
This thread background is here[1].
[0]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7bd291abe2da09f59dca81f35a4ec220e5e138a2
[1]: https://lore.kernel.org/all/f15f8166-c1e4-45dc-9ddd-4ec887e415eb@gdead.co.uk/
--
Best,
Chaoyi
next parent reply other threads:[~2026-09-18 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f15f8166-c1e4-45dc-9ddd-4ec887e415eb@gdead.co.uk>
[not found] ` <d6232ccc-9876-435f-bea8-43cd169dd185@rock-chips.com>
[not found] ` <BxAg81spRPHPsVOcNI5jR9tsii3Wi5a_k_BYW6owu3n6D3jn4N6dbkksomSb82KFdp8nT-mY4cyiZzDFHCqtuskOIYxZwBOzAvyYVRy18KQ=@gdead.co.uk>
[not found] ` <e045dc5b-5b03-4840-ade9-2c8f98c8c885@rock-chips.com>
[not found] ` <iENNazJ40aK7PPjVcvf8KUzlTm4HMyT85UPc2ez-MfyeJjE2HWX1ujGXIA3BGRwegyOJEZQ86kV7UElMjyBc6V5uCkGyK4NRCdw74ZfJwI8=@gdead.co.uk>
2026-09-18 1:21 ` Chaoyi Chen [this message]
2026-09-18 5:03 ` [BUG?] Possible scheduler bug on Rock 5B RK3588 on 7.2.5 No SPAM here
2026-09-18 16:11 ` No SPAM here
2026-09-19 10:57 ` Chaoyi Chen
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=11cdc24a-962a-4f44-b91c-445c2ac80c02@rock-chips.com \
--to=chaoyi.chen@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=nospam@gdead.co.uk \
--cc=peterz@infradead.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