Regression after Kernel updates: Failed Boots with LUKS on LVM

[Jo Bakker]

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)

[Timo Aaltonen (tjaalton)]

test with 'nopti' kernel boot option

[Jo Bakker (jojoma)]

How to perform this test with 'nopti' kernel boot option ?
Do not want to ruin the system. So please make clear what to do.
What is the result of this test you do need ? So, I will be able to send the needed information.

[Jo Bakker (jojoma)]

  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 <email address hidden>:

> 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

[Po-Hsu Lin (cypressyew)]

Hello Jo,

To achieve this, append string:
nopti

To GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub

So let's say if your GRUB_CMDLINE_LINUX_DEFAULT looks like this:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

Make it:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nopti"

When it's done, run "sudo update-grub" and restart you system.

Thanks

[Jo Bakker (jojoma)]

Thank you Po-Hsu Lin for the additional information.

RESULTS of ´nopti´ TEST

ACTION:
1) GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nopti"
2) grub has been updated

RESTART
Boot does not stop (after seven dots have turned from white to red)
Startup is completed .

Test is performed on both Ubuntu and Xubuntu distributions.
All are x86 systems.

Preliminary outcome.
Page Table Isolation instructions make the system crash during boot

How to proceed from here ?

[Jo Bakker (jojoma)]

NEW TEST with GRUB CMDLINE

ACTION:
change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nopti"
into: GRUB CMDLINE_LINUX_DEFAULT="text"
grub has been updated

RESTART
Boot does not stop
Startup is completed.
PC is ready to use.

Test was performed on Ubuntu distribution 16.04 on x86 system.

[Jo Bakker (jojoma)]

NEW TEST with GRUB CMDLINE on another x86 machine

ACTION:
change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
into: GRUB CMDLINE_LINUX_DEFAULT="text"
grub has been updated

RESTART
Boot does stop !!
text on screen:
[40.048004] BUG: unable to handle kernel paging request at fffffffc
[40.048004] IP: print_modules+0x38/0xa5
[40.048004] *pdpt = 000000003445b001 *pde = 0000000010e34063 *pte = 00000000000000

Test was performed on Ubuntu distribution 16.04 on another x86 system.

[Kai-Heng Feng (kaihengfeng)]

Does this issue still happen on an up-to-date kernel?