16.04.1 LTS hang during boot 4.4.0-45-generic with /etc/crypttab. Boots fine in 4.4.0-42-generic and older

[normandrobert]

System hangs during boot with 4.4.0-45-generic if /etc/crypptab contains a valid entry. Passphrase prompt never seen. Black screen with blinking underscore in upper left corner. Repeated attempts to type passphrase have no effect.

There are two workarounds:
1) Comment out line referring the encrypted partition in /etc/crypttab and /etc/fstab. Mount the partition manually after boot completes
2) Boot in 4.4.0-42-generic which works as do earlier versions. i.e. the user provides passphrase at the prompt during boot and the system finishes booting

robert@kalymnos:~$ cat /etc/crypttab
spare2 UUID=498b08bb-5e6b-4ddf-8b37-e059665a34e6 none luks
robert@kalymnos:~$ grep mapper /etc/fstab
/dev/mapper/spare2 /spare2 ext4 defaults 0 2
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: robert 2413 F.... pulseaudio
 /dev/snd/controlC0: robert 2413 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=291e75f9-3814-499b-bbb2-f385c164b942
InstallationDate: Installed on 2016-08-18 (83 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lo no wireless extensions.

 enp0s25 no wireless extensions.
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-42-generic root=UUID=24166ab8-327a-4477-96d2-3f57b4a47657 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-42-generic N/A
 linux-backports-modules-4.4.0-42-generic N/A
 linux-firmware 1.157.4
RfKill:

Tags: xenial
Uname: Linux 4.4.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 07/29/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SOX5810J.86A.5600.2013.0729.2250
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX58SO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE29331-701
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrSOX5810J.86A.5600.2013.0729.2250:bd07/29/2013:svn:pn:pvr:rvnIntelCorporation:rnDX58SO:rvrAAE29331-701:cvn:ct2:cvr:
---
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: robert 2413 F.... pulseaudio
 /dev/snd/controlC0: robert 2413 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=291e75f9-3814-499b-bbb2-f385c164b942
InstallationDate: Installed on 2016-08-18 (83 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IwConfig:
 lo no wireless extensions.

 enp0s25 no wireless extensions.
JournalErrors:
 Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system.
       Users in the 'systemd-journal' group can see all messages. Pass -q to
       turn off this notice.
 No journal files were opened due to insufficient permissions.
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-42-generic root=UUID=24166ab8-327a-4477-96d2-3f57b4a47657 ro quiet splash
ProcVersionSignature: Ubuntu 4.4.0-42.62-generic 4.4.21
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-42-generic N/A
 linux-backports-modules-4.4.0-42-generic N/A
 linux-firmware 1.157.4
RfKill:

Tags: xenial
Uname: Linux 4.4.0-42-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 07/29/2013
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SOX5810J.86A.5600.2013.0729.2250
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DX58SO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE29331-701
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrSOX5810J.86A.5600.2013.0729.2250:bd07/29/2013:svn:pn:pvr:rvnIntelCorporation:rnDX58SO:rvrAAE29331-701:cvn:ct2:cvr:

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1640297

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[normandrobert (sub1)]

apport information

[Joseph Salisbury (jsalisbury)]

I started a kernel bisect between Ubuntu 4.4.0-42 and Ubuntu 4.4.0-45. The kernel bisect will require testing of about 7-10 test kernels.

I built the first test kernel, up to the following commit:
0ae0d9de89eaca45d70ee7a7b961c1e2bf504022

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1640297

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[normandrobert (sub1)]

Ran apport-collect yesterday. It does not seem appropriate for me as the submitter to change the status to "complete" as suggested above :)

[normandrobert (sub1)]

wget -nH -r --cut-dirs=2 -l1 -A.deb -e robots=off http://kernel.ubuntu.com/~jsalisbury/lp1640297/
sudo dpkg -i *.deb
sudo reboot
Choose 4.4.0-43 custom kernel wait wait :) .. hangs like before. Next!

