Devuan bug report logs - #251
Error message and delay on boot, after encrypting the swap partition.

Package: cryptsetup; Reported by: =?UTF-8?B?zpPOuc+Oz4HOs86/z4IgzprPic+Dz4TPjM+Azr/Phc67zr/Pgg==?= <giorgosk67@gmail.com>;
Date: Sun, 21 Oct 2018 12:33:01 UTC;
Maintainer for cryptsetup is (unknown).

View this report as an mbox folder.

Report forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#251; Package cryptsetup. Full text available.

---

Acknowledgement sent to =?UTF-8?B?zpPOuc+Oz4HOs86/z4IgzprPic+Dz4TPjM+Azr/Phc67zr/Pgg==?= <giorgosk67@gmail.com>:
New bug report received and forwarded. Copy sent to owner@bugs.devuan.org. Full text available.

---

Message received at submit@bugs.devuan.org:

From: =?UTF-8?B?zpPOuc+Oz4HOs86/z4IgzprPic+Dz4TPjM+Azr/Phc67zr/Pgg==?= <giorgosk67@gmail.com>
Date: Sun, 21 Oct 2018 15:16:11 +0300
Subject: Error message and delay on boot, after encrypting the swap partition.
To: submit@bugs.devuan.org

Package: cryptsetup
Version: 2:1.7.3-4

After following the FAQ instructions and successfully encrypting my
swap partition, I'm getting the following error message on boot, with
the respective delay: "Gave up waiting for suspend/resume device".

Option noearly has no effect on it (as it suppose to do).
Option noauto, although working, has no effect on the described problem too.

I have a single normal SATA disk with 6 partitions. (No RAID or
complex configuration).
On ASCII x64 KDE.

---

Information forwarded to devuan-bugs@lists.dyne.org, owner@bugs.devuan.org:
bug#251; Package cryptsetup. Full text available.

---

Acknowledgement sent to =?UTF-8?B?zpPOuc+Oz4HOs86/z4IgzprPic+Dz4TPjM+Azr/Phc67zr/Pgg==?= <giorgosk67@gmail.com>:
Extra info received and forwarded to list. Copy sent to owner@bugs.devuan.org. Full text available.

---

Message received at 251@bugs.devuan.org:

From: =?UTF-8?B?zpPOuc+Oz4HOs86/z4IgzprPic+Dz4TPjM+Azr/Phc67zr/Pgg==?= <giorgosk67@gmail.com>
Date: Tue, 23 Oct 2018 03:35:13 +0300
Subject: Workaround.
To: 251@bugs.devuan.org

Editing the resume file and setting RESUME=none.
Of course (as root): update-initramfs -u
and the problem solved.

PS. Although the workaround is effective, the bug is still valid.

---