<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB DP] WARNING: pipe_off wait timed out in ironlake_crtc_disable" href="https://bugs.freedesktop.org/show_bug.cgi?id=67462#c13">Comment # 13</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [SNB DP] WARNING: pipe_off wait timed out in ironlake_crtc_disable" href="https://bugs.freedesktop.org/show_bug.cgi?id=67462">bug 67462</a> from <a class="email" href="mailto:daniel@ffwll.ch" title="Daniel Vetter <daniel@ffwll.ch>"> Daniel Vetter</a> <pre>(In reply to <a href="show_bug.cgi?id=67462#c10">comment #10</a>) > (In reply to <a href="show_bug.cgi?id=67462#c6">comment #6</a>) > > I've forgotten to actually add my question ;-) Which of the two types of > > calltraces do you see on snb-hsw, even without DP? > > I test latest -next-queued kernel on a hsw desktop without any display > ports, it seems like we also have two types of calltraces. I grabbed the > dmesg. :) This is again a different calltrace: [ 1.168965] WARNING: CPU: 1 PID: 1258 at drivers/gpu/drm/i915/i915_gem.c:3440 i915_gem_object_set_cache_level+0x1bd/0x1dc [i915]() Please consult the section about backtraces in the bug filing BKM about how to properly differentiate calltraces in dmesg. We can't just smash all the calltraces into one bug report ;-) Differentiating calltraces properly is imo a very important part of the first-stage bug traiging QA does.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>