Kernel 60 laggy on amd?

Has it maybe to do with the Retbleed update?

Thanks for testing. That’s bizarre…

So the reason for this could be in the specific cpu from me or my kernel settings. Or what could I do next?

  1. Try to remove them and add mitigations=off
  2. Edit /etc/mkinitcpio.conf to add amdgpu in MODULES.
  3. run sudo mkinitcpio -P && sudo update-grub
  4. Create a new file /etc/X11/xorg.conf.d/20-amdgpu.conf if you are using Xorg.
Section "Device"
    Identifier "AMD"
    Driver "amdgpu"
    Option "TearFree" "true"
EndSection
  1. Plug the cable of the power supply into your laptop.
  2. Reboot and select Kernel LTS or 6.0, see if it works?

I don’t have lagginess. Kernel 6.0.2

[alex@alex-b450aoruselite ~]$ glmark2
=======================================================
    glmark2 2021.12
=======================================================
    OpenGL Information
    GL_VENDOR:     AMD
    GL_RENDERER:   AMD Radeon RX 570 Series (polaris10, LLVM 14.0.6, DRM 3.48, 6.0.2-3-MANJARO)
    GL_VERSION:    4.6 (Compatibility Profile) Mesa 22.2.1
=======================================================
[build] use-vbo=false: FPS: 10216 FrameTime: 0.098 ms
[build] use-vbo=true: FPS: 16236 FrameTime: 0.062 ms
[texture] texture-filter=nearest: FPS: 15904 FrameTime: 0.063 ms
[texture] texture-filter=linear: FPS: 15724 FrameTime: 0.064 ms
[texture] texture-filter=mipmap: FPS: 15537 FrameTime: 0.064 ms
[shading] shading=gouraud: FPS: 14846 FrameTime: 0.067 ms
[shading] shading=blinn-phong-inf: FPS: 14992 FrameTime: 0.067 ms
[shading] shading=phong: FPS: 14837 FrameTime: 0.067 ms
[shading] shading=cel: FPS: 14716 FrameTime: 0.068 ms
[bump] bump-render=high-poly: FPS: 11891 FrameTime: 0.084 ms
[bump] bump-render=normals: FPS: 16385 FrameTime: 0.061 ms
[bump] bump-render=height: FPS: 16625 FrameTime: 0.060 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 14449 FrameTime: 0.069 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 10824 FrameTime: 0.092 ms
[pulsar] light=false:quads=5:texture=false: FPS: 14971 FrameTime: 0.067 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 6945 FrameTime: 0.144 ms
[desktop] effect=shadow:windows=4: FPS: 10027 FrameTime: 0.100 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 1687 FrameTime: 0.593 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 2168 FrameTime: 0.461 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 2055 FrameTime: 0.487 ms
[ideas] speed=duration: FPS: 6905 FrameTime: 0.145 ms
[jellyfish] <default>: FPS: 12395 FrameTime: 0.081 ms
[terrain] <default>: FPS: 1757 FrameTime: 0.569 ms
[shadow] <default>: FPS: 13529 FrameTime: 0.074 ms
[refract] <default>: FPS: 3210 FrameTime: 0.312 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 15625 FrameTime: 0.064 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 16491 FrameTime: 0.061 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 15930 FrameTime: 0.063 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 15892 FrameTime: 0.063 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 15694 FrameTime: 0.064 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 15644 FrameTime: 0.064 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 15614 FrameTime: 0.064 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 15686 FrameTime: 0.064 ms
=======================================================
                                  glmark2 Score: 12285 
=======================================================

no differences unfortunately…
glmark2 Score: 1580

What is the output

$ sudo cpupower frequency-info

Maybe this is related to power saving when using APU on laptop.

CPU 0 wird analysiert:
  driver: acpi-cpufreq
  CPUs, die mit der gleichen Hardwarefrequenz laufen: 0
  CPUs, die ihre Frequenz mit Software koordinieren müssen: 0
  Maximale Dauer eines Taktfrequenzwechsels:  Cannot determine or is not supported.
  Hardwarebegrenzungen: 1.40 GHz - 1.70 GHz
  available frequency steps:  1.70 GHz, 1.60 GHz, 1.40 GHz
  verfügbare cpufreq-Regler: conservative ondemand userspace powersave performance schedutil
  momentane Richtlinie: Frequenz sollte innerhalb 1.40 GHz und 1.70 GHz.
                    sein. Der Regler "schedutil" kann frei entscheiden,
                    welche Geschwindigkeit er in diesem Bereich verwendet.
  current CPU frequency: 1.40 GHz (asserted by call to hardware)
  boost state support:
    Unterstützt: ja
    Aktiv: ja
    Boost-Zustände: 0
    Gesamtzustände: 3
    Pstate-P0:  1700MHz
    Pstate-P1:  1600MHz
    Pstate-P2:  1400MHz
  1. Change “Schedutil” to “performance”
    sudo cpupower frequency-set --governor performance

  2. Check sudo cpupower frequency-info again, if it shows “performance”

  3. Plug the cable of the power supply into your laptop.

  4. Then test the benchmark.

