[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20251013141206.0cf358a3@gandalf.local.home>
Date: Mon, 13 Oct 2025 14:12:06 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: "CruzZhao" <cruzzhao@...ux.alibaba.com>
Cc: "mingo" <mingo@...hat.com>, "peterz" <peterz@...radead.org>,
"juri.lelli" <juri.lelli@...hat.com>, "vincent.guittot"
<vincent.guittot@...aro.org>, "dietmar.eggemann"
<dietmar.eggemann@....com>, "bsegall" <bsegall@...gle.com>, "mgorman"
<mgorman@...e.de>, "vschneid" <vschneid@...hat.com>, "catalin.marinas"
<catalin.marinas@....com>, "will" <will@...nel.org>, "linux-kernel"
<linux-kernel@...r.kernel.org>, "linux-arm-kernel"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [BUG] Kernel panic in update_cfs_rq_h_load() on aarch64
On Mon, 13 Oct 2025 11:37:59 +0800
"CruzZhao" <cruzzhao@...ux.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.
> ---
Powered by blists - more mailing lists