Crashes in latest Debian development snapshot

Products Support Qualcomm RB5
#1

Hello,

I know it is not a release and I’m not expecting support, but I am curious about the status of the development snapshot for the RB5. I installed the latest snapshot to mine yesterday and have noticed that a lot of things are triggering Wayland crashes currently:

Launching Firefox or Chromium (Epiphany launches okay)
Launching gitk
Launching glxgears or Vulkan demos

Otherwise it is looking nice, seems to be running better than the current release and benchmarking well. Curious what the blockers are. These are the stack traces I’m getting on crash:

Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE)
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) Backtrace:
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 0: /usr/bin/Xwayland (0xaaaae7320000+0x16babc) [0xaaaae748babc]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 1: /usr/bin/Xwayland (0xaaaae7320000+0x16ec88) [0xaaaae748ec88]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 2: linux-vdso.so.1 (__kernel_rt_sigreturn+0x0) [0xffff8fd0c7a4]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 3: /usr/lib/aarch64-linux-gnu/dri/msm_dri.so (0xffff8d478000+0xb96be8) [0xffff8e00ebe8]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 4: /usr/lib/aarch64-linux-gnu/dri/msm_dri.so (0xffff8d478000+0xb24cc4) [0xffff8df9ccc4]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 5: /usr/lib/aarch64-linux-gnu/dri/msm_dri.so (0xffff8d478000+0xb33350) [0xffff8dfab350]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 6: /usr/lib/aarch64-linux-gnu/dri/msm_dri.so (0xffff8d478000+0x1f88b4) [0xffff8d6708b4]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 7: /usr/lib/aarch64-linux-gnu/dri/msm_dri.so (0xffff8d478000+0x1f8c68) [0xffff8d670c68]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 8: /usr/lib/aarch64-linux-gnu/dri/msm_dri.so (0xffff8d478000+0x1f8d38) [0xffff8d670d38]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 9: /usr/lib/aarch64-linux-gnu/libEGL_mesa.so.0 (0xffff8ecbc000+0x1d0b4) [0xffff8ecd90b4]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 10: /usr/lib/aarch64-linux-gnu/libEGL_mesa.so.0 (0xffff8ecbc000+0xb638) [0xffff8ecc7638]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 11: /usr/bin/Xwayland (0xaaaae7320000+0x45170) [0xaaaae7365170]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 12: /usr/bin/Xwayland (0xaaaae7320000+0x45950) [0xaaaae7365950]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 13: /usr/bin/Xwayland (0xaaaae7320000+0x9a644) [0xaaaae73ba644]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 14: /usr/bin/Xwayland (0xaaaae7320000+0x9f974) [0xaaaae73bf974]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 15: /usr/bin/Xwayland (0xaaaae7320000+0xa3a70) [0xaaaae73c3a70]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 16: /lib/aarch64-linux-gnu/libc.so.6 (__libc_start_main+0xe8) [0xffff8f5f38b8]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) 17: /usr/bin/Xwayland (0xaaaae7320000+0x38278) [0xaaaae7358278]
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE)
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) Segmentation fault at address 0x8
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE)
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: Fatal server error:
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE) Caught signal 11 (Segmentation fault). Server aborting
Dec 06 15:12:56 linaro-gnome org.gnome.Shell.desktop[944]: (EE)
Dec 06 15:12:57 linaro-gnome gnome-shell[837]: Connection to xwayland lost

#2

Oh, the crashes only happen when running Wayland. With X11 the apps will work. In the browsers I regularly get garbled/corrupted/twitchy/glitchy font glyphs though.

#3

If it helps, here is a proper trace with symbols from a core dump of Xwayland after launching glxgears:

