Bug 85311

Summary: [HSW Regression]igt/kms_setmode/clone-exclusive-crtc causes OOPS
Product: DRI Reporter: Guo Jinxian <jinxianx.guo>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: critical    
Priority: high CC: intel-gfx-bugs, przanoni
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
dmesg none

Description Guo Jinxian 2014-10-22 06:04:49 UTC
Created attachment 108219 [details]
dmesg

==System Environment==
--------------------------
Regression: Yes.
Good commit on -next-queud: b7c0d9df97c10ec5693a838df2fd53058f8e9e96(bug 68463)

Non-working platforms: HSW

==kernel==
--------------------------
origin/drm-intel-nightly: 1e61c930ec1745ec3cfc77be1cdd023c409de26d(works)
    drm-intel-nightly: 2014y-10m-21d-17h-46m-36s UTC integration manifest
origin/drm-intel-next-queued: f3b190654cbceb0788bfc3b67e4f38ad870dfb84(works)
    drm/i915: add runtime PM get/put call in i915_execlists
origin/drm-intel-fixes: f114040e3ea6e07372334ade75d1ee0775c355e1(fails)
    Linux 3.18-rc1

==Bug detailed description==
igt/gem_exec_parse some subcases failigt/kms_setmode/clone-exclusive-crtc causes system hang


Output:
[root@x-hsw27 tests]# time ./kms_setmode --run-subtest clone-exclusive-crtc
IGT-Version: 1.8-gbba1cd0 (x86_64) (Linux: 3.18.0-rc1_drm-intel-nightly_1e61c9_20141022+ x86_64)
Testing: clone-exclusive-crtc 2 connector combinations
  Test id#1 CRTC count 2
    CRTC[8] [Pipe A] Mode: 1680x1050@60Hz Connectors: VGA-1[18]
    CRTC[12] [Pipe B] Mode: 640x480@60Hz Connectors: HDMI-A-1[21] (NC)



^Z^C

