<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Regression: stuttering H.264 video w/ mythtv on old laptop w/ 915GM igp" href="https://bugs.freedesktop.org/show_bug.cgi?id=107600#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Regression: stuttering H.264 video w/ mythtv on old laptop w/ 915GM igp" href="https://bugs.freedesktop.org/show_bug.cgi?id=107600">bug 107600</a> from <a class="email" href="mailto:ubuntu@hbuus.com" title="H Buus <ubuntu@hbuus.com>"> H Buus</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=107600#c7">comment #7</a>) > See <a href="https://patchwork.freedesktop.org/series/48379/">https://patchwork.freedesktop.org/series/48379/</a> Many thanks for looking at this issue. I'm compiling with your patch now, but I'm unsure whether I'm supposed to do something about <a href="show_bug.cgi?id=107600#c5">comment #5</a>: "Put a WARN in i915_gem_object_attach_phys() to see how frequently that code is being called. If it is being called, grab an xorg debug log (xf86-video-intel compiled with --enable-debug=full) for the next question is why. If not, the problem is nothing to do with the phys object." My guess is <a href="show_bug.cgi?id=107600#c5">comment #5</a> was your first thought to collect debugging info and then you had a better idea, namely this patch. So, I am assuming I should not put a WARN in i915_gem_object_attach_phys(). If you do want a WARN added to i915_gem_object_attach_phys(), I would appreciate a patch, because I am unfamiliar with kernel WARN macros and how to use them. It wasn't clear to me, reading the commit msg for 6a2c4232ece145d8b5a8f95f767bd6d0d2d2f2bb, that it had anything to do with cursors (and I assume we're talking mouse cursors). FWIW, the mythtv frontend/player normally doesn't display a cursor, unless the mouse is moved. The frontend does have an option to disable the mouse cursor entirely, which I have not enabled. It also has options to change the output mode, refresh rate, etc. based on the video being played, which I haven't enabled either. Those options are intended to take advantage of a display's deinterlacing capabilities (especially TVs), which I have never explored.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>