Ryzen 4800u, kernel 5.8.5 boot errors (AMD-Vi, ACPI, HDCP, Bluetooth)

Bug #1893624 reported by rud
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Lenovo Ideapad S540 13ARE (AMD Ryzen 4800U).
Ubuntu Budgie 20.04.1 LTS, updated kernel to 5.8.5. Secure Boot disabled. Clean install with entire disk (Windows came preinstalled) wiped out.

Most things work just fine. If not for the errors shown during boot, I would not have noticed the issues.Video (native resolutions works), audio, wifi, suspend, the quick buttons (brightness, volume etc) all work fine. However during boot, errors are shortly shown:

asterix@Idefix:~$ sudo dmesg -l err
[ 3.204455] pci 0000:00:00.2: AMD-Vi: Unable to read/write to IOMMU perf counter.
[ 4.901524] I2C multi instantiate pseudo device driver INT3515:00: IRQ index 1 not found
[ 4.919327] snd_pci_acp3x 0000:03:00.5: Invalid ACP audio mode : 0
[ 4.939476] ACPI Error: No handler for Region [ECSI] (00000000bf2d92b9) [EmbeddedControl] (20200528/evregion-127)
[ 4.939724] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20200528/exfldio-261)
[ 4.939929] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20200528/psparse-529)
[ 4.940212] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20200528/psparse-529)
[ 4.940517] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
[ 5.235689] acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
[ 6.273068] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link!
[ 6.273591] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link!
[ 6.273748] [drm:dm_helpers_dp_write_dpcd [amdgpu]] *ERROR* Failed to find connector for link!
[ 7.036019] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.
[ 7.891436] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)```

lspci-vnvn.log: https://pastebin.com/Kygie8nu

What can I do to help solve this? Note I am not a developer and a Linux novice.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-08-30 (0 days ago)
InstallationMedia: Ubuntu-Budgie 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Package: linux (not installed)
Tags: focal
Uname: Linux 5.8.5-050805-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip input lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

rud (jazco)
description: updated
description: updated
rud (jazco)
description: updated
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 1893624

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
Revision history for this message
rud (jazco) wrote : ProcCpuinfoMinimal.txt

apport information

tags: added: apport-collected focal
description: updated
Revision history for this message
rud (jazco) wrote : ProcEnviron.txt

apport information

Revision history for this message
Alex Hung (alexhung) wrote :

Linux 5.8.5-050805, or any kernels on https://kernel.ubuntu.com/~kernel-ppa/mainline/, is not a supported kernel version.

Kernel 5.8 is also used on groovy. Please download and install deb @ https://people.canonical.com/~alexhung/LP1893624/

Once installed, please verify errors and update bug descriptions if errors are still present.

Revision history for this message
rud (jazco) wrote :

Thanks, I did that (sudo dpkg -i *.deb and sudo update-grub) but it still reboots with 5.8.5. I googled a bit but haven't figured out how to boot with 5.8 and remove 5.8.5.

I could start fresh with a clean Ubuntu install again..

Revision history for this message
rud (jazco) wrote :

It worked: via grub booted 5.8 and no more errors at boot. However, brightness setting is not persistent after a reboot anymore, screen is at max brightness after each reboot. If I modify it using the keyboard, it immediately starts at the lowest brightness.

It's a minor issue. Not a big deal.

I will stay away from 5.8.5 for now. Thanks for your help!

Revision history for this message
Alex Hung (alexhung) wrote :

You can use apt purge to remove installed kernel: sudo apt purge linux-image-... linux-header-..., where ... is the version you want to remove.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
rud (jazco) wrote :

Yes I figured that out, managed to uninstall and remove the default kernel (5.4) and the 'bad' one (5.8.5).

Only 2 minor issues remaining:
1) Brightness setting is not persistent after reboot (it was with 5.8.5).
When I turn brightness down using the quick keyboard button, it goes immediately to almost lowest, so the % of brightness is stored in the OS, but the screen itself booted with max brightness.

2) Hibernation does not work:
$ sudo systemctl hibernate
Failed to hibernate system via logind: Not enough swap space for hibernation
Even though my /swapfile is 6.4 GB (40% of 16GB) and only 20% of my RAM is in use.

Not big issues, since I can adjust brightness and I can use suspend.

Revision history for this message
Dehuan Xin (dxin2015) wrote :

[ 6.146732] [drm:mod_hdcp_add_display_to_topology [amdgpu]] *ERROR* Failed to add display topology, DTM TA is not initialized.

I'm also seeing this error on 5.8.0-19-generic kernel.
It's ThinkPad T14 gen1 device with 4750u CPU/GPU with HDMI display connected to the USB-C dock.

Revision history for this message
Ivan Kovnatsky (ikovnatsky) wrote :

I don't run Ubuntu myself, but Linux is Linux:

```
[ 14.934677] ACPI Error: No handler for Region [ECSI] (0000000024032c9e) [EmbeddedControl] (20201113/evregion-128)
[ 14.937851] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20201113/exfldio-261)
[ 14.941080] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20201113/psparse-529)
[ 14.944321] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20201113/psparse-529)
[ 14.948265] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2
[ 17.200797] amdgpu 0000:04:00.0: amdgpu: Unsupported power profile mode 0 on RENOIR
```

kernel: 5.11.5

Revision history for this message
MichaelE (michael-eitelwein) wrote :

I get the following error on Lenovo Yoga 7 Gen 6 AMD (14ACN6) on Ubuntu 21.10 with kernel 5.15.0-051500-generic #202110312130 SMP Sun Oct 31 21:33:20 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

[ 3.216924] usbcore: registered new interface driver btusb
[ 3.241133] ACPI Error: No handler for Region [ECSI] (000000008d9ed4b0) [EmbeddedControl] (20210730/evregion-130)
[ 3.241182] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20210730/exfldio-261)

[ 3.241221] No Local Variables are initialized for Method [ECRD]

[ 3.241224] No Arguments are initialized for method [ECRD]

[ 3.241229] ACPI Error: Aborting method \_SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20210730/psparse-529)
[ 3.241278] ACPI Error: Aborting method \_SB.UBTC._DSM due to previous error (AE_NOT_EXIST) (20210730/psparse-529)
[ 3.241350] ACPI: \_SB_.UBTC: failed to evaluate _DSM (0x6)
[ 3.241364] ucsi_acpi USBC000:00: ucsi_acpi_dsm: failed to evaluate _DSM 2

Revision history for this message
MichaelE (michael-eitelwein) wrote :

My CPU is AMD Ryzen 7 5800U with Radeon Graphics (family: 0x19, model: 0x50, stepping: 0x0)

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.