Bug 93120

Summary:	[SNB BAT IGT regression] WARN_ON(was_visible)
Product:	DRI	Reporter:	Daniel Vetter <daniel>
Component:	DRM/Intel	Assignee:	Maarten Lankhorst <bugs>
Status:	CLOSED FIXED	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	normal
Priority:	highest	CC:	intel-gfx-bugs
Version:	XOrg git	Keywords:	regression
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Daniel Vetter 2015-11-26 13:29:23 UTC

[   66.785318] ------------[ cut here ]------------
[   66.785338] WARNING: CPU: 0 PID: 5768 at drivers/gpu/drm/i915/intel_display.c:11740 intel_plane_atomic_calc_changes+0x5af/0x790 [i915]()
[   66.785340] WARN_ON(was_visible)
[   66.785341] Modules linked in:
[   66.785342]  snd_hda_codec_hdmi x86_pkg_temp_thermal snd_hda_codec_realtek intel_powerclamp snd_hda_codec_generic coretemp crct10dif_pclmul crc32_pclmul i915 snd_hda_intel snd_hda_codec snd_hwdep snd_hda_core snd_pcm lpc_ich mei_me mei broadcom bcm_phy_lib tg3 ptp pps_core
[   66.785356] CPU: 0 PID: 5768 Comm: kms_pipe_crc_ba Not tainted 4.4.0-rc2-gfxbench+ #1
[   66.785357] Hardware name: Dell Inc. XPS 8300  /0Y2MRG, BIOS A06 10/17/2011
[   66.785358]  ffffffffa01d56d0 ffff880095d379f8 ffffffff813df18c ffff880095d37a40
[   66.785361]  ffff880095d37a30 ffffffff810747b1 0000000000000001 ffff88012997b4d0
[   66.785363]  ffff8800c1ae33d8 ffff8800bf33ba18 0000000000000001 ffff880095d37a90
[   66.785366] Call Trace:
[   66.785369]  [<ffffffff813df18c>] dump_stack+0x4e/0x82
[   66.785372]  [<ffffffff810747b1>] warn_slowpath_common+0x81/0xc0
[   66.785373]  [<ffffffff81074837>] warn_slowpath_fmt+0x47/0x50
[   66.785385]  [<ffffffffa017012f>] intel_plane_atomic_calc_changes+0x5af/0x790 [i915]
[   66.785388]  [<ffffffff8150a93a>] ? drm_rect_clip_scaled+0x10a/0x110
[   66.785390]  [<ffffffff814e1c63>] ? drm_plane_helper_check_update+0xb3/0x1d0
[   66.785401]  [<ffffffffa0150a8b>] intel_plane_atomic_check+0x13b/0x1f0 [i915]
[   66.785403]  [<ffffffff814e9703>] drm_atomic_helper_check_planes+0x43/0x1d0
[   66.785415]  [<ffffffffa016a0a1>] intel_atomic_check+0x301/0x1090 [i915]
[   66.785416]  [<ffffffff8150b5c0>] ? drm_modeset_lock+0x30/0xf0
[   66.785418]  [<ffffffff8150cf42>] drm_atomic_check_only+0x142/0x5e0
[   66.785420]  [<ffffffff8150c82b>] ? drm_atomic_set_crtc_for_connector+0x1b/0x90
[   66.785421]  [<ffffffff8150d3f2>] drm_atomic_commit+0x12/0x50
[   66.785424]  [<ffffffff814ea305>] drm_atomic_helper_set_config+0x75/0xb0
[   66.785425]  [<ffffffff814fc010>] drm_mode_set_config_internal+0x60/0x110
[   66.785427]  [<ffffffff81500c26>] drm_mode_setcrtc+0x186/0x4e0
[   66.785429]  [<ffffffff814f2f6d>] drm_ioctl+0x13d/0x590
[   66.785431]  [<ffffffff81500aa0>] ? drm_mode_setplane+0x1b0/0x1b0
[   66.785433]  [<ffffffff811d4d9c>] do_vfs_ioctl+0x2fc/0x550
[   66.785435]  [<ffffffff8118d60a>] ? vm_munmap+0x4a/0x60
[   66.785437]  [<ffffffff811e080a>] ? __fget_light+0x6a/0x90
[   66.785438]  [<ffffffff811d502c>] SyS_ioctl+0x3c/0x70
[   66.785441]  [<ffffffff81797d1b>] entry_SYSCALL_64_fastpath+0x16/0x73
[   66.785442] ---[ end trace 7c5af83250defaf2 ]---


This is a regression since CI build 844

Comment 1 Daniel Vetter 2015-11-26 13:31:46 UTC

One more: Seems to only affect igt@kms_pipe_crc_basic@hang-read-crc-pipe-a

Comment 2 Daniel Vetter 2015-12-08 09:34:00 UTC

Assigning to Maarten as a likely atomic fallout issue.

Comment 3 Maarten Lankhorst 2015-12-16 12:44:46 UTC

Wow, talk about something that should never happen.. Is this still reproducable on nightly?

Comment 4 Daniel Vetter 2016-01-13 12:54:04 UTC

(In reply to Maarten Lankhorst from comment #3)
> Wow, talk about something that should never happen.. Is this still
> reproducable on nightly?

I think all the fixes for this have been merged now. Maarten, is this correct, can we close this?

Comment 5 Maarten Lankhorst 2016-01-18 11:04:52 UTC

If you haven't seen it happen again feel free to close it.

Comment 6 Jari Tahvanainen 2016-12-13 09:02:06 UTC

Closing resolved+fixed after 11 months without comments.

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.