Bug 95125 - [BAT SNB IVB BYT] kms_pipe_crc_basic/hang-read-crc-pipe-? / kms_flip/basic-flip-vs-dpms vblank wait timed out
Summary: [BAT SNB IVB BYT] kms_pipe_crc_basic/hang-read-crc-pipe-? / kms_flip/basic-fl...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: highest normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
: 95262 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-04-25 08:46 UTC by Joonas Lahtinen
Modified: 2016-09-01 09:44 UTC (History)
3 users (show)

See Also:
i915 platform: SNB
i915 features: display/atomic


Attachments

Description Joonas Lahtinen 2016-04-25 08:46:19 UTC
Happens during: kms_pipe_crc_basic --run-subtest hang-read-crc-pipe-A

Relevant error:
[   64.438319] ------------[ cut here ]------------
[   64.438344] WARNING: CPU: 6 PID: 5753 at drivers/gpu/drm/i915/intel_display.c:13529 intel_atomic_commit+0x1271/0x1400 [i915]
[   64.438345] pipe A vblank wait timed out
[   64.438347] Modules linked in: smsc75xx usbnet mii snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic x86_pkg_temp_thermal intel_powerclamp coretemp crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i915 snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core mei_me snd_pcm mei lpc_ich broadcom bcm_phy_lib tg3 ptp pps_core
[   64.438371] CPU: 6 PID: 5753 Comm: kms_pipe_crc_ba Not tainted 4.6.0-rc4-CI-Patchwork_2031+ #1
[   64.438373] Hardware name: Dell Inc. XPS 8300  /0Y2MRG, BIOS A06 10/17/2011
[   64.438374]  0000000000000000 ffff880129437b28 ffffffff81405db5 ffff880129437b78
[   64.438378]  0000000000000000 ffff880129437b68 ffffffff81079c7c 000034d92928e500
[   64.438381]  0000000000000001 ffff88003657b3f8 0000000000000000 0000000000000000
[   64.438384] Call Trace:
[   64.438389]  [<ffffffff81405db5>] dump_stack+0x67/0x92
[   64.438393]  [<ffffffff81079c7c>] __warn+0xcc/0xf0
[   64.438396]  [<ffffffff81079cea>] warn_slowpath_fmt+0x4a/0x50
[   64.438400]  [<ffffffff810c2df9>] ? finish_wait+0x59/0x70
[   64.438418]  [<ffffffffa017acf1>] intel_atomic_commit+0x1271/0x1400 [i915]
[   64.438420]  [<ffffffff810c2f60>] ? wait_woken+0x90/0x90
[   64.438423]  [<ffffffff81538d72>] drm_atomic_commit+0x32/0x50
[   64.438426]  [<ffffffff8151574d>] drm_atomic_helper_set_config+0x7d/0xb0
[   64.438429]  [<ffffffff815277d0>] drm_mode_set_config_internal+0x60/0x110
[   64.438430]  [<ffffffff8152c769>] drm_mode_setcrtc+0x199/0x500
[   64.438432]  [<ffffffff8151e74d>] drm_ioctl+0x13d/0x590
[   64.438433]  [<ffffffff8152c5d0>] ? drm_mode_setplane+0x1d0/0x1d0
[   64.438436]  [<ffffffff811ee0aa>] do_vfs_ioctl+0x8a/0x670
[   64.438438]  [<ffffffff811f9f3a>] ? __fget_light+0x6a/0x90
[   64.438439]  [<ffffffff811ee6cc>] SyS_ioctl+0x3c/0x70
[   64.438442]  [<ffffffff817d2fe9>] entry_SYSCALL_64_fastpath+0x1c/0xac
[   64.438444] ---[ end trace 92fddd8024f6b711 ]---
[   72.825698] drm/i915: Resetting chip after gpu hang
Comment 1 Maarten Lankhorst 2016-04-25 08:55:18 UTC
drm.debug=0x3f log?
Comment 2 Joonas Lahtinen 2016-04-25 10:15:42 UTC
BAT issue: /archive/results/CI_IGT_test/Patchwork_2031/
Comment 3 Ville Syrjala 2016-04-27 15:24:08 UTC
These vblank wait timeouts seems to plague the dell xps machine.

Could be related to
commit 8a292d016d1c ("drm/i915: Make RPS EI/thresholds multiple of 25 on SNB-BDW")

since the symptoms I was fixing there seemed to indicate scheduling/timer interrupts getting lost. Perhaps we're still losing vblank interrupts, but to a lesser degree? Playing around with the RPS EI/threshold values a bit more might be warranted.
Comment 4 Daniel Vetter 2016-05-04 15:23:19 UTC
*** Bug 95262 has been marked as a duplicate of this bug. ***
Comment 5 Ville Syrjala 2016-05-12 15:15:35 UTC
Also seen on ro-ivb2-i7-3770
Comment 6 Tvrtko Ursulin 2016-06-30 09:20:05 UTC
Another failure on BYT/kms_flip/basic-flip-vs-dpms looks similar enough (/archive/results/CI_IGT_test/RO_Patchwork_1335/):

