Package Base Details: linux-amd-znver2

Git Clone URL: (read-only, click to copy)
Submitter: eggz
Maintainer: eggz (NhaMeh)
Last Packager: eggz
Votes: 7
Popularity: 1.85
First Submitted: 2020-10-26 18:04
Last Updated: 2021-05-18 09:39

Pinned Comments

eggz commented on 2020-10-26 18:15

Tired of compiling? Use this binary repo instead! Add this at the end of /etc/pacman.conf :

Server =$repo/$arch
SigLevel = Optional TrustAll

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

eggz commented on 2021-02-19 16:34

Hey, smart maintainers actually just wait for upstream and do nothing. I'm not a smart maintainer. I am an impatient one. I think I'm going to leave it like that, take the big problem out, let upstream take care of the rest. (Unless it's still not fixed in 5.11.1, then I'll have another look)

Thank you so much for your feedback. Now I know it's worth implementing on all my kernels. It's hard to debug/fix for hardware you do not even have.

scruffidog commented on 2021-02-19 16:24

I think you targeted the right fiddly bits. I've performed the poweroff under a few different scenarios and they all seem to work correctly in that when I take it down, it stays down.

The weird trace and the "Renoir unsupported power profile" issues are still there. One step at a time.

eggz commented on 2021-02-19 07:56

@scruffidog I implemented a proposed shutdown patch for renoir hardware. It seems to work in most cases (but not all of them).

If you are able, please provide feedback to me, to see if it is worth implementing on all kernels (or its just better to wait for upstream if it doesnt work in most cases).

eggz commented on 2021-02-19 07:33

This is probably the new renoir modules that aren't working 100%. The vanilla arch kernel works because they never bother activating AMD modules and that might be the probable cause.

as mentioned before this is probably because of these modules (which vanilla doesnt activate)


If the complaints still keep rolling in after 5.11.1, I am disabeling these modules ...


Looks like you are not the only one:

scruffidog commented on 2021-02-19 04:32

something weird with this kernel: when I try to poweroff by doing "poweroff" or "systemctl poweroff" with this kernel, it always winds up rebooting. I thought I was going crazy until I reinstalled the standard linux-5.11.arch2-1 kernel where it then behaves normally. how do I even begin to debug this ?

I was trying to figure out other issues where I'm getting the following error mesgs:

