<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-cpu - incomplete - softdog" href="https://bugs.freedesktop.org/show_bug.cgi?id=106071#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@kms_frontbuffer_tracking@fbcpsr-rgb101010-draw-mmap-cpu - incomplete - softdog" href="https://bugs.freedesktop.org/show_bug.cgi?id=106071">bug 106071</a> from <a class="email" href="mailto:marta.lofstedt@intel.com" title="Marta Löfstedt <marta.lofstedt@intel.com>"> Marta Löfstedt</a> <pre>(In reply to Jani Nikula from <a href="show_bug.cgi?id=106071#c1">comment #1</a>) > (In reply to Marta Löfstedt from <a href="show_bug.cgi?id=106071#c0">comment #0</a>) > > <7>[ 767.397714] [drm:intel_dp_aux_xfer [i915]] Forbidden recv_bytes = 0 on > > aux transaction > > <7>[ 767.399013] [drm:intel_dp_read_dpcd [i915]] DPCD: 12 14 84 41 00 00 01 > > 01 02 00 00 00 00 0b 00 > > I don't think I've ever seen this happen. From code: > > /* > * By BSpec: "Message sizes of 0 or >20 are not allowed." > * We have no idea of what happened so we return -EBUSY so > * drm layer takes care for the necessary retries. > */ > > However, the retry seems to succeed just fine, so I'm not sure if the dmesg > part here is a red herring, and the bug is somewhere else. It could be a duplicate of <a class="bz_bug_link bz_status_NEW " title="NEW - [CI] igt@kms_* - incomplete - softdog - backtrace in dmesg indicates: intel_frontbuffer_flush" href="show_bug.cgi?id=105959">bug 105959</a>. However, I believe that there is too much time in-between the the backtrace and when owatch triggers.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>