<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NVC1] [BISECTED] Monitor on Display port shows distortions" href="https://bugs.freedesktop.org/show_bug.cgi?id=67628#c10">Comment # 10</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NVC1] [BISECTED] Monitor on Display port shows distortions" href="https://bugs.freedesktop.org/show_bug.cgi?id=67628">bug 67628</a> from <a class="email" href="mailto:torsten.wagner@gmail.com" title="Torsten Wagner <torsten.wagner@gmail.com>"> Torsten Wagner</a> <pre>Hi Ilia, thanks for the feedback. Attached you will find the kernel log of an working and non-working kernel. A quick look showed that the non-working kernel reads in (or simply log) much more data from the display port init. The lines below can be found in the NON working kernel but not in the working one NOT WORKING KERNEL: (grep DP) [ 1.742406] nouveau T[ VBIOS][0000:01:00.0] 0x57ab[1]: DP_CONDITION 0x05 0x15 [ 1.742584] nouveau T[ VBIOS][0000:01:00.0] 0x591d[ ]: DP_CONDITION 0x00 0x08 [ 1.742589] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: 2 lanes at 270000 KB/s [ 1.742772] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: training pattern 1 [ 1.743115] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 00 [ 1.743122] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 00 [ 1.743796] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 00 00 00 00 cc cc [ 1.743797] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 38 [ 1.743807] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 38 [ 1.744478] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 11 00 00 00 cc cc [ 1.744479] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: training pattern 2 [ 1.745486] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 11 00 00 00 cc cc [ 1.745487] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 38 [ 1.745493] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 38 [ 1.746432] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 11 00 00 00 88 88 [ 1.746432] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 10 [ 1.746443] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 10 [ 1.747381] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 11 00 00 00 44 44 [ 1.747382] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 08 [ 1.747390] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 08 [ 1.748330] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 11 00 00 00 00 00 [ 1.748331] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 00 [ 1.748340] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 00 [ 1.749301] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 11 00 00 00 44 44 [ 1.749301] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 08 [ 1.749308] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 08 [ 1.750265] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: status 77 00 01 00 44 44 [ 1.750265] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 0 08 [ 1.750272] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: config lane 1 08 [ 1.750596] nouveau D[ PDISP][0000:01:00.0] DP:0006:0342: training pattern 0 [ 1.751350] nouveau T[ VBIOS][0000:01:00.0] 0x58fd[0]: DP_CONDITION 0x00 0x11 vs. WORKING KERNEL (grep DP) [ 5.677400] nouveau T[ VBIOS][0000:01:00.0] 0x57ab[1]: DP_CONDITION 0x05 0x15 [ 5.677577] nouveau T[ VBIOS][0000:01:00.0] 0x591d[ ]: DP_CONDITION 0x00 0x08 [ 5.686368] nouveau T[ VBIOS][0000:01:00.0] 0x58fd[0]: DP_CONDITION 0x00 0x11 As you can see, the entire PDISP part is missing not sure it is simply not logged or it is a new feature which creates the problem. Thanks for looking into this.... On 5 February 2014 04:21, <<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>> wrote: > <a href="show_bug.cgi?id=67628#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [NVC1] [BISECTED] Monitor on Display port shows distortions" href="show_bug.cgi?id=67628">bug 67628</a> from Ilia Mirkin > > Can you post boot logs of kernels with and without the problem booted with > > nouveau.debug=trace drm.debug=0xe > > ________________________________ > You are receiving this mail because: > > You reported the bug.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>