<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [sna] Random X-Server crashes and freezes after update" href="https://bugs.freedesktop.org/show_bug.cgi?id=93848#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [sna] Random X-Server crashes and freezes after update" href="https://bugs.freedesktop.org/show_bug.cgi?id=93848">bug 93848</a> from <a class="email" href="mailto:gentoo@gishpuppy.com" title="M. G. <gentoo@gishpuppy.com>"> M. G.</a> <pre>Created <a href="attachment.cgi?id=121747" name="attach_121747" title="Xorg log from freeze">attachment 121747</a> <a href="attachment.cgi?id=121747&action=edit" title="Xorg log from freeze">[details]</a> Xorg log from freeze Today I had another freeze (I think valgrind prevented the X server from crashing, memcheck-amd64-linux uses 100% CPU since a few hours). I have attached the Xorg log. The valgrind log contains nothing special, just the following messages I see everytime: ==2547== Memcheck, a memory error detector ==2547== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al. ==2547== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info ==2547== Command: /usr/bin/X.valgrind-testing :0 vt07 -nolisten tcp ==2547== Parent PID: 2543 ==2547== ==2547== Warning: noted but unhandled ioctl 0x4b51 with no size/direction hints. ==2547== This could cause spurious value errors to appear. ==2547== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. **2547** SNA compiled for use with valgrind **2547** SNA compiled for use with valgrind ==2547== Warning: noted but unhandled ioctl 0x6458 with no size/direction hints. ==2547== This could cause spurious value errors to appear. ==2547== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==2547== Warning: noted but unhandled ioctl 0x641e with no size/direction hints. ==2547== This could cause spurious value errors to appear. ==2547== See README_MISSING_SYSCALL_OR_IOCTL for guidance on writing a proper wrapper. ==2547== Syscall param writev(vector[...]) points to uninitialised byte(s) ==2547== at 0x676C6F0: __writev_nocancel (syscall-template.S:81) ==2547== by 0x59011B: _XSERVTransSocketWritev (Xtranssock.c:2367) ==2547== by 0x58B24C: FlushClient (io.c:941) ==2547== by 0x58B97D: WriteToClient (io.c:856) ==2547== by 0x4F8734: rrGetScreenResources (rrscreen.c:627) ==2547== by 0x437136: Dispatch (dispatch.c:429) ==2547== by 0x43B23A: dix_main (main.c:298) ==2547== by 0x66AC7AF: (below main) (libc-start.c:289) ==2547== Address 0xdba6df7 is 615 bytes inside a block of size 616 alloc'd ==2547== at 0x4C29F60: malloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==2547== by 0x4F8C8B: rrGetScreenResources (rrscreen.c:551) ==2547== by 0x437136: Dispatch (dispatch.c:429) ==2547== by 0x43B23A: dix_main (main.c:298) ==2547== by 0x66AC7AF: (below main) (libc-start.c:289) ==2547== I will also attach two valgrind logs from previous runs that contain some invalid read and conditional jump or move depends on uninitialised value(s) messages. Not sure if this helps. PS: I have built the Intel driver based on commit 8b8c9a36828e90e46ad0755c6861df85f5307fb5.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>