"Connection to xwayland lost" freezes and appears to take Fedora 38 on Kernel 6.3.x down with it

I’m a long time Fedora user, using it both on a laptop and a desktop, and I like to keep my systems up to date. When the time came to upgrade the kernel version on both of my systems from 6.2 to 6.3, I did so. My desktop (Intel NUC) has no stability issues in running the latest kernel, but my laptop (Dell Inspiron 7506) has frozen within five minutes after logging in while on any 6.3 kernel version in all but one case. But configuring grub to boot into kernel 6.2(.15), the freezing no longer occurs.

When the laptop freezes, it behaves more like the computer isn’t even on at all, but is still displaying what it did when (X11) froze. This behavior has happened on every 6.3.x.fc38 kernel I have tried: 6.3.4, 6.3.6, 6.3.8, and 6.3.11. In fact, with that last one, I had a boot that had a total uptime of one minute before (X11) froze.

After this boot, I checked the logs, and this time I found some errors that might explain what happened, which I will share here.

The freeze happens almost consistently on high CPU usage (in the case above it happened while I was building a program from source code), but the identical level of CPU usage on Kernel 6.2.15 does not freeze the system.

relevant hardware specs
CPU: 11th Gen Intel i7-1165G7
GPU: Intel TigerLake-LP GT2 [Iris Xe Graphics] Integrated Graphics

I will almost certainly be filing a report on Bugzilla, but I want to be sure my understanding is correct for the bug report: X11 is crashing on Fedora 38 with Kernel 6.3.x, taking the whole system down, forcing the user to restart the computer, and load a 6.2.x Kernel.

Edit: I have run a hardware probe on the laptop as mentioned in another topic, and here is what I got. Says my graphics card driver is not found or configured, but I don’t know what steps to take from there, or even if it’s causing the problem (seems unlikely to me).

1 Like

An update. This problem is still happening on 6.5.x as well, and 6.4.x on high CPU usage. Unsure what is causing it, and I keep getting

i’ve run the logs multiple times on priority 4 and I think it’s appropriate to compare the logs between normal operation (on 6.2.15) and the most recent version now (6.5.6)

theyre a bit too long to send in a screenshot so i’ll link a zip of these logs below:
Upload files for free - logs.zip - ufile.io (link will die in 30 days – 13 Nov 2023)