Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-20 Thread Adrien CLERC
Le 20/06/2018 à 00:21, Guilhem Moulin a écrit : > On Tue, 19 Jun 2018 at 23:52:45 +0200, Guilhem Moulin wrote: >> Sorry, I meant between your backup initrd.img (presumably also compiled >> with MODULES=dep) and the new, broken one. > Alternatively, if you don't have this initrd around anymore, are

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 23:52:45 +0200, Guilhem Moulin wrote: > Sorry, I meant between your backup initrd.img (presumably also compiled > with MODULES=dep) and the new, broken one. Alternatively, if you don't have this initrd around anymore, are you able to boot if you add the ‘xts’ module to the

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 23:00:29 +0200, Adrien CLERC wrote: > Le 19/06/2018 à 22:40, Guilhem Moulin a écrit : >> Could you run the following on both the broken and backup initrd and >> send the diff? >> >> lsinitramfs /path/to/initrd.img | grep ^lib/modules/ | sort > > See

Bug#901884: [pkg-cryptsetup-devel] Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Adrien CLERC
Le 19/06/2018 à 23:06, Guilhem Moulin a écrit : > Just noticed what looks like a regression, I wonder if that's the same > problem. Does your system have AES-NI or similar, or are you using the > generic modules? What's the output of > > grep -A2 '^name *: *xts(aes)' /proc/crypto > # grep

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Adrien CLERC
Le 19/06/2018 à 22:40, Guilhem Moulin a écrit : > Could you run the following on both the broken and backup initrd and > send the diff? > > lsinitramfs /path/to/initrd.img | grep ^lib/modules/ | sort See initramfs_dep_vs_most.diff.gz. The dep output is not working, and the most output is

Bug#901884: [pkg-cryptsetup-devel] Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 22:40:23 +0200, Guilhem Moulin wrote: > FWIW 2.0.3-2 was tested with MODULES=dep, too. I wonder how your system > differs from our test environments. Just noticed what looks like a regression, I wonder if that's the same problem. Does your system have AES-NI or similar,

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Guilhem Moulin
On Tue, 19 Jun 2018 at 21:39:06 +0200, Adrien CLERC wrote: > Fortunately, the previous one has still a valid initramfs, so I can boot > my system (many thanks for that backup system). > […] > Check that kernel supports aes-xts-plain64 cipher (check syslog for > more info). Could you run the

Bug#901884: [cryptsetup-initramfs] Unbootable system with MODULES=dep

2018-06-19 Thread Adrien CLERC
Package: cryptsetup-initramfs Version: 2:2.0.3-2 Severity: critical --- Please enter the report below this line. --- Hi, I have a full disk-encryption set up with LUKS. After upgrading from 2.0.3-1 to 2.0.3-2 my last (and current) kernel is unbootable. Fortunately, the previous one has still a