Ryzen 5 3500U - laptop won't boot when on battery power

[Gregor]

Ryzen 5 3500U (release in 2019) won't boot when laptop is on battery power. It affects different brands of laptops. Laptop boots normally with charger in and you can unplug the charger and then use battery.
For some a work around is possible on kernel 5.4. For others kernel should be 5.5 or better yet 5.6.

issue described in more detail in Ubuntu forums: https://ubuntuforums.org/showthread.php?t=2446942

dmesg: https://paste.ubuntu.com/p/C2xNzpBKq5/

iommu=soft boot options provides the work arround on some laptops, while on others USB ports stop working.

OS: Kubuntu 20.04 LTS

CPU: Ryzen 5 3500U
GPU: AMD Vega 8
RAM: 8 GB DDR4 2400 Mhz
disk: 256 GB nvme

I patched kernel (now tainted) to get driver for rtl8821ce (wi-fi).

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1887218/+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.]

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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 1887218

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.

[Alex Hung (alexhung)]

Since the workaround involves amd's iommu and kernel 5.5, we may be able to find a patch that fixes this by cherry-pikcy: git log --pretty=short v5.4..v5.5 -- drivers/iommu/amd_iommu.c

commit 1daa56bcfd8b329447e0c1b1e91c3925d08489b7
Merge: a5255bc31673 9b3a713feef8
Author: Linus Torvalds <email address hidden>

    Merge tag 'iommu-updates-v5.5' of git://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu

commit 995e2ef08280dab8de6c517acd836613678fe2a3
Merge: 1fca7e0e6fe6 ae5e6c6439c3 cb0701acfa7e b5b42b24d783 2e127203d116
Author: Rafael J. Wysocki <email address hidden>

    Merge branches 'acpi-utils', 'acpi-platform', 'acpi-video' and 'acpi-doc'

commit 9b3a713feef8db41d4bcccb3b97e86ee906690c8
Merge: 4e7120d79edb da6b05dce2a9 1289f7f15001 5b47748ecf2e c90ae4a63541 96d3ab802e49 34d1b0895dbd 3c124435e8dd 6c3a44ed3c55 c1c8058dfb98 808be0aae53a
Author: Joerg Roedel <email address hidden>

    Merge branches 'iommu/fixes', 'arm/qcom', 'arm/renesas', 'arm/rockchip', 'arm/mediatek', 'arm/tegra', 'arm/smmu', 'x86/amd', 'x86/vt-d', 'virtio' and 'core' into next

commit 3c124435e8dd516df4b2fc983f4415386fd6edae
Author: Logan Gunthorpe <email address hidden>

    iommu/amd: Support multiple PCI DMA aliases in IRQ Remapping

commit 3332364e4ebc0581d133a334645a20fd13b580f1
Author: Logan Gunthorpe <email address hidden>

    iommu/amd: Support multiple PCI DMA aliases in device table

commit a5bbbf37c6f8522a1afd46c37b5a0d1ce63232b7
Author: Denys Vlasenko <email address hidden>

    iommu/amd: Do not re-fetch iommu->cmd_buf_tail

commit 3057fb9377eb5e73386dd0d8804bf72bdd23e391
Author: Joerg Roedel <email address hidden>

    iommu/amd: Pass gfp flags to iommu_map_page() in amd_iommu_map()

commit 470eb3b31134ada545dcb41e94a0c97b42c95803
Author: Suthikulpanit, Suravee <email address hidden>

    iommu/amd: Simpify decoding logic for INVALID_PPR_REQUEST event

commit ae5e6c6439c3d0ac8e9c71523790ba1ff6887894
Author: Andy Shevchenko <email address hidden>

    iommu/amd: Switch to use acpi_dev_hid_uid_match()

commit be62dbf554c5b50718a54a359372c148cd9975c7
Author: Tom Murphy <email address hidden>

    iommu/amd: Convert AMD iommu driver to the dma-iommu api

commit 781ca2de89bae1b1d2c96df9ef33e9a324415995
Author: Tom Murphy <email address hidden>

    iommu: Add gfp parameter to iommu_ops::map

commit 37ec8eb851c1876580a963f283fe7496592b9f72
Author: Tom Murphy <email address hidden>

    iommu/amd: Remove unnecessary locking from AMD iommu driver

[Alex Hung (alexhung)]

A test kernel, based on UBUNTU: Ubuntu-5.4.0-42.46, is available @ https://people.canonical.com/~alexhung/LP1887218/ver1/

If this solves this bug, we can keep bisecting. If not, we can try other patches.

The following commits are excluded:

== merges ==
1daa56bcfd8b329447e0c1b1e91c3925d08489b7
995e2ef08280dab8de6c517acd836613678fe2a3
9b3a713feef8db41d4bcccb3b97e86ee906690c8

== cannot clean picked ==
3c124435e8dd516df4b2fc983f4415386fd6edae
3332364e4ebc0581d133a334645a20fd13b580f1

We can come back to these if the test kernel fails.

== fail to compile ==
ae5e6c6439c3d0ac8e9c71523790ba1ff6887894
This requires additional patch(es) but this is to replace an existing function with acpi_dev_hid_uid_match and should not have any effects

[Sam B (damnigotaproblemwithmy3500u)]

Hiya - I get this too.

HP 15s-eq0507na:
Ryzen 5 3500U + Vega 8 iGPU
8GB DDR4
256GB M.2 NVME SSD

Always had this problem since the release of 20.04 - tried w/ secure boot on and off.

Haven't tried the iomu=soft thing yet

Others evidently have this problem (I swear I saw a thread ab this on launchpad a month ago):
https://elementaryos.stackexchange.com/questions/22817/inconsistent-booting-on-battery-ryzen-3500u
https://askubuntu.com/questions/1206472/ubuntu-18-04-and-20-04-stuck-on-gnome-startup-on-battery-only

Thanks

[Sam B (damnigotaproblemwithmy3500u)]

I found the thread I talked about.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870971

the laptop the first poster has a 3500U in it according to google and a few comments mentioned it

[Kai-Heng Feng (kaihengfeng)]

Please run `apport-collect 1887218` to upload logs here so we can take a look what happened.

[Launchpad Janitor (janitor)]

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