Created attachment 82889 [details] dmesg System Environment: -------------------------- Platform: Haswell Kernel: (drm-intel-nightly)1a7fc2d3e919e151a2e87dd6c98f20eccf95e041 Bug detailed description: ----------------------------- It causes system hang with VGA_HDMI on Haswell. It happens on drm-intel-nightly and drm-intel-next-queued kernel.It doesn't happen on drm-intel-fixes kernel. Bisect shows:4906557eb37b7fef84fad4304acef6dedf919880 is the first bad commit. commit 4906557eb37b7fef84fad4304acef6dedf919880 Author: Rodrigo Vivi <rodrigo.vivi@gmail.com> AuthorDate: Thu Jul 11 18:45:05 2013 -0300 Commit: Daniel Vetter <daniel.vetter@ffwll.ch> CommitDate: Thu Jul 18 10:34:54 2013 +0200 drm/i915: Hook PSR functionality PSR must be enabled after transcoder and port are running. And it is only available for HSW. v2: move enable/disable to intel_ddi v3: The spec suggests PSR should be disabled even before backlight (by pzano v4: also disabling and enabling whenever panel is disabled/enabled. v5: make it last patch to avoid breaking whenever bisecting. So calling for update and force exit came to this patch along with enable/disable calls v6: Remove unused and unecessary psr_enable/disable calls, as notice by Paul CC: Paulo Zanoni <paulo.r.zanoni@intel.com> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@gmail.com> [danvet: Drop the psr exit code in the busy ioctl since I didn't merge that part of the infrastructure yet - it needs more thought.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> [ 472.767289] Call Trace: [ 472.767324] [<ffffffffa009b496>] ? intel_edp_psr_update+0x3d/0x78 [i915] [ 472.767392] [<ffffffffa008c22d>] ? intel_pipe_set_base+0x218/0x295 [i915] [ 472.767459] [<ffffffffa008d89c>] ? haswell_crtc_mode_set+0x2b2/0x2da [i915] [ 472.770288] [<ffffffffa008f610>] ? __intel_set_mode+0xd30/0xf4e [i915] [ 472.773117] [<ffffffff810334b1>] ? wake_up_klogd+0x2d/0x31 [ 472.775932] [<ffffffffa00906db>] ? intel_set_mode+0xd/0x27 [i915] [ 472.778734] [<ffffffffa0090cf1>] ? intel_crtc_set_config+0x5fc/0x803 [i915] [ 472.781512] [<ffffffffa0018d36>] ? drm_mode_set_config_internal+0x44/0xac [drm] [ 472.784260] [<ffffffffa001a922>] ? drm_mode_setcrtc+0x423/0x4c8 [drm] [ 472.786987] [<ffffffffa000e3c7>] ? drm_ioctl+0x28b/0x3ab [drm] [ 472.789706] [<ffffffffa001a4ff>] ? drm_mode_setplane+0x317/0x317 [drm] [ 472.792442] [<ffffffff810e494e>] ? vfs_ioctl+0x1e/0x31 [ 472.795175] [<ffffffff810e5124>] ? do_vfs_ioctl+0x3ad/0x3ef [ 472.797919] [<ffffffff810e51b4>] ? SyS_ioctl+0x4e/0x7e [ 472.800665] [<ffffffff816f7e12>] ? system_call_fastpath+0x16/0x1b [ 472.803419] Code: f7 ff b2 01 59 5b 5d 41 5c 41 5d 41 5e 88 d0 41 5f c3 55 53 41 52 48 8b 87 40 ff ff ff 48 8b af 78 ff ff ff 48 8b 98 30 03 00 00 <48> 8b 45 50 48 8b 4b 10 48 8b 90 88 00 00 00 f6 41 07 10 75 30 [ 472.806533] RIP [<ffffffffa0098268>] intel_edp_psr_match_conditions+0x19/0x25d [i915] [ 472.809487] RSP <ffff8801492fda38> [ 472.812416] CR2: 0000000000000050 output: Using monotonic timestamps running testcase: absolute-wf_vblank Beginning absolute-wf_vblank on crtc 3, connector 10 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .............................................................. absolute-wf_vblank on crtc 3, connector 10: PASSED Beginning absolute-wf_vblank on crtc 5, connector 10 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 .............................................................. absolute-wf_vblank on crtc 5, connector 10: PASSED Beginning absolute-wf_vblank on crtc 7, connector 10 1920x1080 60 1920 1966 1996 2080 1080 1082 1086 1112 0xa 0x48 138780 ............................................................. absolute-wf_vblank on crtc 7, connector 10: PASSED Beginning absolute-wf_vblank on crtc 3, connector 22 1920x1200 60 1920 1968 2000 2080 1200 1203 1209 1235 0x9 0x48 154000 Reproduce steps: ---------------------------- 1. ./kms_flip --run-subtest absolute-wf_vblank
A kernel oops for Rodrigo!
Oops, where did you hide that CRTC?
*** This bug has been marked as a duplicate of bug 67526 ***
Closing old verified.
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.