You are not logged in.

#1 2023-12-31 18:08:07

maboleth
Member
Registered: 2020-01-03
Posts: 220

[solved] eglinfo gives seg. fault on device 1

My PC machine is

Operating System: Arch Linux 
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
Kernel Version: 6.6.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor
Memory: 31.3 GiB of RAM
Graphics Processor: AMD Radeon RX 6650 XT
Manufacturer: Micro-Star International Co., Ltd
Product Name: MS-7C02
System Version: 1.0

When trying eglinfo -b it gives

GBM platform:
eglinfo: eglInitialize failed

Wayland platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

X11 platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Surfaceless platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device platform:
Device #0:

Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES 
OpenGL core profile vendor: AMD
OpenGL core profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL core profile version: 4.6 (Core Profile) Mesa 23.3.2-arch1.1
OpenGL core profile shading language version: 4.60
OpenGL compatibility profile vendor: AMD
OpenGL compatibility profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL compatibility profile version: 4.6 (Compatibility Profile) Mesa 23.3.2-arch1.1
OpenGL compatibility profile shading language version: 4.60
OpenGL ES profile vendor: AMD
OpenGL ES profile renderer: AMD Radeon RX 6650 XT (radeonsi, navi23, LLVM 16.0.6, DRM 3.54, 6.6.8-arch1-1)
OpenGL ES profile version: OpenGL ES 3.2 Mesa 23.3.2-arch1.1
OpenGL ES profile shading language version: OpenGL ES GLSL ES 3.20

Device #1:

Platform Device platform:
Segmentation fault (core dumped)

What's interesting, on my newest laptop that has totally different hardware - though still AMD processor (with builtin GPU) - displays the same seg. fault message.
Using open source AMD drivers. I'm not sure what is device 1 though? And why I have both 0 and 1 devices on PC and Laptop...

Last edited by maboleth (2024-01-02 19:30:29)

Offline

#2 2023-12-31 18:39:06

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,908

Re: [solved] eglinfo gives seg. fault on device 1

Probably lol, simpledrm. Try adding "initcall_blacklist=simpledrm_platform_driver_init" to your kernel parameters and rebooting and reproducing.

Online

#3 2023-12-31 19:33:32

maboleth
Member
Registered: 2020-01-03
Posts: 220

Re: [solved] eglinfo gives seg. fault on device 1

options root=PARTUUID=d3f06140-5867-4774-94b3-1403391637bf zswap.enabled=0 rw rootfstype=ext4 initcall_blacklist=simpledrm_platform_driver_init quiet splash

Is this the correct way for systemd?
If it is, it doesn't work. Not only I don't have plymouth splash screen, but when I enter eglinfo, it fails on agp mesa driver.

Offline

#4 2023-12-31 20:01:24

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,771
Website

Re: [solved] eglinfo gives seg. fault on device 1

maboleth wrote:

Is this the correct way for systemd?

It looks correct, check it has been applied with

cat /proc/cmdline

FWIW I see a similar error on my laptop but with Device #2. I only have 2 cards though (Rembrandt & Navi 33).

Everything works for me, I've been playing games all day. Is anything apart from eglinfo actually broken on your system?

Offline

#5 2023-12-31 20:43:46

maboleth
Member
Registered: 2020-01-03
Posts: 220

Re: [solved] eglinfo gives seg. fault on device 1

Head_on_a_Stick wrote:

Everything works for me, I've been playing games all day. Is anything apart from eglinfo actually broken on your system?

Actually no, it's just 'cosmetic' so to speak.

I was installing Arch and setting up a new laptop for my father and when I wanted to check all specs in KDE I noticed this error/crash.

I then tried the same on my PC and got identical results. So I was curious. But not worth the hassle as it seems, it's something trivial.

Offline

#6 2023-12-31 20:52:21

seth
Member
Registered: 2012-09-03
Posts: 52,338

Re: [solved] eglinfo gives seg. fault on device 1

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Offline

#7 2024-01-01 00:22:52

maboleth
Member
Registered: 2020-01-03
Posts: 220

Re: [solved] eglinfo gives seg. fault on device 1

seth wrote:

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Alright
http://0x0.st/HEF1.txt

Offline

#8 2024-01-01 09:27:50

seth
Member
Registered: 2012-09-03
Posts: 52,338

Re: [solved] eglinfo gives seg. fault on device 1

plymouth is late because the amdgpu module loads late, https://wiki.archlinux.org/title/Kernel … _KMS_start
But simpledrm is indeed blocked.

when I enter eglinfo, it fails on agp mesa driver

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855 - post the actual eglinfo output.
Also check "eglinfo -B" and in doubt https://wiki.archlinux.org/title/Core_d … _core_dump

There're other issues w/ mesa 23.3.2, but those relate to (very most likely) the simpledrm device interfering on nvidia systems, screwing up the modesettign driver.

Offline

#9 2024-01-01 11:34:19

maboleth
Member
Registered: 2020-01-03
Posts: 220

Re: [solved] eglinfo gives seg. fault on device 1

seth wrote:

plymouth is late because the amdgpu module loads late, https://wiki.archlinux.org/title/Kernel … _KMS_start
But simpledrm is indeed blocked.

That reminded me, when I was using XFCE on Manjaro, it occasionally failed to boot to desktop, the screen was black. It was indeed amdgpu module loading late so having it listed in mkinitcpio fixed it.
Don't have that problem in KDE though.

Offline

#10 2024-01-01 19:45:05

tekstryder
Member
Registered: 2013-02-14
Posts: 139

Re: [solved] eglinfo gives seg. fault on device 1

eglinfo no longer segfaults here with mesa 23.3.2-2

https://gitlab.archlinux.org/archlinux/ … 1108361f65

This is an nvidia/wayland setup, no X11 or XWayland.

I didn't bother adding noise to all the existing recent mesa probs threads, but what got me interested was one I've not seen others mention...

Nautilus search was intermittently crashing after the upgrade to mesa 23.3.2-1 with:

Jan 01 14:31:14 gnome-shell[1533]: WL: error in client communication (pid 3695)
Jan 01 14:31:14 nautilus[3695]: Error 71 (Protocol error) dispatching to Wayland display.

EDIT: this issue is also resolved with mesa 23.3.2-2.

And, for thread completeness, though debug symbols are not all provided, the dump from eglinfo -B with mesa 23.3.2-1...

Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000000600000005 in ?? ()
(gdb) bt full
#0  0x0000000600000005 in ?? ()
No symbol table info available.
#1  0x00007f8ca5ccbbbf in ?? () from /usr/lib/dri/swrast_dri.so
No symbol table info available.
#2  0x00007f8ca56c6a90 in ?? () from /usr/lib/dri/swrast_dri.so
No symbol table info available.
#3  0x00007f8ca56c6dde in ?? () from /usr/lib/dri/swrast_dri.so
No symbol table info available.
#4  0x00007f8ca56c76b5 in ?? () from /usr/lib/dri/swrast_dri.so
No symbol table info available.
#5  0x00007f8cb98e8df6 in ?? () from /usr/lib/libEGL_mesa.so.0
No symbol table info available.
#6  0x00007f8cb98edf08 in ?? () from /usr/lib/libEGL_mesa.so.0
No symbol table info available.
#7  0x00007f8cb98db271 in ?? () from /usr/lib/libEGL_mesa.so.0
No symbol table info available.
#8  0x000055a86509ff7f in doOneDisplay (d=0x55a865ee57d0, name=name@entry=0x55a8650bc5a5 "Platform Device", opts=...) at ../mesa-demos-9.0.0/src/egl/opengl/eglinfo.c:529
        maj = 0
        min = 0
        client_apis = <optimized out>
        display_exts = <optimized out>
        khr_create_context = <optimized out>
        has_opengl = <optimized out>
        has_opengl_es = <optimized out>
        has_openvg = <optimized out>
        do_opengl_core = <optimized out>
        do_opengl_compat = <optimized out>
        do_opengl_es = <optimized out>
        version = 32652
#9  0x000055a86509864b in doOneDevice (opts=..., i=<optimized out>, d=0x7f8cb9917020) at ../mesa-demos-9.0.0/src/egl/opengl/eglinfo.c:647
        getPlatformDisplay = 0x7f8cba1c9f70 <eglGetPlatformDisplayEXT>
#10 doDevices (name=0x55a8650bc551 "Device platform", opts=...) at ../mesa-demos-9.0.0/src/egl/opengl/eglinfo.c:673
        devices = 0x55a865eaa650
        i = <optimized out>
        ret = 1
        queryDevices = <optimized out>
        max_devices = 3
        num_devices = 3
        queryDevices = <optimized out>
        devices = <optimized out>
        max_devices = <optimized out>
        num_devices = <optimized out>
        i = <optimized out>
        ret = <optimized out>
#11 main (argc=<optimized out>, argv=<optimized out>) at ../mesa-demos-9.0.0/src/egl/opengl/eglinfo.c:859
        getPlatformDisplay = <optimized out>
        opts = {platform = <optimized out>, api = 4294967295, mode = <optimized out>, single_line = 0, limits = 0}
        ret = 1
        clientext = <optimized out>

Last edited by tekstryder (2024-01-01 19:48:12)

Offline

#11 2024-01-01 19:50:45

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,771
Website

Re: [solved] eglinfo gives seg. fault on device 1

eglinfo is also fixed for me with mesa v1:23.3.2-2.

Offline

#12 2024-01-01 19:52:39

tekstryder
Member
Registered: 2013-02-14
Posts: 139

Re: [solved] eglinfo gives seg. fault on device 1

Oh, I forgot to include the upstream mesa bug report:

https://gitlab.freedesktop.org/mesa/mesa/-/issues/10371

Offline

#13 2024-01-01 21:26:26

seth
Member
Registered: 2012-09-03
Posts: 52,338

Re: [solved] eglinfo gives seg. fault on device 1

@tekstryder, ok, but why does it load the swrast driver at all?
Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Though HoaS is proabably on AMDGPU as well, maybe eglinfo just loads all drivers unconditionally and ran into swrast this way hmm

Offline

#14 2024-01-01 21:42:17

tekstryder
Member
Registered: 2013-02-14
Posts: 139

Re: [solved] eglinfo gives seg. fault on device 1

seth wrote:

@tekstryder, ok, but why does it load the swrast driver at all?

seth answered his own question wrote:

maybe eglinfo just loads all drivers unconditionally and ran into swrast this way hmm

This wink

You can specify your platform thusly if you want to be specific. E.g.:

$ eglinfo -p wayland

Last edited by tekstryder (2024-01-01 21:45:46)

Offline

#15 2024-01-01 21:44:15

seth
Member
Registered: 2012-09-03
Posts: 52,338

Re: [solved] eglinfo gives seg. fault on device 1

Yup, could have straced that before clicking submit wink

Offline

#16 2024-01-01 21:46:43

tekstryder
Member
Registered: 2013-02-14
Posts: 139

Re: [solved] eglinfo gives seg. fault on device 1

seth wrote:

Yup, could have straced that before clicking submit wink

You beat my edit, but I added more constructive, less snarky.

Offline

#17 2024-01-01 23:05:07

maboleth
Member
Registered: 2020-01-03
Posts: 220

Re: [solved] eglinfo gives seg. fault on device 1

Yeah works for me with this update too. Seems like I just should have waited 1 more day. :`)

Offline

Board footer

Powered by FluxBB