From: Tejun Heo <tj@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-kernel@vger.kernel.org, Naohiro.Aota@wdc.com,
kernel-team@meta.com, Bjorn Andersson <andersson@kernel.org>
Subject: Re: Workqueue regression
Date: Thu, 1 Feb 2024 15:52:19 -1000 [thread overview]
Message-ID: <ZbxK01xuA_FFWaE6@slm.duckdns.org> (raw)
In-Reply-To: <b3d08cd8-d77f-45dd-a2c3-4a4db5a98dfa@kernel.org>
Hello,
On Thu, Feb 01, 2024 at 09:57:59PM +0100, Konrad Dybcio wrote:
> So, commit "Implement system-wide nr_active enforcement for unbound workqueues"
> broke *something* and now performing a suspend-wakeup cycle on a Qualcomm
> SC8280XP-based (arm64) platform hangs when performing the resume tasks,
> presumably somewhere near PCIe reinitialization (but that may be a red herring).
>
> Reverting the commit (and the ones on top of it due to conflicts) fixes
> the issue on next-20240130 and later (plus some out-of-tree patches that
> are largely unrelated).
>
> Not sure where to start looking.
Hmm... sorry about that. Can you please boot with `console_no_suspend` and
retry? Once the system gets stuck, you can wait for several minutes till the
workqueue watchdog triggers and dumps the state or, if you can, trigger
`sysrq-t` which has workqueue state dump at the end.
If the system doesn't become live enough after suspend/resume cycle to get
more info, the following might help:
$ echo test_resume > /sys/power/disk
$ echo disk > /sys/power/state
That should walk most of the hibernation/wakeup path which is pretty simliar
to suspend/resume path without touching system power state.
Thanks.
--
tejun
next prev parent reply other threads:[~2024-02-02 1:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 20:57 Workqueue regression Konrad Dybcio
2024-02-02 1:52 ` Tejun Heo [this message]
2024-02-02 12:31 ` Konrad Dybcio
2024-02-02 18:40 ` Tejun Heo
2024-02-04 21:19 ` Tejun Heo
2024-02-05 11:43 ` Konrad Dybcio
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=ZbxK01xuA_FFWaE6@slm.duckdns.org \
--to=tj@kernel.org \
--cc=Naohiro.Aota@wdc.com \
--cc=andersson@kernel.org \
--cc=kernel-team@meta.com \
--cc=konradybcio@kernel.org \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox