Various crashes in QEMU guests, apparently related to glibc 2.23

krabat · 2016-02-28 00:23:53

Since a couple of days several applications reproducibly crash and dump core in QEMU guests, both guests and host Arch Linux, apparently due to glibc 2.23.

Using its own modesetting driver the X server crashes upon launch. Using the QXL driver compiled in the guest system the X server starts but crashes upon exit.
Each and every Qt 5 GUI, be it the LXQt panel, some tiny dialogue window like lxqt-about or lxqt-leave of LXQt or a full-blown application like QupZilla crashes upon exit. Qt 4 applications don't seem to crash on exit in general, but e. g. VLC crashes when playback of a video gets stopped.

GTK applications aren't affected at all, neither is the host system which is configured the same way except the differences due to hardware.
Downgrading glibc to 2.22 fixes all the issues, even when the QXL driver compiled among other against glibc 2.23 is kept.

A web search didn't yield any result so I tend to believe it's some packaging issue like the need to rebuild some components against the new glibc. Rebuilding pkgbase xorg-server and qt5 did not fix the issue, though.

So any hint how to track this down further would be much appreciated.

Sample traces from crashes of the X server:
Stack trace as found in systemd journal

Process 2608 (Xorg) of user 1002 dumped core.

Stack trace of thread 2608:
#0  0x00007f1b4f2552a8 raise (libc.so.6)
#1  0x00007f1b4f25672a abort (libc.so.6)
#2  0x000000000059b23e OsAbort (Xorg)
#3  0x00000000004792fc ddxGiveUp (Xorg)
#4  0x00000000005a0eb2 n/a (Xorg)
#5  0x00000000005a1ced FatalError (Xorg)
#6  0x0000000000598ade n/a (Xorg)
#7  0x00007f1b4f255330 __restore_rt (libc.so.6)
#8  0x00007f1b4f012c19 pthread_barrier_destroy (libpthread.so.0)
#9  0x00007f1b48d7396f n/a (kms_swrast_dri.so)
#10 0x00007f1b48d7f441 n/a (kms_swrast_dri.so)
#11 0x00007f1b48a1e54f n/a (kms_swrast_dri.so) 
#12 0x00007f1b48a1e5f5 n/a (kms_swrast_dri.so) 
#13 0x00007f1b48a1ca2f n/a (kms_swrast_dri.so)
#14 0x00007f1b49d030aa n/a (libgbm.so.1)
#15 0x00007f1b49f14dd5 n/a (libglamoregl.so)
#16 0x00007f1b49f160ea glamor_egl_init (libglamoregl.so)
#17 0x00007f1b4a14c363 n/a (modesetting_drv.so)
#18 0x000000000047b10b InitOutput (Xorg)
#19 0x000000000043a094 n/a (Xorg)
#20 0x00007f1b4f242710 __libc_start_main (libc.so.6)
#21 0x0000000000424649 _start (Xorg)

Backtrace from gdb after importing the coredump via coredumpctl

#0  0x00007f1b4f2552a8 in raise () from /usr/lib/libc.so.6
#1  0x00007f1b4f25672a in abort () from /usr/lib/libc.so.6
#2  0x000000000059b23e in OsAbort ()
#3  0x00000000004792fc in ddxGiveUp ()
#4  0x00000000005a0eb2 in ?? ()
#5  0x00000000005a1ced in FatalError ()
#6  0x0000000000598ade in ?? ()
#7  <signal handler called>
#8  0x00007f1b4f012c19 in pthread_barrier_destroy () from /usr/lib/libpthread.so.0
#9  0x00007f1b48d7396f in ?? () from /usr/lib/xorg/modules/dri/kms_swrast_dri.so
#10 0x00007f1b48d7f441 in ?? () from /usr/lib/xorg/modules/dri/kms_swrast_dri.so
#11 0x00007f1b48a1e54f in ?? () from /usr/lib/xorg/modules/dri/kms_swrast_dri.so
#12 0x00007f1b48a1e5f5 in ?? () from /usr/lib/xorg/modules/dri/kms_swrast_dri.so
#13 0x00007f1b48a1ca2f in ?? () from /usr/lib/xorg/modules/dri/kms_swrast_dri.so
#14 0x00007f1b49d030aa in ?? () from /usr/lib/libgbm.so.1
#15 0x00007f1b49f14dd5 in ?? () from /usr/lib/xorg/modules/libglamoregl.so
#16 0x00007f1b49f160ea in glamor_egl_init () from /usr/lib/xorg/modules/libglamoregl.so
#17 0x00007f1b4a14c363 in ?? () from /usr/lib/xorg/modules/drivers/modesetting_drv.so
#18 0x000000000047b10b in InitOutput ()
#19 0x000000000043a094 in ?? ()
#20 0x00007f1b4f242710 in __libc_start_main () from /usr/lib/libc.so.6
#21 0x0000000000424649 in _start ()

jasonwryan · 2016-02-28 00:28:44

See https://bbs.archlinux.org/viewtopic.php?id=209340

krabat · 2016-02-28 01:08:05

Besides the traces which I can't judge in detail look somewhat similar I'm actually pretty sure that https://bbs.archlinux.org/viewtopic.php?id=209340 is a different issue.
Starting or stopping the X server, stopping (!) the playback of a local video file or those tiny dialogue windows will hardly involve any network traffic. Browsing using QupZilla or Firefox on the other hand works flawlessly.

Last edited by krabat (2016-02-28 01:29:46)

Arch Linux

#1 2016-02-28 00:23:53

Various crashes in QEMU guests, apparently related to glibc 2.23

#2 2016-02-28 00:28:44

Re: Various crashes in QEMU guests, apparently related to glibc 2.23

#3 2016-02-28 01:08:05

Re: Various crashes in QEMU guests, apparently related to glibc 2.23

Board footer