Core was generated by `/usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth /run/user/1000/.mu’.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at …/sysdeps/unix/sysv/linux/raise.c:49
49 …/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
[Current thread is 1 (Thread 0xffffbb5e9010 (LWP 4357))]
(gdb) where
#0 __GI_raise (sig=sig@entry=6) at …/sysdeps/unix/sysv/linux/raise.c:49
#1 0x0000ffffbbe3c54c in __GI_abort () at abort.c:79
#2 0x0000aaaae6a2168c in OsAbort () at …/os/utils.c:1330
#3 0x0000aaaae6a26454 in AbortServer () at …/os/log.c:879
#4 0x0000aaaae6a273c8 in FatalError (f=f@entry=0xaaaae6a6cfa8 “Caught signal %d (%s). Server aborting\n”) at …/os/log.c:1017
#5 0x0000aaaae6a1ecf4 in OsSigHandler (unused=, sip=0xffffcfb1d410, signo=11) at …/os/osinit.c:156
#6 OsSigHandler (signo=11, sip=0xffffcfb1d410, unused=) at …/os/osinit.c:110
#7
#8 0x0000ffffba857be8 in list_delinit (item=) at …/src/util/list.h:103
#9 lookup_bo (key=, tbl=) at …/src/freedreno/drm/freedreno_bo.c:55
#10 fd_bo_from_dmabuf (dev=, fd=17) at …/src/freedreno/drm/freedreno_bo.c:185
#11 0x0000ffffba7e5cc4 in fd_screen_bo_from_handle (pscreen=pscreen@entry=0xaaab073b4d80, whandle=whandle@entry=0xffffcfb1e948)
at …/src/gallium/drivers/freedreno/freedreno_screen.c:890
#12 0x0000ffffba7f4350 in fd_resource_from_handle (pscreen=0xaaab073b4d80, tmpl=0xffffcfb1e898, handle=0xffffcfb1e948, usage=)
at …/src/gallium/drivers/freedreno/freedreno_resource.c:1329
#13 0x0000ffffb9eb98b4 in dri2_create_image_from_winsys (_screen=_screen@entry=0xaaab073a9de0, width=width@entry=16, height=height@entry=16,
map=, map@entry=0xffffbab6a67c <dri2_format_table+476>, num_handles=num_handles@entry=1, whandle=0xffffcfb1e948,
is_protected_content=is_protected_content@entry=false, loaderPrivate=loaderPrivate@entry=0x0) at …/src/gallium/frontends/dri/dri2.c:905
#14 0x0000ffffb9eb9c68 in dri2_create_image_from_fd (_screen=0xaaab073a9de0, width=16, height=16, fourcc=875713089, modifier=0, fds=0xffffcfb1eac8,
num_fds=1, strides=0xffffcfb1ead8, offsets=offsets@entry=0xffffcfb1eae8, protected_content=protected_content@entry=false,
error=error@entry=0xffffcfb1eac4, loaderPrivate=loaderPrivate@entry=0x0) at …/src/gallium/frontends/dri/dri2.c:1043
#15 0x0000ffffb9eb9d38 in dri2_from_dma_bufs2 (screen=, width=, height=, fourcc=,
modifier=, fds=, num_fds=, strides=, offsets=0xffffcfb1eae8,
yuv_color_space=__DRI_YUV_COLOR_SPACE_UNDEFINED, sample_range=__DRI_YUV_RANGE_UNDEFINED, horizontal_siting=__DRI_YUV_CHROMA_SITING_UNDEFINED,
vertical_siting=__DRI_YUV_CHROMA_SITING_UNDEFINED, error=0xffffcfb1eac4, loaderPrivate=0x0) at …/src/gallium/frontends/dri/dri2.c:1629
#16 0x0000ffffbb5220b4 in dri2_create_image_dma_buf (disp=0xaaab073d3290, ctx=, buffer=, attr_list=)
at …/src/egl/drivers/dri2/egl_dri2.c:2895
#17 0x0000ffffbb510638 in _eglCreateImageCommon (disp=0xaaab073d3290, ctx=0x0, target=12912, buffer=0x0, attr_list=0xffffcfb1ecc8)
at …/src/egl/main/eglapi.c:1744
#18 0x0000aaaae68f5170 in xwl_glamor_gbm_create_pixmap_for_bo (screen=screen@entry=0xaaab0731bdc0, bo=bo@entry=0xaaab07cd0d40, depth=depth@entry=32)
at …/hw/xwayland/xwayland-glamor-gbm.c:221
#19 0x0000aaaae68f5950 in xwl_glamor_gbm_create_pixmap (screen=0xaaab0731bdc0, width=16, height=16, depth=32, hint=0)
at …/hw/xwayland/xwayland-glamor-gbm.c:307
#20 0x0000aaaae694a644 in ProcCreatePixmap (client=0xaaab07bfa240) at …/dix/dispatch.c:1454
#21 0x0000aaaae694f974 in Dispatch () at …/dix/dispatch.c:496
#22 0x0000aaaae6953a70 in dix_main (argc=16, argv=0xffffcfb1f0c8, envp=) at …/dix/main.c:271
#23 0x0000ffffbbe3c8b8 in __libc_start_main (main=0xaaaae68e8220 , argc=16, argv=0xffffcfb1f0c8, init=, fini=,
rtld_fini=, stack_end=) at …/csu/libc-start.c:314
#24 0x0000aaaae68e8278 in _start ()

#4

I had my RB5 on the shelf for a while, but just got it plugged in and updated. Want to report that X11 is now stable without any visual artifacts. Wayland is working well too. Installed mesa-vulkan-drivers and compiled and ran some Vulkan examples successfully.

1 Like
#5

Hi! I wanted to know a few things about the graphic drivers since I would like to buy this board. Did you manage to update Mesa drivers? To which version? Do you have support for OpenGL 4.5 and Vulkan 1.3?

1 Like