On Tue, Oct 12, 2021 at 02:25:31AM +0200, Guilhem Moulin <guil...@debian.org> wrote: > > Also did you run luksFormat on that same machine (and didn't remove > > memory sticks afterwards)? > > I was actually able to reproduce this with buster's 2.1.0, but doing the > same thing after upgrading to bullseye or sid yields
> which sounds alright. Did you run reportbug(1) from the affected system > or from an older one? I reported this from another system, but both were recently upgraded to bullseye. I know because I use kvm to see if the machine will actually boot (Cthus the different memory setup) and the kvm in bullseye has a bug that makes this very hard (remote display makes it freeze randomly), and I had to work around this bug, so I know it was not buster. > Looking at the upstream git log, I found > 206b70c837f29c8b34cb0d80ae496870550ec50c > which fixes https://gitlab.com/cryptsetup/cryptsetup/-/issues/488 which looks > really familiar :-) It looks very similar. It is not the message I got with -v, which specifically had the error number (3) in it somewhere, but maybe thats because it ran out of memory in a different place. I tried to recreate the conditions again (which was basically runnign kvm without -m option), but I can't get the kernel to boot with the default memory, and the minimum amount I got it to boot with was 256MB, at which cryptsetup was able to open the volume. -- The choice of a Deliantra, the free code+content MORPG -----==- _GNU_ http://www.deliantra.net ----==-- _ generation ---==---(_)__ __ ____ __ Marc Lehmann --==---/ / _ \/ // /\ \/ / schm...@schmorp.de -=====/_/_//_/\_,_/ /_/\_\
