<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - PRIME/Hybrid graphics render offload issues with gen7" href="https://bugs.freedesktop.org/show_bug.cgi?id=77094#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED --- - PRIME/Hybrid graphics render offload issues with gen7" href="https://bugs.freedesktop.org/show_bug.cgi?id=77094">bug 77094</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to <a href="show_bug.cgi?id=77094#c9">comment #9</a>) > I will experiment with a couple of different versions of the software to see > if I can mitigate the X crash or such, or see if I can get another error > state dump. Assuming those are unfruitful, you're thinking this might be an > X bug (or perhaps one of the DDX's particularly)? I will try removing all > of the X clients from the picture as well by using startx or such. The crash looks like a core Xserver bug, but it could be one of the DDXs feeding in garbage. Double checking with an older Xserver seems reasonable. > It looks like that particular set of logs/dumps is from 13.14-rc7 with the > mainline builds for DRM/Mesa3D. As well, would someone be able to set me > straight on which repository is building which half (or third?) of the DRI > code? That would be much appreciated as I can't seem to remember it > straight. <a href="http://cgit.freedesktop.org/mesa/mesa/">http://cgit.freedesktop.org/mesa/mesa/</a> > As well, any ideas as to why Xorg would be blatantly ignoring my > LIBGL_DRIVERS_PATH (tried set to both /usr/local/x86_64-linux-gnu/lib and > /usr/local/x86_64-linux-gnu/lib/dri; Xorg loads "intel" module properly (as > I've setup the module path in config), but after that the DRI from > /usr/lib/x86_64-linux-gnu/dri is loaded by Xorg, while all other processes > seem to get the right one from /usr/local. The intel module in /usr/local > is properly built by the build system with > DRI_DRIVER_PATH=/usr/local/x86_64-linux-gnu/lib/dri, and I am then at a > loss. This happens even when I run Xorg as my user from a shell. X is a setuid root binary - it has to be very careful what environment variables it uses (basically it can't trust any of them). The path X uses to load its DRI interface is determined at compile time by `$PKG_CONFIG --variable=dridriverdir dri`</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>