On Mon, 2017-04-24 at 09:27 +0200, Bjørn Mork wrote: > Ben Hutchings <b...@decadent.org.uk> writes: > > > The change in version 0.128 to wait for the resume device to appear > > uncovered a number of systems for which the resume device is not > > properly configured. In fact, systems with swap partitions that > > are never available at boot could not be configured correctly, > > other than by adding 'noresume' to the kernel command line! > > > > While working on that, I found and fixed a couple of other > > longstanding bugs in resume device selection. > > > > This patch series: > > > > - Fixes the sorting of swap partitions > > - Makes the RESUME variable work like every other configuration > > variable, and documents it > > - Adds support for RESUME=none (disable resume) and RESUME=auto > > (explicitly request automatic selection) > > - Adds warning and informational messages where the resume device > > configuration is automatically fixed-up > > Hmm, I got this warning, which seems harmless but unexpected: > > Processing triggers for initramfs-tools (0.129) ... > update-initramfs: Generating /boot/initrd.img-4.9.0-2-amd64 > W: initramfs-tools configuration sets RESUME=UUID=30db89e8-91f2-44ee- > a8fa-61e5855ead41 > W: but no matching swap device is available. > I: The initramfs will attempt to resume from /dev/nvme0n1p4 > I: (UUID=30db89e8-91f2-44ee-a8fa-61e5855ead41) > I: Set the RESUME variable to override this. [...]
This is bug #861057 which should be fixed now. Ben. -- Ben Hutchings All extremists should be taken out and shot.
signature.asc
Description: This is a digitally signed message part
