<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV86] Distorted graphics on NVIDIA GeForce 8400M G after upgrade the kernel to 3.7.0 version" href="https://bugs.freedesktop.org/show_bug.cgi?id=58378#c44">Comment # 44</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NV86] Distorted graphics on NVIDIA GeForce 8400M G after upgrade the kernel to 3.7.0 version" href="https://bugs.freedesktop.org/show_bug.cgi?id=58378">bug 58378</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>Try commenting the same line out and see what happens... (i.e. the one with 0x74c1) FWIW I do remember seeing some PCRYPT-related (and PVP/PBSP-related) errors on start in the form of MMIO write failures in your log and thinking it odd: nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000010 FAULT at 0x10200c Which of course is an enable of FIFO_ACCESS... probably pretty important. (See <a href="https://github.com/envytools/envytools/blob/master/rnndb/vdec/vp2/pcrypt2.xml">https://github.com/envytools/envytools/blob/master/rnndb/vdec/vp2/pcrypt2.xml</a>) But why do you get that error... anyone's guess. If you have the blob installed, would be interested to know if VDPAU hw decode acceleration works for H.264 (i.e. things are actually accelerated), because you get similar errors for the VP/BSP engines: nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 FAULT at 0x00fd94 nouveau E[ PBUS][0000:01:00.0] MMIO write of 0x00000000 FAULT at 0x103d94 And they're all interconnected, I think. [Sadly none of the other bug commenters were kind enough to leave a kernel log around, so can't easily tell if that was their issue as well.]</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>