[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<AS8PR07MB8117E00A3016725F7D70FE5E859EA@AS8PR07MB8117.eurprd07.prod.outlook.com>
Date: Wed, 21 May 2025 08:28:55 +0000
From: "Ismo 1. Puustinen (Nokia)" <ismo.1.puustinen@...ia.com>
To: Steven Rostedt <rostedt@...dmis.org>, fengtian guo
<fengtian_guo@...mail.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>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Linux RT
Development <linux-rt-devel@...ts.linux.dev>, linux-rt-users
<linux-rt-users@...r.kernel.org>
Subject: RE: [PATCH RT] Possible spinlock deadlock in kernel/sched/rt.c under
high load
> I encountered a hard deadlock issue in the RT-patched kernel (v5.10) on an ARM64 arm64 32cores server, triggered by high-load stress testing with RT threads.
Could you re-send the patch? This looks suspiciously close to the RT crash that I'm seeing (https://bugzilla.kernel.org/show_bug.cgi?id=219919). I can try out the fix to see if it solves the task corruption problem.
Ismo
Powered by blists - more mailing lists