Bug 89127 - [SKL]igt/kms_flip fails and causes drivers/gpu/drm/i915/intel_display.c:3612 intel_crtc_wait_for_pending_flips+0xec/0x1ad [i915]()
Summary: [SKL]igt/kms_flip fails and causes drivers/gpu/drm/i915/intel_display.c:3612 ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: high major
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-13 05:38 UTC by lu hua
Modified: 2017-10-06 14:31 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
dmesg (124.83 KB, text/plain)
2015-02-13 05:38 UTC, lu hua
no flags Details
dmesg-update (124.68 KB, text/plain)
2015-03-10 03:14 UTC, lu hua
no flags Details

Description lu hua 2015-02-13 05:38:20 UTC
Created attachment 113446 [details]
dmesg

==kernel==
--------------------------
drm-intel-nightly/b4442ee4e150506cebeee72249efc566c5f14bbe
commit b4442ee4e150506cebeee72249efc566c5f14bbe
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Fri Feb 6 10:25:31 2015 +0100

    drm-intel-nightly: 2015y-02m-06d-09h-25m-00s UTC integration manifest

==Bug detailed description==
-----------------------------
kms_flip fails and causes WARNING: CPU: 0 PID: 5242 at drivers/gpu/drm/i915/intel_display.c:3612 intel_crtc_wait_for_pending_flips+0xec/0x1ad [i915]()

run ./kms_flip --run-subtest absolute-wf_vblank output:
IGT-Version: 1.9-g9846e7f (x86_64) (Linux: 3.19.0-rc7_drm-intel-nightly_b4442e_20150208+ x86_64)
Using monotonic timestamps
Beginning absolute-wf_vblank on crtc 20, connector 34
  3200x1800 60 3200 3248 3280 3316 1800 1802 1807 1816 0xa 0x48 361310
............................................................
absolute-wf_vblank on crtc 20, connector 34: PASSED

Beginning absolute-wf_vblank on crtc 25, connector 34
  3200x1800 60 3200 3248 3280 3316 1800 1802 1807 1816 0xa 0x48 361310
(kms_flip:5242) CRITICAL: Test assertion failure function wait_for_events, file kms_flip.c:1258:
(kms_flip:5242) CRITICAL: Failed assertion: ret > 0
(kms_flip:5242) CRITICAL: select timed out or error (ret 0)
Subtest absolute-wf_vblank: FAIL (14.777s)

real    1m16.251s
user    0m0.340s
sys     0m0.196s

