<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [Vega10] GPU lockup on boot: VMC page fault" href="https://bugs.freedesktop.org/show_bug.cgi?id=105251#c41">Comment # 41</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [Vega10] GPU lockup on boot: VMC page fault" href="https://bugs.freedesktop.org/show_bug.cgi?id=105251">bug 105251</a> from <a class="email" href="mailto:mesa@suchmail.net" title="CheatCodesOfLife <mesa@suchmail.net>"> CheatCodesOfLife</a> <pre>(In reply to Andrey Grodzovsky from <a href="show_bug.cgi?id=105251#c40">comment #40</a>) > Marek Olšák, I still don't see the expected debug output. I looked for > 'Buffer list' > CheatCodesOfLife, can you verify please you are running the patched version > of MESA ? We tested yesterday the new prints and they do show on VM_FAULTs. This is most likely my fault as I'm new to most of this sort of thing. This is what I did, maybe you'll see where I went wrong: - Patch This is the patched version of src/gallium/drivers/radeonsi/si_gfx_cs.c <a href="http://termbin.com/ypet">http://termbin.com/ypet</a> - Build I installed this build of mesa to a different prefix, rather than overriding my system install (I use this computer for work, everything). System install: glxinfo |grep Mesa\ 18 OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.0-devel (git-e345247092) OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.3.0-devel (git-e345247092) OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.0-devel (git-e345247092) New build: OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.0-devel (git-a72dbc461b) OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.3.0-devel (git-a72dbc461b) OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.0-devel (git-a72dbc461b) - Running: I then ran Cemu like this: LD_LIBRARY_PATH=/home/paul/mesa_log/lib/ GALLIUM_HUD="fps" GALLIUM_DDEBUG=1000 wine64 Cemu.exe I know wine lets you do this because this is how we used to use a fork of mesa called 'mesa_mild' to get the required compatibility profile prior to mesa 18.2 which provided core compatibility 4.4 If installing to a prefix like that isn't adequate for this testing, let me know and I'll re-install the OS on an external drive, do a system-wide install of this patched mesa and try again.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>