<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [gm45 regression] [drm:init_ring_common]: *ERROR* render ring initialization failed" href="https://bugs.freedesktop.org/show_bug.cgi?id=76554#c92">Comment # 92</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO --- - [gm45 regression] [drm:init_ring_common]: *ERROR* render ring initialization failed" href="https://bugs.freedesktop.org/show_bug.cgi?id=76554">bug 76554</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>Created <a href="attachment.cgi?id=104227" name="attach_104227" title="head start before enabling">attachment 104227</a> <a href="attachment.cgi?id=104227&action=edit" title="head start before enabling">[details]</a> <a href='page.cgi?id=splinter.html&bug=76554&attachment=104227'>[review]</a> head start before enabling Another crazy idea. Looking at logs and Jiri's patch, the critical step seems to be when we set the valid bit. Let's see what happens if we give the ring a headstart, hopefully catching the moving ring. You can experiment with different values, as long as they're a multiple of 8. 64 might be magic since it's the cacheline size (which in a few w/a is really important for register writes, even though that's strange).</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>