<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#c81">Comment # 81</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:jikos@jikos.cz" title="Jiri Kosina <jikos@jikos.cz>"> Jiri Kosina</a> <pre>Created <a href="attachment.cgi?id=104212" name="attach_104212" title="dmesg with patch from comment #80">attachment 104212</a> <a href="attachment.cgi?id=104212&action=edit" title="dmesg with patch from comment #80">[details]</a> dmesg with patch from <a href="show_bug.cgi?id=76554#c80">comment #80</a> Here is a dmesg from two suspend-resume cycles with Daniel's patch from <a href="show_bug.cgi?id=76554#c80">comment #80</a> (applied on top of all previous patches from Chris). There seems to be a change in behavior! Interestingly, I am not seeing [drm:init_ring_common] *ERROR* render ring initialization failed .... messages any more, and seems like I am indeed running accelerated still (i.e. the graphic seems to be still reasonably fast and usable). For some reason there is still render ring initialization failed [head now 01000000], fudging message present though. I will now try the patch from <a href="show_bug.cgi?id=76554#c80">comment #80</a> on top of something more recent than the 3.15-based branch with all Chris' patches applied, and will let you know.</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>