<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - radeonsi: 3D engines causing frequent GPU lockups" href="https://bugs.freedesktop.org/show_bug.cgi?id=101672#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - radeonsi: 3D engines causing frequent GPU lockups" href="https://bugs.freedesktop.org/show_bug.cgi?id=101672">bug 101672</a> from <a class="email" href="mailto:sonichedgehog_hyperblast00@yahoo.com" title="MirceaKitsune <sonichedgehog_hyperblast00@yahoo.com>"> MirceaKitsune</a> <pre>Created <a href="attachment.cgi?id=132863" name="attach_132863" title="Screenshot of sys/kernel/debug/dri/0">attachment 132863</a> <a href="attachment.cgi?id=132863&action=edit" title="Screenshot of sys/kernel/debug/dri/0">[details]</a> Screenshot of sys/kernel/debug/dri/0 The exact same story repeats with Mesa 17.1.5 (as with 17.1.4); The release notes claim that a core crash has been fixed, yet inexplicably this freeze persists after updating to the latest version. Something very unusual happened however: I rebooted my machine and started testing under Xonotic. After about 10 minutes of playing I got my first freeze, however it did not block the machine; Only Xonotic itself crashed (image froze and sound died), so I was able to alt-tab switch to my desktop... the system detected that the process was unresponsive and killed it, after which I could notice that it did NOT eat up any CPU or memory while it was frozen. I tested again and after about 15 minutes I got another freeze... this time though it froze the entire computer as usual (including taking down SSH). I preformed the suggested test of monitoring the files in sys/kernel/debug/dri/0 through my SSH connection, to check whether this might be caused by a vram leak. The most relevant file in there was radeon_vram, which seems to have 2.0 GB at all times (makes sense as that's the amount of vram on my video card). I used the command "watch -n 1 cat /sys/kernel/debug/dri/0/radeon_vram" to monitor it, but that has not printed any changes in the file itself. Adding a screenshot of that directory and its contents.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>