All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: tj@kernel.org, jiangshanlai@gmail.com, mingo@redhat.com,
	peterz@infradead.org, juri.lelli@redhat.com
Cc: jack@suse.cz, david@fromorbit.com, akpm@linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: workqueue lockup debug
Date: Thu, 24 Oct 2024 16:49:40 +0100	[thread overview]
Message-ID: <70cb224f-a468-40a0-82c7-735c590bdb43@oracle.com> (raw)

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.

At the point it occurs, the system becomes unresponsive and I cannot 
bring it back to life.

Enabling /proc/sys/kernel/softlockup_all_cpu_backtrace does not give 
anything extra in the way of debug. All I get is something like this:

Message from syslogd@jgarry-atomic-write-exp-e4-8-instance-20231214-1221 
at Oct 24 15:34:02 ...
  kernel:watchdog: BUG: soft lockup - CPU#29 stuck for 22s! [mysqld:14352]

Message from syslogd@jgarry-atomic-write-exp-e4-8-instance-20231214-1221 
at Oct 24 15:34:02 ...
  kernel:BUG: workqueue lockup - pool cpus=4 node=0 flags=0x0 nice=0 
stuck for 30s!

Message from syslogd@jgarry-atomic-write-exp-e4-8-instance-20231214-1221 
at Oct 24 15:34:02 ...
  kernel:BUG: workqueue lockup - pool cpus=31 node=0 flags=0x0 nice=0 
stuck for 49s!
^C

Can you advise on a robust method to get some debug from this system?

Maybe this is a scheduler issue, as Dave mentioned in that same thread.

Thanks,
John

             reply	other threads:[~2024-10-24 15:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-24 15:49 John Garry [this message]
2024-10-24 18:56 ` workqueue lockup debug 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

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=70cb224f-a468-40a0-82c7-735c590bdb43@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=jack@suse.cz \
    --cc=jiangshanlai@gmail.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --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.