From: Steven Rostedt <rostedt@goodmis.org>
To: "CruzZhao" <cruzzhao@linux.alibaba.com>
Cc: "mingo" <mingo@redhat.com>, "peterz" <peterz@infradead.org>,
"juri.lelli" <juri.lelli@redhat.com>,
"vincent.guittot" <vincent.guittot@linaro.org>,
"dietmar.eggemann" <dietmar.eggemann@arm.com>,
"bsegall" <bsegall@google.com>, "mgorman" <mgorman@suse.de>,
"vschneid" <vschneid@redhat.com>,
"catalin.marinas" <catalin.marinas@arm.com>,
"will" <will@kernel.org>,
"linux-kernel" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel" <linux-arm-kernel@lists.infradead.org>
Subject: Re: [BUG] Kernel panic in update_cfs_rq_h_load() on aarch64
Date: Mon, 13 Oct 2025 14:12:06 -0400 [thread overview]
Message-ID: <20251013141206.0cf358a3@gandalf.local.home> (raw)
In-Reply-To: <1dbc8668-4607-45ae-a286-77def1037917.cruzzhao@linux.alibaba.com>
On Mon, 13 Oct 2025 11:37:59 +0800
"CruzZhao" <cruzzhao@linux.alibaba.com> wrote:
> Hi, all. We are encountering a kernel panic in our production environment running Linux kernel version 5.10.134, on aarch64 architecture (aarch64 architecture only).
> ### Summary:
> - **Kernel Version**: [5.10.134]
That's an ancient kernel. Why are you sending this to upstream?
Please test 6.17.
-- Steve
> - **Architecture**: [aarch64]
> - **Problem Type**: panic
> - **Reproducibility**: About 40 times per week
> This issue leads to system-wide unresponsiveness and requires a hard reboot. We have collected the panic logs and backtraces, which I will include below for your reference. We tried to analyze the vmcore but have not found out the root cause.
> ---
parent reply other threads:[~2025-10-13 18:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1dbc8668-4607-45ae-a286-77def1037917.cruzzhao@linux.alibaba.com>]
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=20251013141206.0cf358a3@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bsegall@google.com \
--cc=catalin.marinas@arm.com \
--cc=cruzzhao@linux.alibaba.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@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