From: Manuel Ullmann <labre@posteo.de>
To: Jordan Leppert <jordanleppert@protonmail.com>
Cc: labre@posteo.de, stable@vger.kernel.org,
regressions@lists.linux.dev, davem@davemloft.net
Subject: Re: Crash on resume after suspend (5.17.5 and 5.15.36)
Date: Wed, 04 May 2022 22:21:20 +0000 [thread overview]
Message-ID: <874k252b33.fsf@posteo.de> (raw)
In-Reply-To: <vcehgVc5mzweaw_ru0o1up63In2GGa9jtEWuaH8op7p2753Wfr2ezPhxFJdMPFxmpiPmrUB4XnH2nakuhC_BJby3wFa87cbpdLV-lDDb6Ko=@protonmail.com> (Jordan Leppert's message of "Wed, 04 May 2022 21:13:45 +0000")
> I also probably can't test hibernation, never managed to get it
> working before. I'll give it a shot tomorrow though if I have time but
> I don't even have swap set up ATM.
That’s a pity, but okay, of course. Thanks for reporting this bug.
Since you are using Arch and the Wiki is quite detailed, you could try
setting up a swap on an unused USB stick floating around. This should be
the easiest setup. Make sure to add resume to the mkinitcpio hooks after
udev, but before fsck and add the resume parameter to your bootloader as
described in the Wiki. This should get you going.
Don’t make this a permanent setup, if you use encryption or like
performance. The permanent solution would be creating a swap partition
or, if that is not feasible, a swap file while considering the Wiki
notes for e.g. btrfs.
Best regards,
Manuel
next prev parent reply other threads:[~2022-05-04 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <refZ3y2HAXztrRkMMmFbBaF7Dz1CctWgjchSdBtcSNlpk-TL0fqLepVVHfw9qXtIQF9uFzBvFdjQiiX9Jv2zW9oaWej952s1IYwu61d1REo=@protonmail.com>
2022-05-04 15:07 ` Crash on resume after suspend (5.17.5 and 5.15.36) Jordan Leppert
2022-05-04 16:38 ` Jordan Leppert
2022-05-04 17:50 ` Holger Hoffstätte
2022-05-04 18:31 ` Holger Hoffstätte
2022-05-04 19:25 ` Manuel Ullmann
2022-05-04 20:58 ` Holger Hoffstätte
2022-05-04 22:10 ` Manuel Ullmann
[not found] ` <vcehgVc5mzweaw_ru0o1up63In2GGa9jtEWuaH8op7p2753Wfr2ezPhxFJdMPFxmpiPmrUB4XnH2nakuhC_BJby3wFa87cbpdLV-lDDb6Ko=@protonmail.com>
2022-05-04 22:21 ` Manuel Ullmann [this message]
2022-05-05 10:41 ` Jordan Leppert
2022-05-05 7:43 ` Thorsten Leemhuis
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=874k252b33.fsf@posteo.de \
--to=labre@posteo.de \
--cc=davem@davemloft.net \
--cc=jordanleppert@protonmail.com \
--cc=regressions@lists.linux.dev \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).