Unable to boot after upgrade to 18.04 (only works with 16.04 kernel)

Bug #1774029 reported by manuw2009
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I upgraded from 16.04 my ASUS X201E laptop to 18.04, but now I can only boot with the 16.04 kernel (4.4.0.x), I can't seem to boot with the 4.15 kernel (I tried 4.14 & 4.16 as well, to no avail).
Booting with the 4.4 kernel leads to the login screen and everything works OK, while booting with the 4.15 kernel remains stalled on the Ubuntu startup screen with dots, ESC shows traces stuck? on "Reached target Network is Online"
I can successfully boot the 18.04 desktop image though, so I am assuming the issue comes from configuration files and not from the kernel itself. Any help would be highly appreciated !

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.17
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: MATE
Date: Tue May 29 19:05:08 2018
InstallationDate: Installed on 2014-11-19 (1286 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeAptlog:
 Log time: 2018-05-22 20:51:41.459776
 Starting pkgProblemResolver with broken count: 0
 Starting 2 pkgProblemResolver with broken count: 0
 Done

Revision history for this message
manuw2009 (manu-wagner) wrote :
Revision history for this message
manuw2009 (manu-wagner) wrote :

This is the bootlog I get with the old (working) kernel

Revision history for this message
manuw2009 (manu-wagner) wrote :

And dmesg with non working kernel...

Revision history for this message
manuw2009 (manu-wagner) wrote :

bootlog when not working...

description: updated
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

From boot.log there are several timeout and dependency failure for the mount points

[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-5012d3a8\x2d10bc\x2d4218\x2d9563\x2de3243df441bc.device.
[DEPEND] Dependency failed for /media/DATA.
[DEPEND] Dependency failed for Local File Systems.
[DEPEND] Dependency failed for Clean up any mess left by 0dns-up.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/5012d3a8-10bc-4218-9563-e3243df441bc.
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-D725\x2d5E75.device.
[DEPEND] Dependency failed for /boot/efi.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/D725-5E75.
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-2a28f257\x2d2c49\x2d4396\x2d87d8\x2d25febae99938.device.
[DEPEND] Dependency failed for /dev/disk/by-uuid/2a28f257-2c49-4396-87d8-25febae99938.
[DEPEND] Dependency failed for Swap.
[ TIME ] Timed out waiting for device dev-disk-by\x2duuid-72b61b47\x2d1391\x2d45b4\x2d8619\x2de51b48548e11.device.
[DEPEND] Dependency failed for File System Check on /dev/disk/by-uuid/72b61b47-1391-45b4-8619-e51b48548e11.
[DEPEND] Dependency failed for /home.

affects: ubuntu-release-upgrader (Ubuntu) → systemd (Ubuntu)
Revision history for this message
manuw2009 (manu-wagner) wrote :

Hi,
You're right but I get them as well with the working kernel.
How would I fix that though ?

Revision history for this message
manuw2009 (manu-wagner) wrote :

boot-info file...

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Dan Streetman (ddstreet) wrote :

please reopen if this is still an issue

Changed in systemd (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.