[ 3.188408] ------------[ cut here ]------------ [ 3.188411] WARNING: CPU: 6 PID: 633 at net/wireless/nl80211.c:7652 nl80211_get_reg_do+0x22e/0x2a0 [cfg80211] [ 3.188482] Modules linked in: snd_hda_codec_realtek(+) iommu_v2 gpu_sched i2c_algo_bit drm_ttm_helper fjes(-) ccm snd_hda_codec_generic ttm algif_aead ledtrig_audio snd_hda_codec_hdmi cbc snd_hda_intel des_generic snd_acp3x_rn snd_intel_dspcfg libdes snd_soc_dmic drm_kms_helper snd_acp3x_pdm_dma snd_hda_codec hid_sensor_gyro_3d snd_soc_core hid_sensor_accel_3d hid_sensor_magn_3d hid_sensor_trigger industrialio_triggered_buffer kfifo_buf hid_sensor_iio_common snd_hda_core industrialio ac97_bus snd_pcm_dmaengine snd_hwdep snd_pcm cec snd_timer snd syscopyarea sysfillrect hid_sensor_hub sysimgblt snd_rn_pci_acp3x fb_sys_fops soundcore snd_pci_acp3x amd_sfh algif_skcipher cmac sha512_ssse3 sha512_generic md4 algif_hash af_alg joydev mousedev iwlmvm hid_multitouch mac80211 hid_generic libarc4 iwlwifi nls_iso8859_1 edac_mce_amd nls_cp437 hp_wmi(+) kvm_amd vfat fat cfg80211 sparse_keymap ccp wmi_bmof kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel tpm_crb k10temp evdev [ 3.188557] aesni_intel input_leds crypto_simd pcspkr tpm_tis led_class tpm_tis_core cryptd glue_helper rfkill tpm i2c_piix4 i2c_hid ucsi_acpi rng_core typec_ucsi typec thermal wmi video hid battery ac acpi_cpufreq pinctrl_amd button amd_pmc acpi_tad sch_fq_codel tcp_bbr drm pkcs8_key_parser msr fuse crypto_user ip_tables x_tables xfs libcrc32c crc32c_generic rtsx_pci_sdmmc mmc_core serio_raw atkbd libps2 xhci_pci xhci_hcd crc32c_intel nvme usbcore nvme_core usb_common t10_pi rtsx_pci i8042 serio [ 3.188613] CPU: 6 PID: 633 Comm: iwd Not tainted 5.11.0-AMD-znver2 #1 [ 3.188617] Hardware name: HP HP ENVY x360 Convertible 15m-ee0xxx/876F, BIOS F.15 11/12/2020 [ 3.188620] RIP: 0010:nl80211_get_reg_do+0x22e/0x2a0 [cfg80211] [ 3.188674] Code: 89 ef c7 44 24 0c 01 00 00 00 e8 3d 03 49 e1 85 c0 74 cc e9 ff fe ff ff 48 89 ef 48 89 04 24 e8 08 1e 6b e1 48 8b 04 24 eb 89 <0f> 0b 48 89 ef e8 f8 1d 6b e1 b8 ea ff ff ff e9 75 ff ff ff b8 97 [ 3.188678] RSP: 0018:ffffb79e41c7fb60 EFLAGS: 00010202 [ 3.188682] RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 [ 3.188684] RDX: ffff95208e4c8008 RSI: 0000000000000000 RDI: ffff95208e4c8300 [ 3.188686] RBP: ffff9520841e6500 R08: 0000000000000004 R09: ffff952082c1f014 [ 3.188688] R10: 0000000000000020 R11: ffff95208d88b0c0 R12: ffffb79e41c7fbc0 [ 3.188690] R13: ffff952082c1f014 R14: 0000000000000000 R15: ffff95208e4c8300 [ 3.188693] FS: 000077440c5d2740(0000) GS:ffff952f4f780000(0000) knlGS:0000000000000000 [ 3.188696] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 3.188698] CR2: 000077440c55d4e0 CR3: 000000010d912000 CR4: 0000000000150ee0 [ 3.188701] Call Trace: [ 3.188707] genl_family_rcv_msg_doit+0xfd/0x160 [ 3.188721] genl_rcv_msg+0xf0/0x1e0 [ 3.188726] ? nl80211_vendor_cmd_dump+0x5e0/0x5e0 [cfg80211] [ 3.188778] ? nl80211_send_regdom.constprop.0+0x1b0/0x1b0 [cfg80211] [ 3.188832] ? genl_get_cmd+0xc0/0xc0 [ 3.188836] netlink_rcv_skb+0x5b/0x100 [ 3.188841] genl_rcv+0x24/0x40 [ 3.188844] netlink_unicast+0x23c/0x340 [ 3.188848] netlink_sendmsg+0x233/0x460 [ 3.188855] __sys_sendto+0x18e/0x1a0 [ 3.188864] __x64_sys_sendto+0x25/0x30 [ 3.188868] do_syscall_64+0x33/0x40 [ 3.188875] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 3.188882] RIP: 0033:0x77440c6d5680 [ 3.188886] Code: c0 ff ff ff ff eb b8 0f 1f 00 f3 0f 1e fa 41 89 ca 64 8b 04 25 18 00 00 00 85 c0 75 1d 45 31 c9 45 31 c0 b8 2c 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 68 c3 0f 1f 80 00 00 00 00 55 48 83 ec 20 48 [ 3.188889] RSP: 002b:00007ffced034038 EFLAGS: 00000246 ORIG_RAX: 000000000000002c [ 3.188893] RAX: ffffffffffffffda RBX: 0000575a904e3c00 RCX: 000077440c6d5680 [ 3.188895] RDX: 000000000000001c RSI: 0000575a90503330 RDI: 0000000000000004 [ 3.188897] RBP: 0000575a90502ee0 R08: 0000000000000000 R09: 0000000000000000 [ 3.188899] R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffced0340b8 [ 3.188901] R13: 00007ffced0340b4 R14: 0000575a904ed890 R15: 0000000000000000 [ 3.188905] ---[ end trace e842f3efd640ead4 ]---

and further down:

amdgpu: Unsupported power profile mode 0 on RENOIR

This is on a HP Envy x360 with the 4700u.

eggz commented on 2021-02-18 12:53

I identified the AMDgpu troubles in the linux-next tree and "backported" the patch


This reverts commit 8866a67ab86cc0812e65c04f1ef02bcc41e24d68.

This breaks hotplug of HDMI on some systems, resulting in
a blank screen also causes failures for displays to light up
on other systems.

There are a bunch of other fixes in upstream (linux-next), but this one seems standalone and is compatible with the stable tree. I'm not going to put everything upstream inhere, this seems to be enough for me to supress all the AMDGPU errors.

I tested this on 2 machines already and it seems to have good results.

eggz commented on 2021-02-16 15:06

Nice man! Lemme know the results.

Just to be overly clear, set those options to

# CONFIG_AMD_SFH_HID is not set
# CONFIG_AMD_PMC is not set

Let me know that it fixes anything if you are able to. Good luck!

dedguy21 commented on 2021-02-16 15:02


Thanks. I don't mind compiling as it was my main excuse in buying so many darn cores in the first place :)

eggz commented on 2021-02-16 08:56


There were alot of renoir code additions in 5.11 (and I activated them), and I can only hope they were good. If they aren't, theres not much I can do about that. I don't even have renoir hardware :/

I also saw some AMDGPU problems on my vega based hardware on 5.11, but if your problems are CPUrelated, that sends even more chills up my spine ...

I hope they will fix it in 5.11.1 or later. I think it's best you keep checking on every release if things get better or not.

Another option is to disable the new RENOIR options and recompile the kernel:


I think PMC is a strong contender in being a problematic new module explaining the troubles you have..

IF you're intrested in this last option but don't like to compile, I'll do it for you, just let me know. (since I don't have the hardware..)

dedguy21 commented on 2021-02-16 07:25

I have a Dell G5 SE 5505, ryzen 4900H renoir chip, plus radeon 5600M graphics. Any rate have been using this kernel since you split it away from linux-amd, and everything was working fine until this last 5.11-xx update. Performance was horrible, machine stuttered at everything, even booting took longer than usual.

Just an FYI, not sure if anyone else will have the issue, but I had to downgrade back to 5.10-16, that fixed my issues.