AMD AGESA PinnaclePI-AM4_1.0.0.6 causes amdgpu hang on boot

Bug #1809934 reported by Grant Kim
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

CPU: AMD Ryzen 5 2400G / AMD Ryzen 3 2200G
Version: Ubuntu 18.04.1 Desktop (AMD64)
Kernel: 4.15.0-43 generic
Mainboard: ASUS Prime X370-Pro (4207), ASRock B450 Pro4 (1.80), MSI B350 Tomahawk (7A34v1K), Gigabyte GA-AB350M-Gaming3 (F24c)

Detailed information:
AMD AGESA version "PinnaclePI-AM4 1.0.0.6" based firmware is released by many major mainboard manufacturers lately.
However, this 1.0.0.6 based firmware with Raven Ridge processors (2200G, 2400G and more) cause system hangs on boot if a system is running 4.15.0 kernel.

If install kernel version 4.18.0-13-generic from "linux-image-generic-hwe-18.04-edge" has no issue.

Here is boot messages output (dumped via serial port and truncated):

[ 4.385021] [drm] ring test on 5 succeeded in 3 usecs
[ 4.385030] [drm] ring test on 6 succeeded in 2 usecs
[ 4.385035] [drm] ring test on 7 succeeded in 1 usecs
[ 4.385044] [drm] ring test on 8 succeeded in 2 usecs
[ 4.385090] [drm] ring test on 10 succeeded in 2 usecs
[ 5.406001] clocksource: timekeeping watchdog on CPU2: Marking clocksource 'tsc' as unstable because the skew is too large:
[ 5.406002] clocksource: 'hpet' wd_now: 5152d87 wd_last: 40b14df mask: ffffffff
[ 5.406004] clocksource: 'tsc' cs_now: f4c92bc9d cs_last: ebf5adbce mask: ffffffffffffffff
[ 5.406006] tsc: Marking TSC unstable due to clocksource watchdog
[ 5.406014] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
[ 5.406015] sched_clock: Marking unstable (5406009219, 0)<-(5548358599, -142345214)
[ 7.906021] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 9.156104] [drm:amdgpu_ring_insert_nop [amdgpu]] *ERROR* amdgpu: writing more dwords to the ring than expected!
[ 11.656035] ata2.00: ATA-8: TOSHIBA DT01ACA200, MX4OABB0, max UDMA/133
[ 32.204004] watchdog: BUG: soft lockup - CPU#2 stuck for 21s! [kworker/2:1:60]
[ 32.204005] Modules linked in: hid_logitech_hidpp hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 amdgpu(+) chash i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect uas sysimgblt fb_sys_fops drm r8169 usb_storage i2c_piix4 mii ahci libahci wmi video gpio_a

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1809934/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1809934

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: cosmic
Revision history for this message
jacobbrett (jacobbrett) wrote :

I think I am suffering from a related bug.

Asrock X370 Taichi, BIOS 5.10 (2018-12-21).
Ryzen 5 2600X.
Radeon RX 580.
Ubuntu 18.04.02 (HWE). I tested with kernel 4.15 and 4.18, no difference.

Can not boot via GRUB with amdgpu driver, unless "amdgpu.dpm=0" is set.

I only integrated the RX 580 into the build recently, after updating to BIOS 5.10 (AGESA 1.0.0.6), so I haven't yet tested previous BIOS versions with this card. I wonder if this latest BIOS update is affecting AMDGPU's DPM?

https://www.asrock.com/mb/AMD/X370%20Taichi/#BIOS

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

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.