Bug 86187 - [BDW Regression]igt/kms_setmode/clone-exclusive-crtc takes more than 10 minutes and causes BUG: unable to handle kernel NULL pointer dereference at (null)
Summary: [BDW Regression]igt/kms_setmode/clone-exclusive-crtc takes more than 10 minut...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: highest major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-12 06:47 UTC by lu hua
Modified: 2017-02-10 08:58 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
dmesg (124.79 KB, text/plain)
2014-11-12 06:47 UTC, lu hua 		no flags Details
View All

Description lu hua 2014-11-12 06:47:10 UTC 
Created attachment 109320 [details]
dmesg

==System Environment==
--------------------------
Regression: yes
good commit: 0b5492d6b53251acab99b1906a328fac56e08be3(it has bug 68463, fail but not time out)
bad commit: 477f799e966db4c36ca40198e1f48ff0af69e319
Non-working platforms: BDW

==kernel==
--------------------------
drm-intel-nightly/9a7620f405895714b4e0dc3181a8328b4406287e

==Bug detailed description==
It takes more than 10 minutes and doesn't exit testing.

dmesg BUG:
[  103.953141] BUG: unable to handle kernel NULL pointer dereference at           (null)

output:
root@x-bdw05:/GFX/Test/Intel_gpu_tools/intel-gpu-tools/tests# time ./kms_setmode --run-subtest clone-exclusive-crtc
IGT-Version: 1.8-gc049c39 (x86_64) (Linux: 3.18.0-rc3_drm-intel-nightly_9a7620_20141112+ x86_64)
Testing: clone-exclusive-crtc 2 connector combinations
  Test id#1 CRTC count 2
    CRTC[8] [Pipe A] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[12] [Pipe B] Mode: 640x480@60Hz Connectors: HDMI-A-1[32] (NC)
  Test id#2 CRTC count 2
    CRTC[8] [Pipe A] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[16] [Pipe C] Mode: 640x480@60Hz Connectors: HDMI-A-1[32] (NC)
  Test id#3 CRTC count 2
    CRTC[12] [Pipe B] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[8] [Pipe A] Mode: 640x480@60Hz Connectors: HDMI-A-1[32] (NC)
  Test id#4 CRTC count 2
    CRTC[12] [Pipe B] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[16] [Pipe C] Mode: 640x480@60Hz Connectors: HDMI-A-1[32] (NC)
  Test id#5 CRTC count 2
    CRTC[16] [Pipe C] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[8] [Pipe A] Mode: 640x480@60Hz Connectors: HDMI-A-1[32] (NC)
  Test id#6 CRTC count 2
    CRTC[16] [Pipe C] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[12] [Pipe B] Mode: 640x480@60Hz Connectors: HDMI-A-1[32] (NC)
  Test id#7 CRTC count 2
    CRTC[8] [Pipe A] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[12] [Pipe B] Mode: 640x480@60Hz Connectors: HDMI-A-2[35] (NC)

Call trace:
[   67.323990] ------------[ cut here ]------------
[   67.324004] WARNING: CPU: 0 PID: 4679 at drivers/gpu/drm/i915/intel_ddi.c:1565 intel_ddi_compute_config+0x39/0x6c [i915]()
[   67.324005] compute_config() on unknown output!
[   67.324006] Modules linked in: dm_mod ac acpi_cpufreq i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea
[   67.324016] CPU: 0 PID: 4679 Comm: kms_setmode Not tainted 3.18.0-rc3_drm-intel-nightly_9a7620_20141112+ #1450
[   67.324017]  0000000000000000 0000000000000009 ffffffff81789012 ffff880142d3fb68
[   67.324020]  ffffffff810368cc ffffffff8337f162 ffffffffa00e3620 ffff880142d3fb88
[   67.324022]  ffff880002c56000 ffff880147e0e400 000000000000000a 0000000000000001
[   67.324024] Call Trace:
[   67.324030]  [<ffffffff81789012>] ? dump_stack+0x41/0x51
[   67.324034]  [<ffffffff810368cc>] ? warn_slowpath_common+0x78/0x90
[   67.324044]  [<ffffffffa00e3620>] ? intel_ddi_compute_config+0x39/0x6c [i915]
[   67.324047]  [<ffffffff8103697c>] ? warn_slowpath_fmt+0x45/0x4a
[   67.324056]  [<ffffffffa00e3620>] ? intel_ddi_compute_config+0x39/0x6c [i915]
[   67.324067]  [<ffffffffa00d1be3>] ? intel_modeset_pipe_config+0x3d5/0x935 [i915]
[   67.324073]  [<ffffffffa0012ffb>] ? drm_ut_debug_printk+0x59/0x5e [drm]
[   67.324083]  [<ffffffffa00d48b8>] ? intel_crtc_set_config+0x76f/0xbf0 [i915]
[   67.324091]  [<ffffffffa0017f25>] ? drm_mode_set_config_internal+0x48/0xbd [drm]
[   67.324097]  [<ffffffffa001b938>] ? drm_mode_setcrtc+0x3e6/0x48b [drm]
[   67.324107]  [<ffffffffa0010738>] ? drm_ioctl+0x279/0x3bc [drm]
[   67.324110]  [<ffffffff810e86b6>] ? tlb_finish_mmu+0xb/0x2f
[   67.324115]  [<ffffffffa001b552>] ? drm_mode_setplane+0x1ce/0x1ce [drm]
[   67.324120]  [<ffffffffa000fac7>] ? drm_gem_vm_close+0x2a/0x4b [drm]
[   67.324124]  [<ffffffff8111a53f>] ? do_vfs_ioctl+0x3ec/0x435
[   67.324126]  [<ffffffff8111a5d1>] ? SyS_ioctl+0x49/0x78
[   67.324130]  [<ffffffff8178e6d2>] ? system_call_fastpath+0x12/0x17
[   67.324131] ---[ end trace bf75bc0a2682d00b ]---

