From: Dave Chinner <david@fromorbit.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thorsten Leemhuis <regressions@leemhuis.info>,
John Garry <john.g.garry@oracle.com>,
tj@kernel.org, jiangshanlai@gmail.com, mingo@redhat.com,
juri.lelli@redhat.com, jack@suse.cz, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: workqueue lockup debug
Date: Tue, 12 Nov 2024 08:01:44 +1100 [thread overview]
Message-ID: <ZzJwuCvLv5ZEIT0e@dread.disaster.area> (raw)
In-Reply-To: <20241108085419.GA6497@noisy.programming.kicks-ass.net>
On Fri, Nov 08, 2024 at 09:54:19AM +0100, Peter Zijlstra wrote:
> 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@oracle.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?
I just went back and checked the logs. It does appear I was running
an -rc5 base kernel, but that just makes me really confused because
I was running mount path debug trace_printk patches at the time and
that kernel was clearly built on a 6.12-rc6 base.
Yet, apparently, despite getting the tracing output I expected to
see, the kernel still reported as 6.12.0-rc5-dgc+. I suspect some
kind of weird delta rebuild issue (possibly some of my machines have
dropped time sync), but that's my problem to sort out.
IOWs, ignore this, I'll do a full rebuild on -rc7 and test again.
If you don't hear from me again, I haven't hit new problems.
-Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2024-11-11 21:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 15:49 workqueue lockup debug John Garry
2024-10-24 18:56 ` Tejun Heo
2024-10-25 9:28 ` John Garry
2024-10-29 4:11 ` Dave Chinner
2024-10-29 8:07 ` John Garry
2024-10-29 15:51 ` John Garry
2024-11-07 12:39 ` Thorsten Leemhuis
2024-11-07 22:57 ` Dave Chinner
2024-11-08 8:54 ` Peter Zijlstra
2024-11-11 13:22 ` John Garry
2024-11-11 21:01 ` Dave Chinner [this message]
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=ZzJwuCvLv5ZEIT0e@dread.disaster.area \
--to=david@fromorbit.com \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=jiangshanlai@gmail.com \
--cc=john.g.garry@oracle.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=regressions@leemhuis.info \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.