Dear Timo Aaltonen, Thank you for your reaction on the kernel bug report. I want to provide you and all concerned with the information that is needed to solve the problem. Unfortunately, my computer skills are just above the user level. I do not want to ruin the system. Or spoil the results. So please talk me through.
Exactly, how to perform this test with 'nopti' kernel boot option ? Please make clear to me what to do. What is the result of this test you do need ? So, I will be able to post or send the needed information. With kind regards, Jo Bakker Citeren Timo Aaltonen <tjaal...@ubuntu.com>: > test with 'nopti' kernel boot option > > ** Changed in: linux-hwe (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1839381 > > Title: > Regression after Kernel updates: Failed Boots with LUKS on LVM > > Status in linux-hwe package in Ubuntu: > Incomplete > > Bug description: > Regression after the Kernel Updates after april 26th, all result in > Failed Boot with LUKS on LVM. > Occurs on several IBM PC symtems with UBUNTU 16.04 and Xubuntu 18.04. > Fresh installation with the newest version and update does not give a > better result. > > All Pentium ibm pc´s with Ubuntu 16.04 and one with Xubuntu 18.04 have > been installed with the standard full HDD encryption, LUKS on LVM. > Decryption at startup worked fine for years until april the 26th of > 2019. Since these (kernel) updates the regression problem occurs and > stays. > > After Powering on the system, the boot process will start. LUKS asks for > the key. > After entering the key the decryption will start, but comes to an abrupt > end before the startup (boot and decryption) is finished. Nothing is > possible in that situation. The screen is frozen. The HDD is inactive. > Switching off the power is the only way out. > > After this failed boot, restarting the system, the grub menu shows for > some seconds. After that LUKS asks for the key. Entering the key > results in a completed startup and normal usable system. > > Is this enough information to understand the problem ? > Or let me know what other information you need. > > Is there a way out of this problem ? Or > Is there a simple way to circumvent this problem ? > > Kind regards > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: linux-image-4.15.0-55-generic 4.15.0-55.60~16.04.2 > ProcVersionSignature: Ubuntu 4.15.0-55.60~16.04.2-generic 4.15.18 > Uname: Linux 4.15.0-55-generic i686 > ApportVersion: 2.20.1-0ubuntu2.19 > Architecture: i386 > CurrentDesktop: Unity > Date: Wed Aug 7 21:43:50 2019 > EcryptfsInUse: Yes > InstallationDate: Installed on 2018-10-03 (308 days ago) > InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 > (20180731) > SourcePackage: linux-hwe > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go > to:https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839381/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839381 Title: Regression after Kernel updates: Failed Boots with LUKS on LVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1839381/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs