GPU DRM failed in imx6qsabresd

rakesh3 — Thu, 01 Jun 2023 12:23:57 GMT

Hi team,

I am using the imx6qsabresd board with custom kernel based on imx-linux-hardknott 5.10 and using the yocto Dunfell version.

I am trying to run the Qt application and getting the segmentation fault. I am using the prebuild libs of imx-gpu-viv_6.4.3. I am using the below libs.

ibCLC.so
libGAL.so
libGLES_CL.so.1.1.0
libGLES_CM.so.1.1.0
libGLESv1_CL.so.1.1.0
libEGL.so.1.5.0
libGLESv1_CM.so.1.1.0
libGLESv2.so.2.0.0
libGLSLC.so
libGL.so.1.2.0
libOpenCL.so.1.2.0
libOpenVG.2d.so.1.1.0
libOpenVG.3d.so.1.1.0
libVDK.so.1.2.0
libVSC.so
libGLES_CL.so -> libGLES_CL.so.1.1.0
libGLES_CL.so.1 -> libGLES_CL.so.1.1.0
libGLES_CM.so -> libGLES_CM.so.1.1.0
libGLES_CM.so.1 -> libGLES_CM.so.1.1.0
libGLESv1_CL.so -> libGLESv1_CL.so.1.1.0
libGLESv1_CL.so.1 -> libGLESv1_CL.so.1.1.0
libGLESv1_CM.so -> libGLESv1_CM.so.1.1.0
libGLESv1_CM.so.1 -> libGLESv1_CM.so.1.1.0
libGLESv2.so -> libGLESv2.so.2.0.0
libGLESv2.so.2 -> libGLESv2.so.2.0.0
libGL.so -> libGL.so.1.2.0
libGL.so.1 -> libGL.so.1.2.0
libOpenCL.so -> libOpenCL.so.1.2.0
libOpenCL.so.1 -> libOpenCL.so.1.2.0
libOpenVG.so -> libOpenVG.3d.so.1.1.0
libOpenVG.so.1 -> libOpenVG.3d.so.1.1.0
libEGL.so -> libEGL.so.1.5.0
libEGL.so.1 -> libEGL.so.1.5.0
libVDK.so -> libVDK.so.1.2.0
libVDK.so.1 -> libVDK.so.1.2.0

I am using the X11 window display. I am suspecting the segmentation fault is coming because of Dri failure as i am getting in X11.0.org

VIVANTE(0): Backing store enabled
[ 73.718] (==) VIVANTE(0): DPMS enabled
[ 74.428] (EE) VIVANTE(0): [dri] VivDRIScreenInit failed because Drm can't be opened.
[ 74.460] (II) Initializing extension Generic Event Extension

(II) xfree86: Adding drm device (/dev/dri/card0)
[ 71.321] (II) no primary bus or device found
[ 71.322] falling back to /sys/devices/platform/soc/130000.gpu/drm/card0

In the backtrace in gdb I am getting the below error,

OThread 1 "panic" received signal SIGSEGV, Segmentation fault.
0xb6053908 in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0
(gdb) bt full
#0 0xb6053908 in pthread_mutex_lock () from /lib/arm-linux-gnueabihf/libpthread.so.0
No symbol table info available.
#1 0xb0c0f048 in wl_proxy_create_wrapper () from /lib/arm-linux-gnueabihf/libwayland-client.so.0
No symbol table info available.
#2 0xb0c5dd64 in ?? () from /lib/arm-linux-gnueabihf/libEGL.so.1
No symbol table info available.
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb)

Below is my imx-gpu-viv_6.4.3.bb file content.

SRC_URI = "file://${PN}-${PV}-armhf.tar.gz \
file://debian \
"

SRC_URI[sha256sum] = "4e50fb2f13205ce84062f3bb70ae0b8453f7525f8725355cce3f71d1ce550f82"

S = "${WORKDIR}/${PN}-${PV}-armhf"

PROVIDES = " \
libclc-imx6q \
libegl-imx6q \
libgal-imx6q \
libgles-imx6q \
libgles2-imx6q \
libgl-imx6q \
libglslc-imx6q \
libopencl-imx6q \
libopenvg-imx6q \
libvdk-imx6q \
libvivante-dri-imx6q \
libvsc-imx6q \
"

Does this bb file needs the DEPENDS_append_imxdrm = " libdrm " ??

Could you please suggest what package or configuration is missing which is causing this segmentation fault.

Attached the Xorg.0.log. Please have a look into log.

Regards,

Re: GPU DRM failed in imx6qsabresd

Harvey021 — Fri, 02 Jun 2023 08:47:53 GMT

Hi @rakesh3

As stated in other case. The way to build is correct, you can have a try.

and What I known is that, the display driver for iMX6 should be fb driver, not DRM driver.

Best regards

Harvey

Re: GPU DRM failed in imx6qsabresd

rakesh3 — Fri, 02 Jun 2023 09:17:13 GMT

Thanks for reply,

So what can we do in this case, if EGL are not being supported to X11 graphics?

How to run the Qt5 GUI application with X11 graphics without segmentation fault in kernel imx-linux-hardknott 5.10 kernel having GPU imx-gpu-viv_6.4.3?

Please suggest on this, have been struggling with this issue!

Regards,

topic GPU DRM failed in imx6qsabresd in i.MX Processors

GPU DRM failed in imx6qsabresd

Re: GPU DRM failed in imx6qsabresd

Re: GPU DRM failed in imx6qsabresd