0ad crashes desktop on kernel 5.15

[Mijzelf]

Since a few months starting 0ad will crash the desktop. The terminal switches back to textmode for a short while, and then back to graphical login. Journald doesn't log any cause, only the results:

Code: Select all

Feb 15 16:47:39 localhost.localdomain mgaapplet[3223]: Packages are up to date
Feb 15 17:32:43 localhost.localdomain xfce4-screensav[2605]: xfce4-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
Feb 15 17:32:43 localhost.localdomain pulseaudio[2710]: X connection to :0.0 broken (explicit kill or server shutdown).
Feb 15 17:32:44 localhost.localdomain systemd[2398]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE
Feb 15 17:32:44 localhost.localdomain systemd[2398]: pulseaudio.service: Failed with result 'exit-code'.

I started 0ad @17:32:42, or something like that.

When I start the laptop with an old kernel (5.10?) it works, but since a few days I only have 5.15 kernels in grub left. My laptop runs the xfce4 desktop, if that matters.

[sturmvogel]

Maybe tell as a little bit about your hardware with:

Code: Select all

inxi -GmCSM

Than maybe the content from /var/log/Xorg.0.log (this is the Xorg log from your last session). And also .xsession-errors from your home directory.

[Mijzelf]

Code: Select all

 inxi -GmCSM
System:    Host: localhost Kernel: 5.15.16-desktop-1.mga8 x86_64 bits: 64 Desktop: Xfce 4.16.0 Distro: Mageia 8 mga8
Machine:   Type: Laptop System: Hewlett-Packard product: HP EliteBook 820 G1 v: A3009DD10203 serial: <superuser required>
           Mobo: Hewlett-Packard model: 1991 v: KBC Version 15.59 serial: <superuser required> BIOS: Hewlett-Packard
           v: L71 Ver. 01.39 date: 09/26/2016
Memory:    RAM: total: 7.58 GiB used: 1.65 GiB (21.8%)
           RAM Report: permissions: Unable to run dmidecode. Root privileges required.
CPU:       Info: Dual Core model: Intel Core i5-4310U bits: 64 type: MT MCP L2 cache: 3 MiB
           Speed: 998 MHz min/max: 800/3000 MHz Core speeds (MHz): 1: 998 2: 998 3: 998 4: 998
Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics driver: i915 v: kernel
           Device-2: Cheng Uei Precision Industry (Foxlink) HP HD Webcam type: USB driver: uvcvideo
           Display: x11 server: Mageia X.org 1.20.14 driver: intel,v4l resolution: 1366x768~60Hz
           OpenGL: renderer: Mesa DRI Intel HD Graphics 4400 (HSW GT2) v: 4.5 Mesa 21.3.4


.xsession-errors.old is huge. I attached it. Xorg.0.log.old is smaller, attached it too.

[doktor5000]

Seems to be a problem with either DRI or mesa with the newer kernels, or maybe with the intel driver itself:

Code: Select all

[ 25781.069] (EE) event18 - PS/2 Generic Mouse: client bug: event processing lagging behind by 577ms, your system is too slow
[ 26408.766] (EE)
[ 26408.766] (EE) Backtrace:
[ 26408.784] (EE) 0: /usr/libexec/Xorg (OsSigHandler+0x25) [0x594a15]
[ 26408.785] (EE) 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7f5c93b81180]
[ 26408.797] (EE) 2: /usr/libexec/Xorg (damageSetWindowPixmap+0x14e) [0x51567e]
[ 26408.810] (EE) 3: /usr/libexec/Xorg (DRI2SetWindowPixmap+0x41) [0x560321]
[ 26408.825] (EE) 4: /usr/libexec/Xorg (present_set_tree_pixmap_visit+0x32) [0x5116f2]
[ 26408.838] (EE) 5: /usr/libexec/Xorg (TraverseTree+0x42) [0x466da2]
[ 26408.850] (EE) 6: /usr/libexec/Xorg (present_set_tree_pixmap+0x54) [0x511a64]
[ 26408.863] (EE) 7: /usr/libexec/Xorg (present_execute+0x369) [0x514179]
[ 26408.878] (EE) 8: /usr/libexec/Xorg (present_scmd_pixmap+0x3c9) [0x514639]
[ 26408.891] (EE) 9: /usr/libexec/Xorg (proc_present_pixmap+0x1a4) [0x513244]
[ 26408.903] (EE) 10: /usr/libexec/Xorg (Dispatch+0x2fb) [0x43d13b]
[ 26408.916] (EE) 11: /usr/libexec/Xorg (dix_main+0x364) [0x440f94]
[ 26408.919] (EE) 12: /lib64/libc.so.6 (__libc_start_main+0xea) [0x7f5c939cae2a]
[ 26408.932] (EE) 13: /usr/libexec/Xorg (_start+0x2a) [0x42b51a]
[ 26408.932] (EE)
[ 26408.932] (EE) Segmentation fault at address 0x20
[ 26408.932] (EE)
Fatal server error:
[ 26408.932] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 26408.932] (EE)
[ 26408.932] (EE)
Please consult the Mageia support
    at https://bugs.mageia.org
 for help.
[ 26408.932] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 26408.932] (EE)
[ 26408.933] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 26409.046] (EE) Server terminated with error (1). Closing log file.

If you have any other application which requires OpenGL and/or hardware acceleration and which runs fine, then I'd suggest to report this as a bug against X server: https://wiki.mageia.org/en/How_to_report_a_bug_properly

[Mijzelf]

If you have any other application which requires OpenGL and/or hardware acceleration and which runs fine, then I'd suggest to report this as a bug against X server: https://wiki.mageia.org/en/How_to_report_a_bug_properly

Is there a way to know if an application meets that requirements? The examples on https://threejs.org/examples/#webgl_animation_keyframes work fine (in Firefox). I *think* it uses hardware acceleration, seeing my processor load. But how to know?

[doktor5000]

Best post the output of

Code: Select all

glxinfo

as regular user

[morgano]

Also, any change after todays updates of kernel, mesa, microcode?

[Mijzelf]

@doktor5000: Output of glxinfo attached.

@morgano: Unfortunately not. After upgrading&rebooting the problem was still there.