Created attachment 115138 [details] dmesg ==System Environment== -------------------------- Regression: not sure Non-working platforms: BDW ==kernel== -------------------------- drm-intel-nightly/d600654ab94b325f253e267422dcf60302120ea0 commit d600654ab94b325f253e267422dcf60302120ea0 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Thu Apr 16 17:54:10 2015 +0200 drm-intel-nightly: 2015y-04m-16d-15h-53m-28s UTC integration manifest ==Bug detailed description== ----------------------------- It sporadically causes <3>[ 138.640445] [drm:gen8_irq_handler [i915]] *ERROR* The master control interrupt lied (SDE)!. Run it 2 cycles, it happens once. Following cases also have this error: igt@kms_cursor_crc@cursor-128x128-random igt@kms_cursor_crc@cursor-128x128-sliding igt@kms_cursor_crc@cursor-256x256-offscreen igt@kms_cursor_crc@cursor-256x256-onscreen igt@kms_cursor_crc@cursor-256x256-random igt@kms_cursor_crc@cursor-64x64-offscreen igt@kms_cursor_crc@cursor-64x64-onscreen igt@kms_cursor_crc@cursor-64x64-random igt@kms_cursor_crc@cursor-64x64-sliding output: IGT-Version: 1.10-gbeddb3b (x86_64) (Linux: 4.0.0_drm-intel-nightly_d60065_20150417+ x86_64) Beginning cursor-128x128-onscreen on pipe A, connector eDP-1 ............................ cursor-128x128-onscreen on pipe A, connector eDP-1: PASSED Beginning cursor-128x128-onscreen on pipe B, connector eDP-1 ............................ cursor-128x128-onscreen on pipe B, connector eDP-1: PASSED Beginning cursor-128x128-onscreen on pipe C, connector eDP-1 ............................ cursor-128x128-onscreen on pipe C, connector eDP-1: PASSED Subtest cursor-128x128-onscreen: SUCCESS (24.188s) ==Reproduce steps== ---------------------------- 1. ./kms_cursor_crc --run-subtest cursor-128x128-onscreen
kms_flip@dpms-off-confusion and kms_flip@dpms-off-confusion-interruptible also have this error.
*** This bug has been marked as a duplicate of bug 80896 ***
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.