==Reproduce steps==
---------------------------- 
1. ./kms_setmode --run-subtest clone-exclusive-crtc
Comment 1 Daniel Vetter 2014-11-19 13:06:51 UTC 
Please bisect where this hang/timeout started to appear.

But before that please retest on latest -nightly, this might be fixed already.
Comment 2 Li Xu 2014-11-21 03:36:07 UTC 
We tried with the latest-nightly ,and it seems that hang/timeout has disappeared.But the it shows that:

n-subtest clone-exclusive-crtc
IGT-Version: 1.8-gd807891 (x86_64) (Linux: 3.18.0-rc5_drm-intel-nightly_18748b_20141121+ x86_64)
Testing: clone-exclusive-crtc 2 connector combinations
  Test id#1 CRTC count 2
    CRTC[8] [Pipe A] Mode: 1920x1080@60Hz Connectors: eDP-1[19]
    CRTC[12] [Pipe B] Mode: 640x480@60Hz Connectors: HDMI-A-1[32] (NC)
Test assertion failure function test_crtc_config, file kms_setmode.c:431:
Failed assertion: config_failed == !!(tconf->flags & TEST_INVALID)
Last errno: 22, Invalid argument
Subtest clone-exclusive-crtc: FAIL (0.078s)


And the dmesg call trace

[   72.460042] Call Trace:
[   72.460048]  [<ffffffff81789572>] ? dump_stack+0x41/0x51
[   72.460052]  [<ffffffff810368cc>] ? warn_slowpath_common+0x78/0x90
[   72.460062]  [<ffffffffa00e61ca>] ? intel_ddi_compute_config+0x3a/0x6f [i915]
[   72.460065]  [<ffffffff8103697c>] ? warn_slowpath_fmt+0x45/0x4a
[   72.460074]  [<ffffffffa00e61ca>] ? intel_ddi_compute_config+0x3a/0x6f [i915]
[   72.460085]  [<ffffffffa00d33a9>] ? intel_modeset_pipe_config+0x3d5/0x935 [i915]
[   72.460091]  [<ffffffffa0012ffb>] ? drm_ut_debug_printk+0x59/0x5e [drm]
[   72.460102]  [<ffffffffa00d60bc>] ? intel_crtc_set_config+0x772/0xbf5 [i915]
[   72.460109]  [<ffffffffa0017f54>] ? drm_mode_set_config_internal+0x4e/0xd2 [drm]
[   72.460116]  [<ffffffffa001ba4d>] ? drm_mode_setcrtc+0x3e9/0x48e [drm]
[   72.460121]  [<ffffffffa0010738>] ? drm_ioctl+0x279/0x3bc [drm]
[   72.460124]  [<ffffffff810e877f>] ? tlb_finish_mmu+0xb/0x2f
[   72.460130]  [<ffffffffa001b664>] ? drm_mode_setplane+0x1ce/0x1ce [drm]
[   72.460135]  [<ffffffffa000fac7>] ? drm_gem_vm_close+0x2a/0x4b [drm]
[   72.460139]  [<ffffffff8111a76f>] ? do_vfs_ioctl+0x3ec/0x435
[   72.460141]  [<ffffffff8111a801>] ? SyS_ioctl+0x49/0x78
[   72.460144]  [<ffffffff8178ec12>] ? system_call_fastpath+0x12/0x17
[   72.460146] ---[ end trace 8f48497b96dbe155 ]---
[   72.460148] ------------[ cut here ]------------
[   72.460158] WARNING: CPU: 0 PID: 4694 at drivers/gpu/drm/i915/intel_dp.c:140 intel_dp_max_link_bw+0x6f/0x77 [i915]()
[   72.460159] invalid max DP link bw val 0, using 1.62Gbps
[   72.460160] Modules linked in: snd_hda_codec_hdmi pcspkr snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm i2c_i801 lpc_ich snd_timer mfd_core snd soundcore dm_mod battery parport_pc parport ac acpi_cpufreq i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea
[   72.460172] CPU: 0 PID: 4694 Comm: kms_setmode Tainted: G     U  W      3.18.0-rc5_drm-intel-nightly_18748b_20141121+ #1774
[   72.460172]  0000000000000000 0000000000000009 ffffffff81789572 ffff8801441efaf8
[   72.460175]  ffffffff810368cc ffff880002c39000 ffffffffa00eb919 0000000000000009
Comment 3 lu hua 2014-12-30 05:48:16 UTC 
Test on latest -nightly kernel. The error goes away, the fail will be track 68463.
Comment 4 Jari Tahvanainen 2017-02-10 08:58:36 UTC 
Closing (>2 years) old Verified+Fixed.

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.