[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250106122734.54bf57c6@gandalf.local.home>
Date: Mon, 6 Jan 2025 12:27:34 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: cheung wall <zzqq0103.hey@...il.com>
Cc: Ingo Molnar <mingo@...hat.com>, Peter Zijlstra <peterz@...radead.org>,
Juri Lelli <juri.lelli@...hat.com>, Vincent Guittot
<vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, Valentin
Schneider <vschneid@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: "INFO: rcu_tasks_trace detected stalls on tasks in
kernel/sched/core.c" in Linux kernel version 6.13.0-rc2
On Fri, 3 Jan 2025 16:11:18 +0800
cheung wall <zzqq0103.hey@...il.com> wrote:
> Root Cause:
>
> The system crash was triggered by a malfunction in the Linux kernel’s
> scheduler, specifically within the context_switch, __schedule,
> __schedule_loop, and schedule functions located in
> kernel/sched/core.c. These scheduler functions failed to properly
> manage task states, causing critical tasks like syz-executor.7 and
> systemd-udevd to become stuck in a running state while attempting to
> execute sleep operations. Concurrent filesystem issues, including
> unexpected loop device capacity changes and unrecognized mount
> parameters, likely exacerbated the problem by imposing additional
> stress on the scheduler. This combination led to prolonged
> Read-Copy-Update (RCU) stalls, preventing the system from efficiently
> handling task scheduling and ultimately resulting in the crash.
That looks like output from ChatGPT :-/
-- Steve
Powered by blists - more mailing lists