Bug 204369 - Unable to boot on 5.2 branch
Summary: Unable to boot on 5.2 branch
Status: NEW
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: platform_x86_64@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-29 20:26 UTC by Nic Ola
Modified: 2019-08-15 17:13 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.2.4
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
/var/log/boot.log (1.80 MB, application/octet-stream)
2019-07-29 20:26 UTC, Nic Ola
Details
Log displayed when boot frozen on 5.2.8 kernel (1.58 MB, image/jpeg)
2019-08-15 14:56 UTC, Nic Ola
Details

Description Nic Ola 2019-07-29 20:26:05 UTC
Created attachment 284031 [details]
/var/log/boot.log

Hello,

(I am not quite sure of the product assignment, do not hesitate to change it if required)

I am unable to boot with a kernel from the 5.2 branch on my PC with an AMD Ryzen 2400G APU. File system is Ext4 on Ubuntu 18.04.2 LTS.

I already tried before with 5.2.2 (I think) and just now with 5.2.4 (I'm sure!) still the same, it crashes at boot.
It is booting quite well on the 5.1 branch but it is coming to end of life now.

I don't know where it's coming from, from the logs it could a mounting problem (I have network folders but there is no issue with it on 5.1.x). 

I attached the full /var/log/boot.log file, but here is a part of it, see [FAILED] lines:

[FAILED] Failed to mount Mount unit for core, revision 7169.
See 'systemctl status snap-core-7169.mount' for details.
[FAILED] Failed to mount Mount unit for core, revision 7270.
See 'systemctl status snap-core-7270.mount' for details.
[  OK  ] Started Authorization Manager.
[  OK  ] Started Accounts Service.
[  OK  ] Mounted Mount unit for gnome-calculator, revision 260.
[  OK  ] Mounted Mount unit for indicator-sensors, revision 166.
         Starting Manage, Install and Generate Color Profiles...
[  OK  ] Started Modem Manager.
         Starting Hostname Service...
[  OK  ] Started Disk Manager.
[  OK  ] Started Manage, Install and Generate Color Profiles.
[  OK  ] Started Hostname Service.
[  OK  ] Started Network Manager.
         Starting Network Manager Wait Online...
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started Dispatcher daemon for systemd-networkd.
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Mounted Mount unit for gnome-3-26-1604, revision 90.
[  OK  ] Mounted Mount unit for gnome-characters, revision 296.
[  OK  ] Mounted Mount unit for core18, revision 1055.
[  OK  ] Started Login Service.
[  OK  ] Mounted Mount unit for gnome-characters, revision 292.
[  OK  ] Mounted Mount unit for gnome-calculator, revision 406.
[  OK  ] Mounted Mount unit for notepad-plus-plus, revision 212.
[  OK  ] Mounted Mount unit for wine-platform-runtime, revision 6.
[  OK  ] Mounted Mount unit for gnome-3-28-1804, revision 63.
[  OK  ] Mounted Mount unit for gnome-logs, revision 61.
[  OK  ] Mounted Mount unit for gnome-calculator, revision 352.
[  OK  ] Mounted Mount unit for gnome-3-28-1804, revision 67.
[  OK  ] Mounted Mount unit for core18, revision 1066.
[  OK  ] Mounted Mount unit for wine-platform-3-stable, revision 6.
[FAILED] Failed to mount Mount unit for gnome-system-monitor, revision 100.
See 'systemctl status "snap-gnome\\x2dsystem\\x2dmonitor-100.mount"' for details.
[  OK  ] Mounted Mount unit for wps-office-all-lang-no-internet, revision 1.
[  OK  ] Mounted Mount unit for gtk-common-themes, revision 1313.
[  OK  ] Mounted Mount unit for opera, revision 44.
[  OK  ] Mounted Mount unit for chromium-ffmpeg, revision 13.
[  OK  ] Mounted Mount unit for gtk-common-themes, revision 1198.
[  OK  ] Mounted Mount unit for gnome-system-monitor, revision 95.
[  OK  ] Mounted Mount unit for wine-platform-runtime, revision 23.
[  OK  ] Mounted Mount unit for chromium-ffmpeg, revision 11.
[FAILED] Failed to mount Mount unit for vlc, revision 1049.
See 'systemctl status snap-vlc-1049.mount' for details.


Thanks in advance for our help, let me know if you need any other log. 
I tried to perform "systemctl status snap-vlc-1049.mount" as mentioned in the log but once I booted again on 5.1.x so there is nothing specific to be noted. Let me know how to do it during boot failure if required.

Thanks again for your quick help.
Comment 1 Nic Ola 2019-07-31 20:46:22 UTC
Confirmation I am not the only one impacted, a similar issue was reported here: https://bugzilla.kernel.org/show_bug.cgi?id=204325

Thanks in advance for the investigation as 5.1 branch is at EOL.
Comment 2 Nic Ola 2019-08-15 14:56:30 UTC
Created attachment 284441 [details]
Log displayed when boot frozen on 5.2.8 kernel
Comment 3 Nic Ola 2019-08-15 15:05:45 UTC
I tried again on 5.2.8 kernel, after updating my UEFI to the latest version (P5.90) and Ubuntu 18.04.3 LTS. I still get a boot freeze. I attach a capture of the errors displayed when the boot is frozen. Clearly some errors are reported.

As the 5.1 branch came to an end of life and no support is provided on newest kernel versions, I reverted back to the one provided by Canonical for Ubuntu, which was updated to 5.0 branch for 18.04.3 with HWE support (if someone is interested, explanations and how to do here: https://www.omgubuntu.co.uk/2019/08/ubuntu-18-04-3-point-release )

If it can be relevant for later investigations: I am using MESA drivers from padoka stable ppa (https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/pkppa) which is using MESA 19.1 at the moment. 

I hope this will be fixed when Canonical decides to use 5.2 kernel or later. (very likely for 20.04 LTS at least)
Comment 4 Borislav Petkov 2019-08-15 15:47:49 UTC
Nothing in those log files shows a freeze or a crash - only failed filesystem mounts. Try shutting up systemd by booting with "systemd.log_target=null debug ignore_loglevel log_buf_len=16M" to see if you can catch more interesting info. Or a picture of a crash or so...

Also, is your GPU microcode up-to-date? The package name should be something like firmware-amd-graphics or so...

HTH.
Comment 5 Nic Ola 2019-08-15 17:13:59 UTC
Sorry the only picture of the crash I could get was this one, the system remained stuck at this stage (displayed this after the Ubuntu loading screen disappeared).

Unfortunately I cannot try again as I reverted back to another solution, with an older kernel as I explained above. 

I am not sure of the GPU microcode you mention, but I am using an APU Ryzen 2400G (no dedicated GPU) and my UEFI is the latest one provided by Asrock, so I would say yes.

Note You need to log in before you can comment on or make changes to this bug.