From: Dave Chinner <david@fromorbit.com>
To: John Garry <john.g.garry@oracle.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
brauner@kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: v6.12-rc workqueue lockups
Date: Fri, 25 Oct 2024 08:13:20 +1100 [thread overview]
Message-ID: <Zxq4cEVjcHmluc9O@dread.disaster.area> (raw)
In-Reply-To: <df9db1ce-17d9-49f1-ab6d-7ed9a4f1f9c0@oracle.com>
On Thu, Oct 24, 2024 at 10:35:29AM +0100, John Garry wrote:
> On 23/10/2024 21:39, Jan Kara wrote:
> > On Wed 23-10-24 11:19:24, John Garry wrote:
> > > Hi All,
> > >
> > > I have been seeing lockups reliably occur on v6.12-rc1, 3, 4 and linus'
> > > master branch:
> > >
> > > Message from syslogd@jgarry-atomic-write-exp-e4-8-instance-20231214-1221 at
> > > Oct 22 09:07:15 ...
> > > kernel:watchdog: BUG: soft lockup - CPU#12 stuck for 26s! [khugepaged:154]
> >
> > BTW, can you please share logs which would contain full stacktraces that
> > this softlockup reports produce? The attached dmesg is just from fresh
> > boot... Thanks!
> >
>
> thanks for getting back to me.
>
> So I think that enabling /proc/sys/kernel/softlockup_all_cpu_backtrace is
> required there. Unfortunately my VM often just locks up without any sign of
> life.
Attach a "serial" console to the vm - add "console=ttyS0,115600" to
the kernel command line and add "-serial pty" to the qemu command
line. You can then attach something like minicom to the /dev/pts/X
device that qemu creates for the console output and capture
everything from initial boot right through to the softlockup traces
that are emitted...
-Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2024-10-24 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 10:19 v6.12-rc workqueue lockups John Garry
2024-10-23 20:13 ` Jan Kara
2024-10-24 3:18 ` Dave Chinner
2024-10-23 20:39 ` Jan Kara
2024-10-24 9:35 ` John Garry
2024-10-24 21:13 ` Dave Chinner [this message]
2024-10-24 22:23 ` John Garry
2024-10-28 5:35 ` Dave Chinner
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=Zxq4cEVjcHmluc9O@dread.disaster.area \
--to=david@fromorbit.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=john.g.garry@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox