Control: severity -1 important Cyril Brulebois <kibi@debian.org> (2023-01-08): > I'm seeing at least two problems with cryptsetup while testing daily > builds: > - with 6.1.0-1 (currently getting into the archive), my very usual 1G > RAM / 5G storage setup can no longer get an automated encrypted LVM > setup created: cryptsetup triggers the OOMK while creating the > encrypted storage; that doesn't happen with 6.0.0-6. Not sure > cryptsetup itself is the culprit, it might just be more components or > heavier components on the kernel side, pushing memory to the limit. > - with either kernel (and 1G RAM for 6.0.0-6, 2G RAM for 6.1.0-1 due > to the first point), I cannot boot into the installed system: I'm not > getting the LVM passphrase prompt, and the root device is therefore > missing. > > I haven't investigated either issue, and I'm not sure when I'll be able > to. Help welcome. > > The first point could be waved aside with an errata entry; the second > point is going to be a blocker for the next release. Trying to investigate the second one, I cannot replicate my earlier results, with either a clean unstable daily build using 6.1.0-1 or with D-I Bookworm Alpha 1; and besides cryptsetup uploads in early December, I must admit a quick look around didn't suggest anything obvious that could explain what I were getting… Bad luck, maybe; lowering severity accordingly for the time being. Cheers, -- Cyril Brulebois (kibi@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
Attachment:
signature.asc
Description: PGP signature