In all honestly, it’s likely that it will. Intel fixed a lot of things with their i915 kernel modules in recents versions.
Let’s hope it works for you!
I mean I went back to kernel 5.10. So far it did not crash with 5.10. I think the new 5.15 kernel is causing the crashes.
It was too early to celebrate. It just froze, crashed and rebooted again. Right after boot the machine is pretty busy and even I drag the windows around or whatever I try I cannot make it crash. But then an hour later or when the machine is quiet with maybe one window open I move or resize the window and it hangs and crashes. This wasn’t the case before the QubesOS dom0 updates.
See also:
I’ve got the exact same issue with kernel 5.15. Now I’ve tried the latest kernel (sudo qubes-dom0-update kernel-latest kernel-latest-qubes-vm) which resulted in kernel 5.18.16-1 and I’m not getting crashes as often. When a freeze does happen I’m only logged out instead of having to power cycle the computer. Will try a bit more to figure out which kernel might be the most stable.
1 Like
I’ve done some extensive testing with kernels 5.10, 5.15, 5.16, 5.18 and combinations of those as well as installing Qubes-20220806-kernel-latest-x86_64.iso from https://qubes.notset.fr/iso/.
I could not avoid Qubes freezing up after 30-60 minutes of standard usage with moderate load. This leads me to believe that it is not a kernel problem.
When using some kernels the Window Manager is restarted when a freeze occurs allowing the user to login again and restart certain hung VMs (which is better than a full restart). Still these problems are quite annoying and will likely mean I’ll have to wait for a future Qubes version or go back to Qubes 4.1.
I agree it is not a kernel problem. I have had this issue trying the various available versions of the kernel with the same results.
Might be worth updating this thread’s title, something like Qubes 4.1.1 freeze for others searching for this issue as it doesn’t seem to be related to the kernel.
My previously rock solid x230 shows this behaviour intermittently, after
recent updates. (Not after 30-60 mins - I cant see any pattern.)
Thanks, done.
Last week I had my first 2 system freezes in 2 days ever… It looked like it was about the RAM (especially since I’m using zram swap), but for months before that I haven’t faced issues while using it and I wasn’t overused my resources more than usual.
And it looks like it isn’t related to these kernels only. Just after writing my previous post, my Qubes simply crashed and rebooted, since I was updating dom0 while writing that post. Today it happened again, so I chose lower version kernel (5.15.52 if I can recall) and update went smoothly. After update I set the kernel-latest as default kernel again. Have no courage to try to update dom0 again under it.
xen_version : 4.14.5
Linux 5.18.16-1.fc32.qubes.x86_64
I updated dom0 the other day and now I managed to keep my laptop running for 8 hours. A few VMs crashed after this time but it’s still a big improvement compared to previously 
Might have been too early to celebrate, seems like Qubes is back to crashing regularly today. Oh well…
I’ve got the same issue. I’ve got graphics artefact and soon after a crash : only the mouse can be moved but nothing responds. I’ve seen that issue : Xen-related dom0 freeze / crash · Issue #7751 · QubesOS/qubes-issues · GitHub and applied the kernel param nouveau.noaccel=1 but I just go a new crash. Really frustrating
Had my first freeze today in my 2+ years of using Qubes.
Froze completely when trying to shutdown a vm, no mouse movement, no switching between tty. Immediately after it froze system looked like it was under massive stress, fans spinning at full speed and temperature increasing, but no network or disk i/o activity. After forced power off it took longer to boot the first time. Guess it run some checks?
Tried to look up something in the logs:
journalctl just shows --Reboot-- and that’s it, can’t see anything abnormal otherwise
Why does it show “Reboot” when the system was powered off, not rebooted?
/var/log/xen/console/hypervisor.log and vm-that-was-shutting-down.log don’t show anything abnormal either
Anywhere else I could look at what might be the cause?
This is all very troubling from a Qubes stability standpoint. I’m using a L380 which has been rock solid for several years until the other day. I use the i3 window manager and was setting a window to floating mode and resizing it when bam! …instant reboot of the system. Never happened before, ever. Nothing in logs, everything up to date.
1 Like
I am also constantly crashing since updating to Qubes 4.1.1. I have reverted to my debian machine as a system that crashes every few hours is essentially useless. I’ve lost a lot of data and time on this.
It’s mostly from the kernel or the hardware system does not have that power to get into. However, mostly heating issues of the hardware system.
It’s not exclusively heating issues that are causing the crashes, but there are heating issues as well. I get heating issues when doing large inter-VM file copies. I don’t know if these heating issues were around prior to 4.1.1.