<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - intermittent unit test crashes since mesa 17.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=104778#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - intermittent unit test crashes since mesa 17.2" href="https://bugs.freedesktop.org/show_bug.cgi?id=104778">bug 104778</a> from <a class="email" href="mailto:lionel.g.landwerlin@linux.intel.com" title="Lionel Landwerlin <lionel.g.landwerlin@linux.intel.com>"> Lionel Landwerlin</a> <pre>(In reply to Mark Janes from <a href="show_bug.cgi?id=104778#c22">comment #22</a>) > Hmm...`cp` in xterm is a pretty clear indicator that this issue is random > and not triggered by a specific workload. > > Lionel suggested that it would be good to have a feedback from the kernel > about what didn't pass validation. > > There is a kernel option to generate debug traces for that but you have to > recompile your kernel with that option. Lionel, can you provide some > details? > > It would be a good data point to see if a much older kernel produces this > error (eg 4.9, 4.4). I can't deploy those kernels in Mesa i965 CI because > they lack features needed to run our Vulkan test suites. With the kernel compiled with CONFIG_DRM_I915_DEBUG_GEM and the following command issued as root : echo 15 > /sys/module/drm/parameters/debug You should be able to get some traces about why the execbuffer failed. Unfortunately that generates a lot of traces...</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>