Ubuntu doesn't boot with 4.13.0 kernels

Bug #1751584 reported by bmaupin on 2018-02-25
64
This bug affects 13 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Edit: the 4.13.0.37 kernel doesn't boot either.

My system won't boot with the 4.13.0.36 kernel. Yesterday it hung at a flashing cursor screen. I updated a few packages yesterday (see below) and today it hangs at this screen:

Loading Linux 4.13.0.36-generic ...
Loading initial ramdisk ...
_

Booting to the previous kernel (4.13.0-32) seems to work just fine.

I'm using Ubuntu 16.04.3 on a Thinkpad T430u with an Intel i5-3317U.

Is this possibly related to this bug?: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742675

$ lsb_release -rd
Description: Ubuntu 16.04.4 LTS
Release: 16.04

$ apt-cache policy linux-image-4.13.0-36-generic
linux-image-4.13.0-36-generic:
  Installed: 4.13.0-36.40~16.04.1
  Candidate: 4.13.0-36.40~16.04.1
  Version table:
 *** 4.13.0-36.40~16.04.1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages
        100 /var/lib/dpkg/status

$ tail -n 2 /var/log/apt/history.log
Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), google-chrome-stable:amd64 (64.0.3282.167-1, 64.0.3282.186-1), python-apt-common:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), grub2-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc-bin:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), ntpdate:amd64 (1:4.2.8p4+dfsg-3ubuntu5.7, 1:4.2.8p4+dfsg-3ubuntu5.8), ubuntu-drivers-common:amd64 (1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 (1:16.04.23, 1:16.04.24), libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), libpulse0:i386 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-core:amd64 (1:16.04.23, 1:16.04.24), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python-apt:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), pulseaudio-utils:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 (1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 (9.4ubuntu4.5, 9.4ubuntu4.6)
End-Date: 2018-02-24 10:22:59

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.13.0-36-generic 4.13.0-36.40~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Feb 25 08:37:33 2018
InstallationDate: Installed on 2014-05-08 (1388 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: linux-hwe
UpgradeStatus: Upgraded to xenial on 2016-08-05 (568 days ago)

bmaupin (bmaupin) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-hwe (Ubuntu):
status: New → Confirmed
Caspar Jordan (kaspar-jordan) wrote :

I have the same problem on 17.10. My computer hangs at a slightly different point, see attached screenshot.

Booting into 4.13.0-32 works fine.

not available (error.500) wrote :

This seems to be a caused by NVIDIA driver on Ubuntu 17.10 (see attachment). Can anyone confirm this?

bmaupin (bmaupin) wrote :

I'm using Ubuntu 16.04 with Intel graphics.

bmaupin (bmaupin) on 2018-03-17
summary: - Ubuntu doesn't boot with 4.13.0-36 kernel
+ Ubuntu doesn't boot with 4.13.0-36/37 kernels
description: updated

The weirdest thing just happened yesterday. 4.13.0-37 wouldn't boot, so I tried 4.13.0-32. The boot process got stuck at this line:

APCI: EC: interrupt blocked

So I tried 4.13.0-37 again and it worked...

I'm definitely confused now.

The only change I made was to do a verbose boot (https://askubuntu.com/a/926700/18665) so I could see the logs.

bmaupin (bmaupin) wrote :

After having intermittent problems booting 4.13.0-32, 4.13.0-36, and 4.13.0-37 I uninstalled those kernels (which also uninstalled linux-generic-hwe-16.04 and linux-image-generic-hwe-16.04) as well as intel-microcode. I'm running the 4.4 kernel that comes with 16.04 now with zero problems. It's not ideal but since 17.10 won't be supported much longer anyway, I'll just wait for the 18.04 kernel.

summary: - Ubuntu doesn't boot with 4.13.0-36/37 kernels
+ Ubuntu doesn't boot with 4.13.0 kernels
Lorenz Werner (l.werner) wrote :

For me the 4.13.0-36 kernel works just fine.
However, 4.13.0-37 and 4.13.0-38 won't boot.

KyleH (kyle-hayes) wrote :
Download full text (3.4 KiB)

I have three systems of which two show this problem.

Two systems are ASUS "All-in-One PC ET2230I". One is an ACER All-in-One PC Aspire C24-760.

All were installed from Ubuntu 16.04.1 and have been updated to the latest patch sets as of 2018/04/14.

The ASUS systems do not boot with 4.13.0-38. The hang is the same as above with the last thing showing that the kernel was loading the RAM disk. The ACER system boots fine with the -38 kernel.

The two kernels I tried on these systems are:

(Working on ASUS)
Linux domiclient2.domistyle.ad 4.13.0-31-generic #34~16.04.1-Ubuntu SMP Fri Jan 19 17:11:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

(Working on ACER, but failing on ASUS)
Linux domiclient1.domistyle.ad 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I manually selected the -31 kernel and the two ASUS systems boot correctly. No obvious problems. When I either manually interrupt GRUB and select the -38 kernel or I allow GRUB to select it, the ASUS systems hang.

The non-working ASUS systems have older CPUs:

root@domiclient2:~# cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 60
model name : Intel(R) Core(TM) i3-4150T CPU @ 3.00GHz
stepping : 3
microcode : 0x22
cpu MHz : 2993.244
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid xsaveopt dtherm arat pln pts
bugs : cpu_meltdown spectre_v1 spectre_v2
bogomips : 5986.48
clflush size : 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:

The ACER system has a newer CPU:

cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 78
model name : Intel(R) Core(TM) i3-6100U CPU @ 2.30GHz
stepping : 3
microcode : 0x84
cpu MHz : 800.011
cache size : 3072 KB
physical id : 0
siblings : 4
core id : 0
cpu cores : 2
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti retpoline intel_pt rsb_ctxsw tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdsee...

Read more...

KyleH (kyle-hayes) wrote :

Forgot to mention that these systems are all Intel IGP. No add-on graphics chips.

bmaupin (bmaupin) wrote :

It looks like I was also suffering from this bug:

https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920

If anyone's having issues booting, I'd recommend downgrading intel-microcode as described in the workaround for that bug.

In my case my machine still wouldn't boot with 4.13.0 kernels, so I guess it's still 2 separate bugs.

affects: linux-hwe (Ubuntu) → linux (Ubuntu)
bmaupin (bmaupin) wrote :

I hesitatingly upgraded to 18.04, and the 4.15 kernel that it comes with booted just fine, so it seems like this issue is limited to the 4.13 kernels that come with 17.10/16.04 HWE.

This is what I have now:

$ lsb_release -rd
Description: Ubuntu 18.04 LTS
Release: 18.04

$ uname -a
Linux thinkpad 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I am having the same problem. Mine is the latest version of UBUNTU with Kernal 4.15.0-42-generic
.

bmaupin (bmaupin) wrote :

After upgrading my BIOS the problem came back again with the 4.15 kernels. I was able to solve the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"

Once I did that, the kernels worked fine as did intel-microcode.

I'll update the description and details of the ticket to reflect my findings.

bmaupin (bmaupin) wrote :

...on second thought, I'm not sure updating it would be the best idea since the end problem appears to be specific to my hardware. I think it's probably better to mark this bug as invalid and create a new one.

Changed in linux (Ubuntu):
status: Confirmed → Invalid
bmaupin (bmaupin) wrote :

I went ahead and filed this new bug that's more specific to my hardware: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418

bmaupin (bmaupin) on 2019-02-04
Changed in linux (Ubuntu):
status: Invalid → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers