CPUs stuck during boot after 19.10 upgrade to 5.3.0-40

Bug #1863759 reported by Michael
42
This bug affects 8 people
Affects Status Importance Assigned to Milestone
ubuntu-release-upgrader (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

lsb_release:
Ubuntu 19.10
Release 19.10

Boot process stops at blank screen with .....[76.575608] watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [systemd-udev:411] [48.523054] watchdog: BUG: soft lockup - CPU#3 stuck for 1s! [swapper/3:0]

I rebooted holding the shift key and was able to reboot into 5.3.0-29 which runs with no issues.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15.4
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.4
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 18 08:15:52 2020
InstallationDate: Installed on 2019-10-29 (111 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

Changed in ubuntu-release-upgrader (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrei Belov (defan) wrote :

Which hardware are you on?

I'm seeing exactly the same behavior on Ubuntu 19.10 and KDE Neon on Lenovo Ideapad S340-14API with AMD Ryzen 3200U / Radeon Vega Mobile Gfx on board.

The 5.3.0-28 kernel works just fine, while 5.3.0-40 shows the following effect:
 - on Ubuntu 19.10, booting never ends due to random "BUG: soft lockup - CPU#xx stuck for 23s! [system-udevd:383]" events, thus causing various jobs/services to hang forever;
 - on KDE Neon, I'm seeing failures with amdgpu driver somewhere in amdgpu_mm_rreg with a call trace ending with gfx_v9_0_set_safe_mode() call.

Appreciate any input.

Revision history for this message
Andrei Belov (defan) wrote :

Just for the record - the only way I can boot 5.3.0-40 on the hardware mentioned in previous message is to use the "nomodeset" parameter, obviously leading to absence of GUI.

Revision history for this message
Michael (mshumer0517) wrote : Re: [Bug 1863759] Re: CPUs stuck during boot after 19.10 upgrade to 5.3.0-40

I am using a Lenovo IdeaPad L340 with AMD  Ryzen 3 processor and Radeon
VEGA graphics by AMD

Glad its not just me.

:)

On 2/19/20 1:26 AM, Andrei Belov wrote:
> Which hardware are you on?
>
> I'm seeing exactly the same behavior on Ubuntu 19.10 and KDE Neon on
> Lenovo Ideapad S340-14API with AMD Ryzen 3200U / Radeon Vega Mobile Gfx
> on board.
>
> The 5.3.0-28 kernel works just fine, while 5.3.0-40 shows the following effect:
> - on Ubuntu 19.10, booting never ends due to random "BUG: soft lockup - CPU#xx stuck for 23s! [system-udevd:383]" events, thus causing various jobs/services to hang forever;
> - on KDE Neon, I'm seeing failures with amdgpu driver somewhere in amdgpu_mm_rreg with a call trace ending with gfx_v9_0_set_safe_mode() call.
>
> Appreciate any input.
>

Revision history for this message
Sergey (sergeysi779) wrote :

Same issue on AMD Athlon 300U (basically a Ryzen 3). 5.3.0-29 works, 5.3.0-40 doesn't.

Revision history for this message
Ron Bentley (rtbentley) wrote :

I am joining the chorus only to confirm this seems to be related to a specific set of hardware. I got the same result on an Acer Aspire 5, AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx: 5.3.0-40 fails to boot (or fails to boot to the full graphical login) and 5.3.0-29 continues to work just fine.

Revision history for this message
James Horine (james-horine) wrote :

Me too on AMD hardware:

AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx

can boot and run 5.3.0-28 but NOT 5.3.0-40 installed last night at recommendation of Discover app on Ubuntu 18.04

Revision history for this message
Jan Troll (jantroll) wrote :

I have the same problem with 5.3.0-40 kernel on Ubuntu 18.04.4 , 5.3.0-28 works without any problems.
My hardware is:
AMD Athlon 3000G
ASRock B450M-HDV R4.0 with R3.70 UEFI BIOS
8GB 3000MHz DDR4 RAM
240GB Crucial BX500 SSD

Revision history for this message
halmholz (halmholz) wrote :

Can confirm. HP Notebook with AMD Ryzen 3 3200U with Radeon Vega 3 GPU

Revision history for this message
Venzislav Ivanov Stefanov (venzislav) wrote :

The same thing with my hardware :

lenovo notebook LENOVO S340-14API / 81NB008ABM

AMD Dual Core R3-3200U Processor, 2.0 GHz (1M Cache, up to 3.5 GHz)
8 GB DDR4
256 GB SSD | М.2 PCIe NVMe (2280)
AMD Radeon Vega 3

Revision history for this message
Terence Ho (dummy800) wrote :

The latest kernel 5.3.0-42 seems to have resolved the boot problem

Revision history for this message
Ron Bentley (rtbentley) wrote :

I can confirm this seems to be resolved with the 5.3.0-42 kernel packages.

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.