dmesg:
[  135.062622] WARNING: CPU: 0 PID: 5242 at drivers/gpu/drm/i915/intel_display.c:3612 intel_crtc_wait_for_pending_flips+0xec/0x1ad [i915]()
[  135.062625] WARN_ON(wait_event_timeout(dev_priv->pending_flip_queue, !intel_crtc_has_pending_flip(crtc), 60*HZ) == 0)
[  135.062670] Modules linked in: dm_mod snd_hda_codec_realtek snd_hda_codec_generic ppdev snd_hda_intel snd_hda_controller pcspkr snd_hda_codec snd_hwdep snd_pcm snd_timer i2c_i801 snd soundcore wmi battery parport_pc parport ac acpi_cpufreq i915 button video drm_kms_helper drm cfbfillrect cfbimgblt cfbcopyarea
[  135.062675] CPU: 0 PID: 5242 Comm: kms_flip Not tainted 3.19.0-rc7_drm-intel-nightly_b4442e_20150208+ #198
[  135.062677] Hardware name: Intel Corporation Skylake Client platform/Skylake Y LPDDR3 RVP3, BIOS SKLSE2R1.86C.B069.R00.1501192136 01/19/2015
[  135.062681]  0000000000000000 0000000000000009 ffffffff8179a69b ffff880143f3f8e8
[  135.062683]  ffffffff8103bdec ffffffff833b3a80 ffffffffa00d7244 ffffffff833b3a80
[  135.062686]  ffff880144282000 0000000000000000 ffff8801440b9800 ffff880004ed0000
[  135.062687] Call Trace:
[  135.062695]  [<ffffffff8179a69b>] ? dump_stack+0x40/0x50
[  135.062702]  [<ffffffff8103bdec>] ? warn_slowpath_common+0x98/0xb0
[  135.062725]  [<ffffffffa00d7244>] ? intel_crtc_wait_for_pending_flips+0xec/0x1ad [i915]
[  135.062729]  [<ffffffff8103be9c>] ? warn_slowpath_fmt+0x45/0x4a
[  135.062736]  [<ffffffff81064f7a>] ? prepare_to_wait_event+0xb0/0xec
[  135.062755]  [<ffffffffa00d7244>] ? intel_crtc_wait_for_pending_flips+0xec/0x1ad [i915]
[  135.062760]  [<ffffffff81065284>] ? add_wait_queue+0x3c/0x3c
[  135.062778]  [<ffffffffa00d73f9>] ? intel_begin_crtc_commit+0xf4/0x15e [i915]
[  135.062786]  [<ffffffffa0062a72>] ? drm_atomic_helper_commit_planes+0x4b/0x149 [drm_kms_helper]
[  135.062808]  [<ffffffffa00ee7fd>] ? intel_atomic_commit+0xa3/0xc9 [i915]
[  135.062815]  [<ffffffffa006328a>] ? drm_atomic_helper_plane_set_property+0x62/0x9c [drm_kms_helper]
[  135.062880]  [<ffffffffa001723f>] ? drm_mode_plane_set_obj_prop+0x22/0x48 [drm]
[  135.062886]  [<ffffffffa006528f>] ? restore_fbdev_mode+0x55/0xc3 [drm_kms_helper]
[  135.062892]  [<ffffffffa00665ff>] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x1f/0x56 [drm_kms_helper]
[  135.062897]  [<ffffffffa0066664>] ? drm_fb_helper_set_par+0x2e/0x33 [drm_kms_helper]
[  135.062918]  [<ffffffffa00eb9fa>] ? intel_fb_initial_config+0x4d1/0x4d1 [i915]
[  135.062936]  [<ffffffffa00eba0b>] ? intel_fbdev_set_par+0x11/0x55 [i915]
[  135.062940]  [<ffffffff813820db>] ? fb_set_var+0x246/0x32c
[  135.062946]  [<ffffffff8134577b>] ? vsnprintf+0x70/0x3cc
[  135.062952]  [<ffffffff8110dce2>] ? kmem_cache_alloc_trace+0x2a/0x104
[  135.062958]  [<ffffffff8137a6e0>] ? fbcon_blank+0x71/0x230
[  135.062963]  [<ffffffff81112176>] ? do_dentry_open+0x1f1/0x2a6
[  135.062968]  [<ffffffff813ce94b>] ? do_unblank_screen+0xef/0x169
[  135.062972]  [<ffffffff813c6f94>] ? vt_ioctl+0x4b0/0xf7f
[  135.062977]  [<ffffffff813be628>] ? tty_ioctl+0x946/0x9b5
[  135.062981]  [<ffffffff8112069f>] ? do_filp_open+0x2b/0x6f
[  135.062986]  [<ffffffff8112241d>] ? do_vfs_ioctl+0x412/0x459
[  135.062990]  [<ffffffff81129d70>] ? __fd_install+0x15/0x43
[  135.062994]  [<ffffffff811224ad>] ? SyS_ioctl+0x49/0x78
[  135.062998]  [<ffffffff817a0092>] ? system_call_fastpath+0x12/0x17
[  135.063000] ---[ end trace 342b78d921c2a6a6 ]---
[  135.063001] ------------[ cut here ]------------
[  135.063022] WARNING: CPU: 0 PID: 5242 at drivers/gpu/drm/i915/intel_display.c:3617 intel_crtc_wait_for_pending_flips+0x126/0x1ad [i915]()

