From: Sasha Levin <sashal@kernel.org>
To: David Lomas <david.s.lomas@gmail.com>, gregkh@linuxfoundation.org
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, rafael.j.wysocki@intel.com,
matthew.leach@collabora.com, superm1@kernel.org,
linux-pm@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH 6.18 0167/1250] PM: hibernate: call preallocate_image() after freeze prepare
Date: Sun, 20 Sep 2026 20:13:01 -0400 [thread overview]
Message-ID: <20260920200637.10dc42c1bb6a@kernel.org> (raw)
In-Reply-To: <CALjEBWQo0-Sdimo+aRNKUQvgDGw=jBFCcfwCXaqVdtoPrHLAQA@mail.gmail.com>
On Sat, Sep 19, 2026 at 02:47:25PM +0100, David Lomas wrote:
> Upstream commit 783c8109844503bd1c35dab41b6d5fd074a9f131 deadlocks
> hibernation entry on my machine (7.2.4, Dell XPS 13 9360, 8 GB, zswap
> on) whenever the system has been in use for some hours: the hibernate
> call never returns and the laptop sits warm with no image written,
Thank you for the report!
> Captured with SysRq (w) after ~8 minutes hung. The hibernating task is
> in the direct-reclaim throttle waiting for kswapd, which was frozen 27
> ms earlier by freeze_kernel_threads(), which this commit moved ahead
> of hibernate_preallocate_memory():
I've dropped the patch from the 6.18 queue. 783c8109 has not appeared in
a released 6.18.y yet (v6.18.52 is the latest), so dropping it from the
queue is enough to keep 6.18.y clear of this.
--
Thanks,
Sasha
next prev parent reply other threads:[~2026-09-21 0:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 13:47 [PATCH 6.18 0167/1250] PM: hibernate: call preallocate_image() after freeze prepare David Lomas
2026-09-20 17:50 ` Sasha Levin
2026-09-21 8:08 ` Thorsten Leemhuis
2026-09-21 10:22 ` David Lomas
2026-09-21 0:13 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-19 20:52 David Lomas
2026-09-21 21:18 ` Hic Haec Hoc
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=20260920200637.10dc42c1bb6a@kernel.org \
--to=sashal@kernel.org \
--cc=david.s.lomas@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthew.leach@collabora.com \
--cc=rafael.j.wysocki@intel.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=superm1@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