Ubuntu won't launch after the Ubuntu, with Linux 4.4.0-39 generic update

[Juhani Korhonen]

I am running Linux Ubuntu 16.04 LTS, and I've discussed in a thread at 'Ask Ubuntu: System update almost broke the system' about the Kernel Bug — as suggested by a local user boddhi.zazen — that I experienced as I was running my system updates. The problem occurs with "Ubuntu, with Linux 4.4.0-39 generic", although I am still able to access Ubuntu with the older "Ubuntu, with Linux 4.4.0-38 generic" via "+Advanced options for Ubuntu".

Here's what happened:

1. I first ran the upgrade procedures through terminal as usual: sudo apt-get update, sudo apt-get upgrade, sudo apt-get autoremove, and sudo apt-get autoremove
2. However, I was told that "4 not upgraded", so I decided to run Software Updater as well, and there was indeed updates available concerning "Ubuntu base". I installed those successfully, and decided to proceed with restart my system.

After the restart, my system doesn't start though. Instead, I receive the following error message:

<-- THE BEGINNING, NOT PART OF THE ERROR MESSAGE -->
[ 1.452270] genirq: Flags mismatch irq 0. 00000080 (nvme0q0) vs. 00015a00 (timer)
[ 1.452551] iounmap: bad address ffffc90001b88000
Scanning for Btrfs filesystems
Gave up waiting for root device. Common problems:
 - Boot args (cat /proc/cmdline)
  - Check rootdelay= (did the system wait for the right device?)
  - Check root= (did the system wait for the right device?)
 - Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=a5ccaf22-ffde-44c2-8c59-84a851f9fd90 does not exist. Dropping to shell!

BusyBox v1.222.1 (Ubuntu 1:1.22.0-15ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)
<-- THE END, NOT PART OF THE ERROR MESSAGE -->

I was able to recover my system through the "+Advanced options for Ubuntu", which I opened after. There I had total of nine choices, three options for each version. I first tried the "recovery version" of the latest one, but it didn't work. After that, I tried the "generic version" of the second latest, and — thank God — that one managed to recover my system! I believe the package is called linux-image-4.4.0-39-generic ("Ubuntu, with Linux 4.4.0-38 generic" in the menu")

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.16
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CrashDB: ubuntu
Date: Mon Oct 3 16:19:33 2016
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

So you can boot your system if you select the -38 kernel from the GRUB menu but not the -39?

[Juhani Korhonen (juhani-j-korhonen)]

@jsalisbury Exactly.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream stable kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 stable kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.25

[Juhani Korhonen (juhani-j-korhonen)]

tag 'kernel-fixed-upstream'.

[Joseph Salisbury (jsalisbury)]

The upstream 4.4.24 updates are now in the 4.4.0-46.67 Ubuntu kernel. This is the current kernel in the -proposed repository.

Can you test the -46 proposed kernel?

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed.

[Chris (squintysloth)]

Hi, first time here. Please excuse my ignorance if I am going against standard protocol. I have the same message on Ubuntu Mate 16.04 LTS after update to vmlinuz-4.4.0-45-generic. I was able to boot into recovery mode on reboot. The dpkg repair option got me up and running again after downloading a missing xorg.conf file. Now after a few days of use and going through the boot sequence normally I have been affected twice by this again. The first time a simple reboot without the use of recovery had me back in. Now, I have not decided what action to take as it seems persistent, and would like to bring it to someone's attention. I am certain now that the kernel prior to the update boots, and will use it until I receive a practical solution. I believe it has more to do with a bad initrd.img file than any changes to the boot arguments as none were applied manually. I will happily provide more information/logs as necessary, but I have to wonder if this elicits a new bug report or not. Thanks.

[Chris (squintysloth)]

Simply adding -mate at the end of the launchpad url on the main page brought me to a Mate version of this site I did not know existed prior. Sorry to bother you all, I will repost there.