Asahi kernel update causes catastrophic slowdown

[ppp7032]

Is this a new report?

Yes

System Info

Void 7.1.5+2-asahi_1 aarch64 Unknown uptodate rrF

Package(s) Affected

linux-asahi-7.1.9+1_1, linux-asahi-7.1.8+1_1

Does a report exist for this bug with the project's home (upstream) and/or another distro?

No response

Expected behaviour

GUI is responsive.

Actual behaviour

Since I updated from Kernel 7.1.5 to 7.1.8 (and above), my system has become unusably slow. My mouse cursor lags across my screen and anything updating on my KDE GUI is terribly slow too. It's strange, it's like I can see updates to my display happen as a scan line moves down my screen. It's almost like my display is set to a refresh rate of 1 and I get to watch the refresh happen as it moves down my screen slowly.

I've attached my kernel log for reference.

dmesg-2.log

Steps to reproduce

1. Update to kernel 7.1.8
2. Attempt to use GUI

[dkwo]

Is this with the laptop's or external monitor? logs from your desktop environment? can you reproduce it e.g. with a wlroots-based compositor?

[dkwo]

Another thing I can think of is updating m1n1-stage1 and firmware from within macos using the installer, but since this machine is M1, I am not sure it will help.

[ppp7032]

Updating m1n1 and firmware didn't help.

Also I'm not sure I was clear before - everything works fine for me as long as I boot with the old kernel which I never deleted (7.1.5+2-asahi_1).

I've attached KDE plasma logs.

kde-bad.log
kde-good.log

From observing the mouse cursor in Sway on the new and old kernels, I can conclude that the issue does also exist when I use Sway. It's much less dramatic and only manifested as a slightly laggy cursor. I didn't try opening any windows because tiling window managers scare me.

[ppp7032]

The "bad" logs are when using the new kernel and "good" are when the old one.

[ppp7032]

Oh and this is on the laptop's display, yes.

[dkwo]

Got it. Looks like it's not using the GPU for rendering

< kwin_wayland_drm: Could not find edid for connector DrmConnector(id=39, gpu="/dev/dri/card0", name="Unknown-1", connection="Connected", countMode=1)
---
> kwin_wayland_drm: Could not find edid for connector DrmConnector(id=47, gpu="/dev/dri/card2", name="eDP-1", connection="Connected", countMode=6)

Output of ls -la /dev/dri in both cases?

[dkwo]

Are you booting uboot-grub-dracut?

[dkwo]

If the render node is still available, can you try exporting KWIN_RENDER_NODES=/dev/dri/renderD128 or the appropriate value for your case?