[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20241108085419.GA6497@noisy.programming.kicks-ass.net>
Date: Fri, 8 Nov 2024 09:54:19 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Dave Chinner <david@...morbit.com>
Cc: Thorsten Leemhuis <regressions@...mhuis.info>,
John Garry <john.g.garry@...cle.com>, tj@...nel.org,
jiangshanlai@...il.com, mingo@...hat.com, juri.lelli@...hat.com,
jack@...e.cz, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: workqueue lockup debug
On Fri, Nov 08, 2024 at 09:57:38AM +1100, Dave Chinner wrote:
> On Thu, Nov 07, 2024 at 01:39:39PM +0100, Thorsten Leemhuis wrote:
> > On 24.10.24 17:49, John Garry wrote:
> > > Hi workqueue and scheduler maintainers,
> > >
> > > As reported in https://lore.kernel.org/linux-fsdevel/df9db1ce-17d9-49f1-
> > > ab6d-7ed9a4f1f9c0@...cle.com/T/
> > > #m506b9edb1340cdddd87c6d14d20222ca8d7e8796, I am experiencing a
> > > workqueue lockup for v6.12-rcX.
> >
> > John, what this resolved in between? This and the other thread[1] look
> > stalled, but I might be missing something. Asking, because I have this
> > on my list of tracked regressions and wonder if this is something that
> > better should be solved one way or another before 6.12.
> >
> > [1]
> > https://lore.kernel.org/lkml/63d6ceeb-a22f-4dee-bc9d-8687ce4c7355@oracle.com/
>
> I'm still seeing the scheduler bug in -rc6.
But that WARN you reported earlier isn't there anymore. So what exactly
are you seeing now?
Powered by blists - more mailing lists