FS#74276 - [mesa] kodi fails to start via systemd service due to segfault in crocus_dri.so
Attached to Project:
Arch Linux
Opened by John (graysky) - Wednesday, 30 March 2022, 09:41 GMT
Last edited by David Thurstenson (thurstylark) - Sunday, 10 April 2022, 04:36 GMT
Opened by John (graysky) - Wednesday, 30 March 2022, 09:41 GMT
Last edited by David Thurstenson (thurstylark) - Sunday, 10 April 2022, 04:36 GMT
|
Details
I am running kodi-x11 starting it via a systemd service
using kodi-standalone-service:
https://github.com/graysky2/kodi-standalone-service
Upon updating to mesa-22.0.0-1, the service fails to start. Downgrading to mesa-21.3.7-2 fixes the problem/kodi runs as expected. When I inspect the output of journalctl (attached as journalctl.log) it seems that first segfault occurs in crocus_dri.so (line 45), and then the core dumps start from there: ... kodi-x11[8934]: segfault at 2a0 ip 00007f4ddd1c208b sp 00007fff13bfa890 error 4 in crocus_dri.so[7f4ddc0df000+118d000] kernel: Code: 78 20 0a 74 c1 c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 49 89 cb 89 d3 48 8d 0d bb 4e 51 00 41 8d 50 d8 48 89 f8 49 89 f2 <8b> 3f 48 63 14 91 48 01 ca 3e ff e2 be 00 04 00 00 0f 1f 40 00 39 systemd[1]: Started Process Core Dump (PID 8950/UID 0). systemd-coredump[8951]: Process 8934 (kodi-x11) of user 989 dumped core. ... When I inspect the output of a kodi debug log (attached as kodi_crashlog-20220330_051325.log), I did not see anything that looked like it was a root cause, rather, the log just seems to stop getting written to perhaps caused by the segfaults reported in journalctl. |
kodi_crashlog-20220330_053204...
This task depends upon
Closed by David Thurstenson (thurstylark)
Sunday, 10 April 2022, 04:36 GMT
Reason for closing: Not a bug
Sunday, 10 April 2022, 04:36 GMT
Reason for closing: Not a bug
Does anyone know where I can find the "amber" branch where i915 support has be migrated? I did not find one here: https://cgit.freedesktop.org/mesa/mesa/
?
Crash on kodi startup LXQt DE:
kernel: kodi.bin[1508]: segfault at 2a0 ip 00007f2fa66e108b sp 00007ffe4f123800 error 4 in crocus_dri.so[7f2fa55fe000+118d000]
kernel: Code: 78 20 0a 74 c1 c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 53 49 89 cb 89 d3 48 8d 0d bb 4e 51 00 41 8d 50 d8 48 89 f8 49 89 f2 <8b> 3f 48 63 14 91 48 01 ca 3e ff e2 be 00 04 00 00 0f 1f 40 00 39
Downgrading mesa (22.0.0-1 -> 21.3.7-1) and kodi (19.4-2 -> 19.3-6) solves it for the moment.
vainfo also fails with 'error driver name =(NULL)'
Manually setting driver name 'export LIBVA_DRIVER_NAME=i965' vainfo still fails with 'unknown error'
Mesa 22 release note explicitlely state:
Mesa 22.0.0 is a new development release.
People who are concerned with stability and reliability should stick with a previous release or wait for Mesa 22.0.1.
Perhaps mesa 22 should still belong to the testing-repo
ADDENUM:
Issue persists with latest mesa 22.0.1-3
OS: Arch Linux x86_64
Host: XS35V4 V1.0
Kernel: 5.17.1-arch1-1
CPU: Intel Celeron J1900 (4) @ 2.415GHz
GPU: Intel Atom Processor Z36xxx/Z37xxx Series Graphics & Display
I posted on the forum : https://bbs.archlinux.org/viewtopic.php?id=275402