==Reproduce steps==
---------------------------- 
1. ./kms_setmode --run-subtest clone-exclusive-crtc
Comment 1 Paulo Zanoni 2014-10-22 13:15:03 UTC
Can you please bisect this for us?
Comment 2 Chris Wilson 2014-10-22 18:47:01 UTC
[   35.654241] WARNING: CPU: 0 PID: 4000 at drivers/gpu/drm/i915/intel_ddi.c:1566 intel_ddi_compute_config+0x39/0x6c [i915]()
[   35.654242] compute_config() on unknown output!
...
[   35.654336] BUG: unable to handle kernel NULL pointer dereference at           (null)
[   35.654367] IP: [<ffffffffa00de532>] intel_dp_max_link_bw+0x10/0x75 [i915]
[   35.654398] PGD 250228067 PUD 251862067 PMD 0 
[   35.654415] Oops: 0000 [#1] SMP 
[   35.654428] Modules linked in: ipv6 dm_mod acpi_cpufreq i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea
[   35.654477] CPU: 0 PID: 4000 Comm: kms_setmode Tainted: G        W      3.18.0-rc1_drm-intel-nightly_1e61c9_20141022+ #742
[   35.654513] Hardware name: ASUS All Series/Z87-EXPERT, BIOS 1008 05/17/2013
[   35.654536] task: ffff88025122a800 ti: ffff880250328000 task.ti: ffff880250328000
[   35.654561] RIP: 0010:[<ffffffffa00de532>]  [<ffffffffa00de532>] intel_dp_max_link_bw+0x10/0x75 [i915]
[   35.654598] RSP: 0018:ffff88025032bb10  EFLAGS: 00010297
[   35.654616] RAX: 0000000000000000 RBX: ffff8800881e7000 RCX: 0000000000000000
[   35.654640] RDX: ffff8800881e7000 RSI: ffff880250327c00 RDI: ffff8800881e70e0
[   35.654664] RBP: ffff8802517b9800 R08: 0000000000000002 R09: 00000000fffffffe
[   35.654687] R10: 00000000fffffffe R11: ffffffff81a52200 R12: ffff880002ce0000
[   35.654711] R13: ffff8800881e0000 R14: ffff880250327c00 R15: 0000000000000001
[   35.654735] FS:  00007faa66e868c0(0000) GS:ffff88025fa00000(0000) knlGS:0000000000000000
[   35.654762] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[   35.654781] CR2: 0000000000000000 CR3: 00000002501a2000 CR4: 00000000001407f0
[   35.654804] Stack:
[   35.654811]  ffffffffa00de6ae ffffffffa0116bac ffff880200000018 ffff88025032bb78
[   35.654839]  ffff88025032bb38 00000000fffffffe ffff8800881e70e0 0000000000000000
[   35.654866]  0000000000000000 ffff880250327cd8 ffff880250db0708 ffff8800881e0000
[   35.654894] Call Trace:
[   35.654908]  [<ffffffffa00de6ae>] ? intel_dp_compute_config+0x63/0x479 [i915]
[   35.654938]  [<ffffffffa00c6df8>] ? __intel_set_mode+0x5cd/0x1216 [i915]
[   35.654961]  [<ffffffff8178a0df>] ? printk+0x4f/0x54
[   35.654983]  [<ffffffffa00c9be8>] ? intel_set_mode+0xd/0x27 [i915]
[   35.655009]  [<ffffffffa00ca7fb>] ? intel_crtc_set_config+0x757/0xa92 [i915]
[   35.655036]  [<ffffffffa0017f21>] ? drm_mode_set_config_internal+0x48/0xbd [drm]
[   35.655064]  [<ffffffffa001b931>] ? drm_mode_setcrtc+0x3e6/0x48b [drm]
[   35.655088]  [<ffffffffa0010738>] ? drm_ioctl+0x279/0x3bc [drm]
[   35.655108]  [<ffffffff810eebc2>] ? tlb_finish_mmu+0xb/0x2f
[   35.655129]  [<ffffffffa001b54b>] ? drm_mode_setplane+0x1ce/0x1ce [drm]
[   35.655153]  [<ffffffffa000fac7>] ? drm_gem_vm_close+0x2a/0x4b [drm]
[   35.655176]  [<ffffffff8112095b>] ? do_vfs_ioctl+0x3ec/0x435
[   35.655195]  [<ffffffff810a13d2>] ? __audit_syscall_entry+0xb2/0xd2
[   35.655217]  [<ffffffff8100d284>] ? syscall_trace_enter_phase1+0x11e/0x127
[   35.655240]  [<ffffffff811209ed>] ? SyS_ioctl+0x49/0x78
[   35.655258]  [<ffffffff810a15fb>] ? __audit_syscall_exit+0x209/0x225
[   35.655280]  [<ffffffff81792692>] ? system_call_fastpath+0x12/0x17
[   35.655301] Code: 48 8b 78 28 e8 cc 70 fa ff 83 7b 68 08 74 07 c7 43 68 07 00 00 00 5b 5d 41 5c c3 8a 57 1c 48 8b 8f b0 04 00 00 80 fa 0a 0f b6 c2 <48> 8b 09 74 5f 80 fa 14 74 06 80 fa 06 75 32 c3 48 8b 51 28 f6 
[   35.655412] RIP  [<ffffffffa00de532>] intel_dp_max_link_bw+0x10/0x75 [i915]
[   35.655441]  RSP <ffff88025032bb10>
[   35.655453] CR2: 0000000000000000
Comment 3 Guo Jinxian 2014-10-24 06:52:42 UTC
The good commit is wrong. I think the error occurs sporadically.

The test at 2014-04-30(nightly and next-queued branch) was hang(please refer comment 9 at bug 68463), and failed at both 2014-01-17(bug 73725) and 2014-07-23(comment9 at bug 73725). 
In a word. fails and hang interleave appearance. It's hard to bisect

By the way, I tried to test the failed commit(e.g.-fixes 2014-07-23), system still hangs.
Comment 4 Paulo Zanoni 2014-10-27 16:38:58 UTC

*** This bug has been marked as a duplicate of bug 68463 ***

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.