The crash hasn't happened, but the Atomic update failure messages are still present and happening relatively often. Strange how the kernel from command 34 was fine until i915.enable_fbc=0 was set.
By the way, does the bisect from the duplicate make sense? I found the result strange, but it seemed to fix it to me.
For now (1 hour and 40 minutes running glxgears in one screen), the system hasn't crashed. With the following command line:
BOOT_IMAGE= /boot/vmlinuz- 5.4.30+ root=UUID= 6b4ae5c0- c78c-49a6- a1ba-029192618a 7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ ignored_ msrs=0 kvm.halt_poll_ns=0 kvm.halt_ poll_ns_ grow=0 i915.enable_fbc=0 i915.enable_gvt=1 resume= UUID=a82e38a0- 8d20-49dd- 9cbd-de7216b589 fc log_buf_len=16M usbhid. quirks= 0x0079: 0x0006: 0x100000 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 cgroup_ enable= memory swapaccount=1
The crash hasn't happened, but the Atomic update failure messages are still present and happening relatively often. Strange how the kernel from command 34 was fine until i915.enable_fbc=0 was set.
By the way, does the bisect from the duplicate make sense? I found the result strange, but it seemed to fix it to me.