Comment #97 on issue 326995 by
mari...@gmail.com: Resizing browser
@piman: Thanks for the reply, good to know htat the syncing extension is
not strictly needed after all, I was not sure about that.
About the crashes, I think you're right once again: As Jasper explained on
IRC earlier, we have our own modifications (see [1]) on top of the ARM
driver we're using, which might be in the end reason behind those crashes.
Actually, without any further change to that driver (using it as it is from
the master branch), I've observed the following messages showing up in the
journal output when the X server crashes:
Nov 24 21:34:14 endless kernel: Mali<2>: Executor: Mali page fault
detected at 0x12f13240 from bus id 23 of type read on Mali_PP_MMU_Broadcast
Nov 24 21:34:14 endless kernel: Mali<2>: Mali group: Executing recovery
reset due to job failure
Nov 24 21:34:14 endless kernel: Mali<2>: Mali PP: Hard reset of core
Mali_PP0
Nov 24 21:34:14 endless kernel: Mali<2>: Mali PP: Hard reset of core
Mali_PP1Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE)
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE) Backtrace:
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE)
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE) Segmentation fault at
address 0xb3d86000
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE)
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: Fatal server error:
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE) Caught signal 11
(Segmentation fault). Server aborting
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE)
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE)
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: Please consult the The X.Org
Foundation support
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: at
http://wiki.x.org
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: for help.
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE) Please also check the
log file at "/dev/null" for additional information.
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE)
Nov 24 21:34:15 endless gdm-Xorg-:1[1455]: (EE) Server terminated with
error (1). Closing log file.
...which result in the X server crashing with the following backtrace:
(gdb) bt
#0 __libc_do_syscall () at
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
#1 0xb6a39f36 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
#2 0xb6a3ac3e in __GI_abort () at abort.c:89
#3 0xb6f545d2 in OsAbort () at ../../os/utils.c:1373
#4 0xb6e8e80c in ddxGiveUp (error=EXIT_NO_ERROR,
error@entry=EXIT_ERR_ABORT)
at ../../../../hw/xfree86/common/xf86Init.c:1101
#5 0xb6e8e890 in AbortDDX (error=error@entry=EXIT_ERR_ABORT) at
../../../../hw/xfree86/common/xf86Init.c:1145
#6 0xb6f57fac in AbortServer () at ../../os/log.c:784
#7 0xb6f586c2 in FatalError (f=0xb6f7fa58 "Caught signal %d (%s).
Server
aborting\n") at ../../os/log.c:925
#8 0xb6f5284a in OsSigHandler (signo=245838, sip=0xb6f7fa58,
unused=<optimized out>) at ../../os/osinit.c:147
#9 <signal handler called>
#10 0xb6c79534 in ?? () from /lib/arm-linux-gnueabihf/libpixman-1.so.0
#11 0xb3c70000 in ?? ()
#12 0xb3c70000 in ?? ()
If now I revert the patch from [2], then I can no longer get neither the
crashes in the X server nor those error messages in the journal, which
might suggest that the exchange path is broken somehow.
I'll discuss this tomorrow with my work mate Daniel to see if I can drop
more light on the issue, but so far it's indeed looking better. In the
meanwhile, please let me know if there's anything else you'd like me to
test and/or to change in the patch proposed in my previous comment.
Thanks again!
[1]
https://github.com/endlessm/xf86-video-armsoc
[2]
https://github.com/endlessm/xf86-video-armsoc/commit/c878da8fbf2e8bafde27a334513e244dc0b9ad36