Thanks for forwarding Bernhard.
TJ, the problem is gone for me. It was either due to upgrading the RAM size or
a subsequent kernel update.
Haven't had the problem in months and I'm currently running
linux-image-5.19.0-2-amd64.
I think you can close this issue.
Forwarding, as the email from TJ possibly did not reach Felix.
On Fri, 21 Oct 2022 11:43:07 +0100 TJ wrote:
On Sat, 12 Feb 2022 08:21:55 + Felix Leimbach wrote:
> I noticed that vgamem_mb was still low (32 MB).
> So I changed to this (slightly wasteful) command-line and am now running
On Sat, 12 Feb 2022 08:21:55 + Felix Leimbach wrote:
I noticed that vgamem_mb was still low (32 MB).
So I changed to this (slightly wasteful) command-line and am now running the
latest kernel (5.15.0-3-amd64):
-vga none -device
I noticed that vgamem_mb was still low (32 MB).
So I changed to this (slightly wasteful) command-line and am now running the
latest kernel (5.15.0-3-amd64):
-vga none -device
qxl-vga,ram_size_mb=256,vgamem_mb=256,vram_size_mb=256,vram64_size_mb=256,max_outputs=1
Will report back if that helps.
Thanks for looking into this Bernhard!
I found the problem vanishes if I downgrade my kernel from 5.15.0-2 to
5.10.0-10.
So it seems to be a regression on the kernel side.
Yes, it is a virtual qemu/kvm machine. I increased the VRAM years ago, when I
experimented with spice's h264 acceleration.
Package: xserver-xorg-video-qxl
Version: 0.1.5+git20200331-1
Severity: grave
Justification: Xorg randomly crashes (all unsaved work lost)
Kernel:
---
Happens with latest 5.15.5-2
Testing older versions right now, will report if they solve the issue
Contents of Xorg X server log file after a
6 matches
Mail list logo