[  459.087969] ------------[ cut here ]------------
[  459.088252] WARNING: CPU: 1 PID: 7674 at drivers/gpu/drm/i915/intel_display.c:13669 intel_atomic_commit_tail+0x1179/0x1180 [i915]
[  459.088261] pipe B vblank wait timed out
[  459.088266] Modules linked in: snd_hda_intel i915 drm_kms_helper drm snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic intel_powerclamp snd_hda_codec coretemp crct10dif_pclmul crc32_pclmul snd_hwdep ghash_clmulni_intel snd_hda_core snd_pcm lpc_ich i2c_algo_bit syscopyarea sysfillrect sysimgblt fb_sys_fops i2c_hid i2c_designware_platform i2c_designware_core r8169 mii sdhci_acpi sdhci mmc_core [last unloaded: vgem]
[  459.088353] CPU: 1 PID: 7674 Comm: kms_flip Tainted: G     U          4.7.0-rc5-gfxbench-RO_Patchwork_1335+ #1
[  459.088360] Hardware name: \xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff \xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff\xffffffff/DN2820FYK, BIOS FYBYT10H.86A.0053.2016.0205.1707 02/05/2016
[  459.088366]  0000000000000000 ffff8800b6777ac0 ffffffff8140e495 ffff8800b6777b10
[  459.088395]  0000000000000000 ffff8800b6777b00 ffffffff8107a996 0000356500000296
[  459.088421]  0000000000000158 ffff8800366b9158 0000000000000004 0000000000000001
[  459.088435] Call Trace:
[  459.088449]  [<ffffffff8140e495>] dump_stack+0x67/0x92
[  459.088458]  [<ffffffff8107a996>] __warn+0xc6/0xe0
[  459.088470]  [<ffffffff8107a9fa>] warn_slowpath_fmt+0x4a/0x50
[  459.088487]  [<ffffffff810c4719>] ? finish_wait+0x59/0x70
[  459.088562]  [<ffffffffa04a4589>] intel_atomic_commit_tail+0x1179/0x1180 [i915]
[  459.088575]  [<ffffffff810d009f>] ? mark_held_locks+0x6f/0xa0
[  459.088588]  [<ffffffff810d01f2>] ? trace_hardirqs_on_caller+0x122/0x1b0
[  459.088601]  [<ffffffff810c48e0>] ? wake_atomic_t_function+0x60/0x60
[  459.088675]  [<ffffffffa04a4a0c>] intel_atomic_commit+0x47c/0x5a0 [i915]
[  459.088703]  [<ffffffffa01233c1>] ? __drm_atomic_helper_crtc_duplicate_state+0x51/0xa0 [drm_kms_helper]
[  459.088750]  [<ffffffffa036b002>] drm_atomic_commit+0x32/0x50 [drm]
[  459.088776]  [<ffffffffa0122ca8>] drm_atomic_helper_connector_dpms+0xe8/0x1a0 [drm_kms_helper]
[  459.088815]  [<ffffffffa03582e0>] ? _object_find+0x70/0xe0 [drm]
[  459.088856]  [<ffffffffa035f3b4>] drm_mode_obj_set_property_ioctl+0x224/0x230 [drm]
[  459.088894]  [<ffffffffa035f3eb>] drm_mode_connector_property_set_ioctl+0x2b/0x30 [drm]
[  459.088924]  [<ffffffffa0350b6e>] drm_ioctl+0x13e/0x530 [drm]
[  459.088959]  [<ffffffffa035f3c0>] ? drm_mode_obj_set_property_ioctl+0x230/0x230 [drm]
[  459.088970]  [<ffffffff811df513>] ? __vfs_read+0x23/0x110
[  459.088978]  [<ffffffff811f2f1e>] do_vfs_ioctl+0x8e/0x660
[  459.088986]  [<ffffffff810e60bd>] ? debug_lockdep_rcu_enabled+0x1d/0x20
[  459.088994]  [<ffffffff811ffe2a>] ? __fget_light+0x6a/0x90
[  459.089001]  [<ffffffff811f352c>] SyS_ioctl+0x3c/0x70
[  459.089011]  [<ffffffff817ad269>] entry_SYSCALL_64_fastpath+0x1c/0xac
[  459.092250] ---[ end trace 0c0033dfddd287b4 ]---
Comment 7 Jari Tahvanainen 2016-09-01 09:22:33 UTC
This failure (for kms_pipe_crc_basic@hang-read-crc-pipe-a and kms_flip@basic-flip-vs-dpms) has not been visible in Patchwork Intel GFX CI Testing during last week. I propose this to be closed as Resolved + Worksforme. Please comment if you disagree.
Comment 8 yann 2016-09-01 09:44:28 UTC
I agree both kms_pipe_crc_basic@hang-read-crc-pipe-a and kms_flip@basic-flip-vs-dpms are now passing. 
Last week we had still failure with hang-read-crc-pipe-a on some platform but now we are getting only a warn message "drm/i915: Resetting chip after gpu hang" for that is expected :)


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.