The result is a bit higher, but don’t think it’s a real difference. Every test I made was with power supply.

glmark2 Score: 1648

Check if journalctl -b -p err --no-page shows kernel error messages?

If no error, try to enable AMD P-state instead acpi-cpufreq.

If it does not help, I am out of ideas, then You can report Issues · drm / amd · GitLab

it doesn’t look like kernel errors… I will do the pstate-instruction

Okt 18 12:46:06 T14 systemd-modules-load[387]: Failed to find module 'v4l2loopback-dc'
Okt 18 12:46:06 T14 systemd-modules-load[387]: Failed to find module 'acpi_call'
Okt 18 12:46:06 T14 systemd-modules-load[387]: Failed to find module 'acpi_call'
Okt 18 12:46:06 T14 systemd-modules-load[387]: Failed to find module 'acpi_call'
Okt 18 12:46:06 T14 systemd-modules-load[387]: Failed to find module 'acpi_call'
Okt 18 12:46:06 T14 systemd-modules-load[387]: Failed to find module 'v4l2loopback'
Okt 18 12:46:06 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found
Okt 18 12:46:06 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error requesting irq at index 1
Okt 18 12:46:08 T14 bluetoothd[813]: src/plugin.c:add_plugin() Version mismatch for sixaxis
Okt 18 12:46:08 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 12:46:10 T14 systemd[1117]: /run/user/1000/systemd/generator.late/app-org.kde.yakuake@autostart.service:18: WorkingDirectory= path is not absolute, ignoring: 
Okt 18 12:46:12 T14 kded5[1318]: org.kde.plasma.dataengine.geolocation: error:  "Unbekannter Rechner location.services.mozilla.com: Rechner konnte nicht gefunden werden"
Okt 18 12:46:13 T14 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Okt 18 12:46:14 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 12:46:14 T14 bluetoothd[813]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
Okt 18 12:46:19 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 12:47:02 T14 nmbd[5236]: [2022/10/18 12:47:02.966003,  0] ../../source3/nmbd/nmbd.c:901(main)
Okt 18 12:47:02 T14 nmbd[5236]:   nmbd version 4.17.0 started.
Okt 18 12:47:02 T14 nmbd[5236]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Okt 18 12:47:03 T14 smbd[5242]: [2022/10/18 12:47:03.020563,  0] ../../source3/smbd/server.c:1741(main)
Okt 18 12:47:03 T14 smbd[5242]:   smbd version 4.17.0 started.
Okt 18 12:47:03 T14 smbd[5242]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Okt 18 12:47:04 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 12:47:26 T14 nmbd[5236]: [2022/10/18 12:47:25.997370,  0] ../../source3/nmbd/nmbd_become_lmb.c:398(become_local_master_stage2)
Okt 18 12:47:26 T14 nmbd[5236]:   *****
Okt 18 12:47:26 T14 nmbd[5236]: 
Okt 18 12:47:26 T14 nmbd[5236]:   Samba name server T14 is now a local master browser for workgroup WORKGROUP on subnet 192.168.2.11
Okt 18 12:47:26 T14 nmbd[5236]: 
Okt 18 12:47:26 T14 nmbd[5236]:   *****
Okt 18 12:47:26 T14 systemd[1]: Failed to start DisplayLink Manager Service.

And then a lot of “Failed to start DisplayLink Manager Service.”-errors

Why do you use DisplayLink?

Try to disable it: sudo systemctl disable --now displaylink.service

Try to install linux[VERSION]-headers, then run sudo mkinitcpio -P, reboot.

1 Like

I can’t find CPPC-settings in the T14 BIOS settings (Ryzen 7 PRO 4750U)

journalctl -b 0 | grep pstate
answers with
Failed to insert module 'amd_pstate': No such device

