Messages in this thread | | | Date | Tue, 28 Jun 2022 01:13:30 -0400 | From | Alexandre Messier <> | Subject | [REGRESSION] Unable to unlock encrypted disk starting with kernel 5.19-rc1+ |
| |
Hello,
I tested 5.19-rc4 on my system that is currently running 5.18.0, and came across an issue when unlocking the encrypted rootfs disk at startup. The error message is:
device-mapper: reload ioctl on nvme0n1p3_crypt (254:0) failed: No such file or directory
The kernel log shows:
device-mapper: table: 254:0: crypt: Error allocating crypto tfm (-ENOENT) device-mapper: ioctl: error adding target to table
I tested the previous 5.19-rcX, and the issue started happening with 5.19-rc1. A bisection between 5.18.0 and 5.19-rc1 identifies the following commit:
8ad7e8f69695 ("x86/fpu/xsave: Support XSAVEC in the kernel")
I reverted that commit on top of 5.19-rc4, and unlocking the encrypted disk works again.
Some more information about the system: - CPU is AMD Ryzen 5700G - Userspace is Debian Sid - The encrypted disk setup is a default encrypted rootfs, as configured by the standard Debian installer
Please let me know if more information is needed, or if some tests are needed to be run.
Thanks, Alex
#regzbot introduced 8ad7e8f69695
| |