==Reproduce steps==
---------------------------- 
1. ./kms_flip --run-subtest absolute-wf_vblank
Comment 1 Damien Lespiau 2015-02-16 12:16:18 UTC
This should be fixed by http://lists.freedesktop.org/archives/intel-gfx/2015-February/060079.html
Comment 2 Paulo Zanoni 2015-03-09 15:13:35 UTC
We just merged some SKL fixes that may affect all display-related tests. Please retest this bug against the latest drm-intel-nightly.
Comment 3 lu hua 2015-03-10 03:14:41 UTC
Created attachment 114181 [details]
dmesg-update

Test on the latest -nightly kernel. It still has warning.
[   63.539320] ------------[ cut here ]------------
[   63.539367] WARNING: CPU: 2 PID: 0 at drivers/gpu/drm/i915/intel_display.c:9826 intel_check_page_flip+0xa6/0xc1 [i915]()
[   63.539371] Kicking stuck page flip: queued at 1, now 5
[   63.539373] Modules linked in: dm_mod ppdev snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm pcspkr i2c_i801 snd_timer snd soundcore wmi battery parport_pc parport ac acpi_cpufreq i915 button video drm_kms_helper drm
[   63.539402] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.0.0-rc3_drm-intel-nightly_c09a3b_20150310+ #104
[   63.539405] Hardware name: Intel Corporation Skylake Client platform/Skylake Y LPDDR3 RVP3, BIOS SKLSE2R1.86C.B069.R00.1501192136 01/19/2015
[   63.539408]  0000000000000000 0000000000000009 ffffffff81793a7f ffff88014e483e18
[   63.539414]  ffffffff8103bcf8 ffff880148e479a0 ffffffffa00d12f1 0000000000000002
[   63.539418]  ffff880148e47800 ffff880004c2c000 0000000000000001 0000000000000001
[   63.539423] Call Trace:
[   63.539426]  <IRQ>  [<ffffffff81793a7f>] ? dump_stack+0x40/0x50
[   63.539443]  [<ffffffff8103bcf8>] ? warn_slowpath_common+0x98/0xb0
[   63.539469]  [<ffffffffa00d12f1>] ? intel_check_page_flip+0xa6/0xc1 [i915]
[   63.539476]  [<ffffffff8103bd55>] ? warn_slowpath_fmt+0x45/0x4a
[   63.539504]  [<ffffffffa00c1b6d>] ? __intel_pageflip_stall_check+0xaf/0xd8 [i915]
[   63.539529]  [<ffffffffa00d12f1>] ? intel_check_page_flip+0xa6/0xc1 [i915]
[   63.539557]  [<ffffffffa00a8e3a>] ? gen8_irq_handler+0x1fb/0x345 [i915]
[   63.539563]  [<ffffffff81071c70>] ? handle_irq_event_percpu+0x34/0x15b
[   63.539569]  [<ffffffff81081e69>] ? update_wall_time+0x524/0x53d
[   63.539573]  [<ffffffff81071dc5>] ? handle_irq_event+0x2e/0x4c
[   63.539578]  [<ffffffff8107430e>] ? handle_edge_irq+0xba/0xcf
[   63.539583]  [<ffffffff81004313>] ? handle_irq+0x15/0x1d
[   63.539588]  [<ffffffff81003dd7>] ? do_IRQ+0x41/0xc0
[   63.539593]  [<ffffffff81799daa>] ? common_interrupt+0x6a/0x6a
[   63.539595]  <EOI>  [<ffffffff816acead>] ? cpuidle_enter_state+0x71/0x11e
[   63.539608]  [<ffffffff816ace91>] ? cpuidle_enter_state+0x55/0x11e
[   63.539616]  [<ffffffff8106526b>] ? cpu_startup_entry+0x1f7/0x34d
[   63.539620] ---[ end trace 0d2c93c119121b88 ]---
Comment 4 Damien Lespiau 2015-03-10 16:21:04 UTC
That's a different problem... (the traces are different). Let's not use the same bug to track different problems please. I've filed a new bug (https://bugs.freedesktop.org/show_bug.cgi?id=89519) and closing this one.
Comment 5 lu hua 2015-03-11 05:47:17 UTC
Verified.Fixed.
Comment 6 Elizabeth 2017-10-06 14:31:25 UTC
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.