so I only can use acpi-cpufreq… ?

I didn’t know that I can use displaylink features without the displaylink package too…

linux headers is already installed.

now I reboot to check the displaylink error. Thanks for the hint!

The displaylink errors are still there but significantly fewer

Okt 18 13:59:33 T14 systemd-modules-load[371]: Failed to find module 'v4l2loopback-dc'
Okt 18 13:59:33 T14 systemd-modules-load[371]: Failed to find module 'acpi_call'
Okt 18 13:59:33 T14 systemd-modules-load[371]: Failed to find module 'acpi_call'
Okt 18 13:59:33 T14 systemd-modules-load[371]: Failed to find module 'acpi_call'
Okt 18 13:59:33 T14 systemd-modules-load[371]: Failed to find module 'acpi_call'
Okt 18 13:59:33 T14 systemd-modules-load[371]: Failed to find module 'v4l2loopback'
Okt 18 13:59:33 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found
Okt 18 13:59:33 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error requesting irq at index 1
Okt 18 13:59:34 T14 bluetoothd[742]: src/plugin.c:add_plugin() Version mismatch for sixaxis
Okt 18 13:59:34 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 13:59:36 T14 systemd[1073]: /run/user/1000/systemd/generator.late/app-org.kde.yakuake@autostart.service:18: WorkingDirectory= path is not absolute, ignoring: 
Okt 18 13:59:38 T14 kded5[1276]: org.kde.plasma.dataengine.geolocation: error:  "Unbekannter Rechner location.services.mozilla.com: Rechner konnte nicht gefunden werden"
Okt 18 13:59:38 T14 kded5[1276]: org.kde.plasma.dataengine.geolocation: error:  "Unbekannter Rechner location.services.mozilla.com: Rechner konnte nicht gefunden werden"
Okt 18 13:59:39 T14 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Okt 18 13:59:40 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 13:59:40 T14 bluetoothd[742]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object upon power down
Okt 18 13:59:46 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 13:59:51 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 13:59:57 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 14:00:03 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 14:00:08 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 14:00:14 T14 systemd[1]: Failed to start DisplayLink Manager Service.
Okt 18 14:00:19 T14 systemd[1]: Failed to start DisplayLink Manager Service.

Did you update the last version of BIOS firmware ?

If no CPPC, you can use acpi-cpufreq only.

Remove displaylink from AUR.

Try to install v4l2loopback-dkms and acpi_call-dkms

1 Like

yes

OK

done

v4l2loopback-dkms was already installed and acpi_call-dkms is no installed. error message is gone

Here the current output.

Okt 18 14:30:21 T14 systemd-modules-load[376]: Failed to find module 'v4l2loopback-dc'
Okt 18 14:30:21 T14 systemd-modules-load[376]: Failed to find module 'v4l2loopback'
Okt 18 14:30:21 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: IRQ index 1 not found
Okt 18 14:30:21 T14 kernel: Serial bus multi instantiate pseudo device driver INT3515:00: error -ENXIO: Error requesting irq at ind
ex 1
Okt 18 14:30:22 T14 systemd[1]: displaylink.timer: Refusing to start, unit displaylink.service to trigger not loaded.
Okt 18 14:30:22 T14 systemd[1]: Failed to start Start Displaylink with 5 Sec delay..
Okt 18 14:30:22 T14 bluetoothd[781]: src/plugin.c:add_plugin() Version mismatch for sixaxis
Okt 18 14:30:25 T14 systemd[1086]: /run/user/1000/systemd/generator.late/app-org.kde.yakuake@autostart.service:18: WorkingDirectory
= path is not absolute, ignoring:
Okt 18 14:30:27 T14 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Okt 18 14:30:32 T14 bluetoothd[781]: src/adv_monitor.c:btd_adv_monitor_power_down() Unexpected NULL btd_adv_monitor_manager object
upon power down

Thanks a lot already! I think, it goes now off-topic, didn’t it? You helped already a lot.

Now I will have to make to open an issue in gitlab I think…Or somebody other has still an idea…

Disable “displaylink.timer” that does not need to trigger displaylink service:
sudo systemctl disable --now displaylink.timer

1 Like

I think, I found a bug-report related to this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=17d819e2828cacca2e4c909044eb9798ed379cd2

With kernel 6.0.3 I get nearly the same glmark score like with 5.18:
Score: 3263

Now I’m using linux-manjaro-xanmod (6.0.3-1)
So, it’s fine.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.