[Bug 99887] Random segfault in intel driver in __kgem_busy() with Xorg 1.19.x

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99887

--- Comment #6 from Olivier Fourdan <fourdan at xfce.org> ---
Created attachment 129797
  --> https://bugs.freedesktop.org/attachment.cgi?id=129797&action=edit
valgrind log

Right, I suspect the intel driver is not the culprit but probably a victim of
another memory corruption that occurs earlier.

I just had a crash with a complete different backtrace that has nothing to do
with the intel driver:

#0  0x00000000071b491f in __GI_raise (sig=sig at entry=6) at
../sysdeps/unix/sysv/linux/raise.c:58
#1  0x00000000071b651a in __GI_abort () at abort.c:89
#2  0x00000000005a15ce in OsAbort () at utils.c:1355
#3  0x00000000005a7203 in AbortServer () at log.c:877
#4  0x00000000005a7fed in FatalError (f=f at entry=0x5d56f0 "Caught signal %d
(%s). Server aborting\n") at log.c:1015
#5  0x000000000059e86e in OsSigHandler (signo=11, sip=<optimized out>,
unused=<optimized out>) at osinit.c:154
#6  0x0000000006f725c0 in <signal handler called> () at /lib64/libpthread.so.0
#7  0x000000000059e1ec in WriteToClient (who=who at entry=0x972d060,
count=count at entry=32, __buf=__buf at entry=0xfff000810) at io.c:705
#8  0x0000000000445749 in ProcGetInputFocus (client=0x972d060) at events.c:4861
#9  0x0000000000437095 in Dispatch () at dispatch.c:479
#10 0x000000000043b018 in dix_main (argc=15, argv=0xfff0009f8, envp=<optimized
out>) at main.c:287
#11 0x000000000719f401 in __libc_start_main (main=
    0x424cc0 <main>, argc=15, argv=0xfff0009f8, init=<optimized out>,
fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0xfff0009e8)
    at ../csu/libc-start.c:289

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170221/e6346668/attachment-0001.html>