<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c28">Comment # 28</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 <span class="vcard"><a class="email" href="mailto:jikos@jikos.cz" title="Jiri Kosina <jikos@jikos.cz>"> <span class="fn">Jiri Kosina</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=76554#c27">comment #27</a>)
<span class="quote">> Indeed. What happens is that UXA now finally detects that the kernel is
> reporting that it cannot execute GPU commands, and instead it falls back to
> CPU rendering directly into the framebuffer.</span >
Understood, thanks. So kernel should probably put a huge warning into dmesg
once such condition is detected and workaround applied.
<span class="quote">> > to it, although I assume the ring initialization failure still needs to be
> > solved ... ?
>
> Yes. We never knew why g45 failed in the first place, if we can figure out
> what changed now, we may be able to create a better band-aid.</span >
Excellent, thanks. Happy to test any diag patches necessary.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<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>