<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - AMDGPU - Can't even get Xorg to start - Kernel driver hangs with ring buffer timeout on ARM64" href="https://bugs.freedesktop.org/show_bug.cgi?id=108625#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - AMDGPU - Can't even get Xorg to start - Kernel driver hangs with ring buffer timeout on ARM64" href="https://bugs.freedesktop.org/show_bug.cgi?id=108625">bug 108625</a> from <a class="email" href="mailto:raster@rasterman.com" title="Carsten Haitzler <raster@rasterman.com>"> Carsten Haitzler</a> <pre>so wouldn't that make it a necessity then if its even glamor needing it? i guess i can turn off glamor accel but realistically gl is a necessity so the problem needs to be addressed sooner or later. the ring gfx timeout smells to me of "not a mesa bug" in that an ioctl going to the drm driver never returns qhen doing a simple query. it hangs, thus something lower down that is having a bad day, if something as simple as querying a fence causes a hang... :) what is this ring gfx thing exactly (seems to be some command queue) and why would it be timing out? all the way back at seq 10/11 ... like right at the start of its use? it's almost like some interrupt or in memory semaphore thing mapped from the card is messing up? i'm looking for something to look into more specifically.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>