<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [G84] nouveau fails to properly initialize GPU" href="https://bugs.freedesktop.org/show_bug.cgi?id=82714#c20">Comment # 20</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [G84] nouveau fails to properly initialize GPU" href="https://bugs.freedesktop.org/show_bug.cgi?id=82714">bug 82714</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>(In reply to Bruno from <a href="show_bug.cgi?id=82714#c18">comment #18</a>) > Created <a href="attachment.cgi?id=116185" name="attach_116185" title="linux-4.1-rc5+">attachment 116185</a> <a href="attachment.cgi?id=116185&action=edit" title="linux-4.1-rc5+">[details]</a> > linux-4.1-rc5+ > > Same 4.1-rc5+ kernel but this time around performing nvapeek/nvapoke. > > Doing the peek/poke makes display get signal over DVI but does not prevent > the system from freezing after X has started. > > The last lines of output from X were (the COPY failure coming some time > after the rest): > (--) Depth 24 pixmap format is 32 bpp > (II) NOUVEAU(0): Channel setup complete. > (EE) NOUVEAU(0): [COPY] failed to allocate class. Expected. Your GPU doesn't have COPY engine. > > > The PGRAPH/VM FLUSH timeouts look like they could have something to do with > the freeze and be cause of X COPY failure. Recent kernels should fix the PDISP hang error, which in turn might avoid tickling the vm lockup. Can you test a kernel that includes 697bb728d9e (v4.2 should have it).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>