[Joseph Salisbury (jsalisbury)]

I built the next test kernel, up to the following commit:
08556c973d37789102b0058f79ec77f8b88983ab

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1640297

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[normandrobert (sub1)]

Hangs when Booting in 4..4.0-43 generic as shown in pic after having added pkgs as shown below.

I am assuming that I don't need to remove anything that was already there like the previous kernel iteration etc. so that I can just keep doing dpkg -i with your latest debs

firstuser@kalymnos:~/temp/$ mkdir 2; cd 2;
wget -nH -r --cut-dirs=2 -l1 -A.deb -e robots=off http://kernel.ubuntu.com/~jsalisbury/lp1640297/
firstuser@kalymnos:~/temp/2$ sudo dpkg -i *.deb
[sudo] password for firstuser:
(Reading database ... 521823 files and directories currently installed.)
Preparing to unpack linux-cloud-tools-4.4.0-43_4.4.0-43.63~lp1640297Commit08556c97_amd64.deb ...
Unpacking linux-cloud-tools-4.4.0-43 (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-43.63~lp1640297Commit0ae0d9de89) ...
Preparing to unpack linux-cloud-tools-4.4.0-43-generic_4.4.0-43.63~lp1640297Commit08556c97_amd64.deb ...
Unpacking linux-cloud-tools-4.4.0-43-generic (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-43.63~lp1640297Commit0ae0d9de89) ...
dpkg: warning: downgrading linux-cloud-tools-common from 4.4.0-47.68 to 4.4.0-43.63~lp1640297Commit08556c97
Preparing to unpack linux-cloud-tools-common_4.4.0-43.63~lp1640297Commit08556c97_all.deb ...
Unpacking linux-cloud-tools-common (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-47.68) ...
dpkg: warning: downgrading linux-doc from 4.4.0-47.68 to 4.4.0-43.63~lp1640297Commit08556c97
Preparing to unpack linux-doc_4.4.0-43.63~lp1640297Commit08556c97_all.deb ...
Unpacking linux-doc (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-47.68) ...
Preparing to unpack linux-headers-4.4.0-43_4.4.0-43.63~lp1640297Commit08556c97_all.deb ...
Unpacking linux-headers-4.4.0-43 (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-43.63~lp1640297Commit0ae0d9de89) ...
Preparing to unpack linux-headers-4.4.0-43-generic_4.4.0-43.63~lp1640297Commit08556c97_amd64.deb ...
Unpacking linux-headers-4.4.0-43-generic (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-43.63~lp1640297Commit0ae0d9de89) ...
Preparing to unpack linux-image-4.4.0-43-generic_4.4.0-43.63~lp1640297Commit08556c97_amd64.deb ...
Done.
Unpacking linux-image-4.4.0-43-generic (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-43.63~lp1640297Commit0ae0d9de89) ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.4.0-43-generic /boot/vmlinuz-4.4.0-43-generic
Preparing to unpack linux-image-extra-4.4.0-43-generic_4.4.0-43.63~lp1640297Commit08556c97_amd64.deb ...
Unpacking linux-image-extra-4.4.0-43-generic (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-43.63~lp1640297Commit0ae0d9de89) ...
dpkg: warning: downgrading linux-source-4.4.0 from 4.4.0-47.68 to 4.4.0-43.63~lp1640297Commit08556c97
Preparing to unpack linux-source-4.4.0_4.4.0-43.63~lp1640297Commit08556c97_all.deb ...
Unpacking linux-source-4.4.0 (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-47.68) ...
Preparing to unpack linux-tools-4.4.0-43_4.4.0-43.63~lp1640297Commit08556c97_amd64.deb ...
Unpacking linux-tools-4.4.0-43 (4.4.0-43.63~lp1640297Commit08556c97) over (4.4.0-43.63~lp1640297Commit0a...

[normandrobert (sub1)]

Just being anal here to make sure that I am doing what I am supposed to/expected.

[Joseph Salisbury (jsalisbury)]

Thanks for asking and confirming on the installation of kernels. That is the correct process. We only have one or two more to go.

I built the next test kernel, up to the following commit:
8d796174763c89ec63b45699665d66ddf2050296

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1640297

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

[normandrobert (sub1)]

http://kernel.ubuntu.com/~jsalisbury/lp1640297 empty or file permission problem

[Joseph Salisbury (jsalisbury)]

Sorry for the delay. The test kernel should be there now.

[normandrobert (sub1)]

Hangs like the others

[normandrobert (sub1)]

Should I expect a response or new kernel? Regards.

[Joseph Salisbury (jsalisbury)]

The bisect reported commit 8d796174763c89ec63b45699665d66ddf2050296 as the first bad commit. This really doesn't make sense. That commit is just a start release.

However, I still built a test kernel with that commit reverted.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1640297

Can you test that kernel and report back if it has the bug or not?

[Marc-Antoine Ruel (maruel)]

I've done a fresh install of 16.04.1 desktop amd64 this weekend; after the first kernel upgrade from 4.4.0-31 to 4.4.0-57, it refused to boot. I had to manually select -31 back in grub to be able to boot the system.

In my case, /etc/crypttab is my root partition so I can't comment it out. I'm surprised this wasn't hit by more people. Nobody uses FDE?

[Marc-Antoine Ruel (maruel)]

Uninstalling the nvidia binary driver (367.57) and moving back to Nouveau "fixed" the problem for me. The reproducibility of this problem seems to dependent on the nvidia video card model, as I have another workstation with another nvidia card model and the other one had no issue with the boot prompt on newer kernel.

The boot prompt UI definitely changed between -31 and -57 and the video driver probably mess up. So I don't think it's the kernel itself but plymouth (? or whatever prompts for the FDE password) upgrade that happened around the same time.

[normandrobert (sub1)]

HELLO so you spend time making kernels, I spend time installing and rebooting my system and then the process dies. Seems kind of pointless don't you think?

[normandrobert (sub1)]

My 4.4.0-42 kernel which booted fine and was my workaround for months now hangs at boot like the later versions. I also discovered that I can boot in 42 recovery mode and I get asked the luks password at boot. I suspect a bad interaction with something else that got updated like possibly the nvidia graphics which I am rather dependent on due to CUDA etc.

Now running...
firstuser@kalymnos:~/scripts$ uname -a
Linux kalymnos 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
and I mount the encrypted filesystem via a sudo bash script

[Joseph Salisbury (jsalisbury)]

The v4.10-rc5 kernel is now available. Can you test that kernel to see if it still exhibits the bug? It can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10-rc5

[aPlatypus (william-full-moon)]

I am getting this with 4.4.0-59-generic, I'm booted off a thumb drive using 4.4 and this systems update manager is prompting to upgrade the kernel to 4.4.0-59. Which I'm obviously NOT doing. However my point is why is this still in circulation -- Shouldn't it be pulled off the list of packages?

I am not sure how other people managed to get command output, my system hangs just after it says Loading Virtual Drive or RAM-disk. And "Console not available" which sucks, since it is just dead.

Also I am not sure about numbering scheme here. Is v4.10-rc5, 0.6 increments away from 4.4.0-59? Is that the right way to read this?

[normandrobert (sub1)]

My 4.4.0-42 kernel which booted fine and was my workaround for months now hangs at boot like the later versions. I also discovered that I can boot in 42 recovery mode and I get asked the luks password at boot. I suspect a bad interaction with something else that got updated like possibly the nvidia graphics which I am rather dependent on due to CUDA etc.

Now running...
firstuser@kalymnos:~/scripts$ uname -a
Linux kalymnos 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
and I mount the encrypted filesystem via a sudo bash script :(