Hang at login with nvidia proprietary driver and encrypted swap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
initramfs-tools (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
plymouth (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Tested with initramfs-tools 0.130ubuntu3.1 and initramfs-tools 0.130ubuntu3.2, both have the same bug. 0.130ubuntu3 works fine.
Description: Ubuntu 18.04 LTS
Release: 18.04
Reproed with nvidia-396 396.24.02-0ubuntu and the 390 package as well.
System is using a nvidia 1050TI mobile. With prime-select to nvidia.
My setup includes an encrypted home dir, and encrypted ram disk. Boot drive is an Nvme ssd.
When installing the older working package I see this message:
I: The initramfs will attempt to resume from /dev/dm-0
I: (UUID=34e1ed83-
I: Set the RESUME variable to override this.
I don't that that message from the broken packages.
With the broken packages, once I login from gdm3, the computer freezes. I haven't been able to find a related error in the logs.
Workarounds with the nvidia driver have included switching the prime-select to intel, swapping to the nouveau drivers, or booting with nvidia-
Downgrading to initramfs-tools 0.130ubuntu3 solves the problem without needing to make and nvidia driver changes.
Also removing `quite splash` from the boot options also solves the issue. So it appears the bug here is likely in plymouth.
Took another crack at debugging this and got my package upgraded. I get the same freeze if I set RESUME=None, but if I set `RESUME= UUID=$( blkid -s UUID -o value "/dev/mapper/ cryptswap1" )` I was able to get the old behaviour back on the newer initramfs-tools
From looking at the newer initramfs-tools diff I don't think but bug is here, but that the change here is further revealing the bug.
I posted an issue for some support on the nvidia dev forum here: https:/ /devtalk. nvidia. com/default/ topic/1050238/ linux/freeze- after-login- screen- in-ubuntu- 18-04-with- 1050ti- mobile/
And was pointed toward plymouth likely being part of the problem. Sure enough, by removing `quite splash` from the boot options, the problem also goes away.