Bug 103097

Summary:	[BAT] igt@kms_busy@basic-flip-c - dmesg-warn - EDID is invalid - ERROR CPU pipe C FIFO underrun
Product:	DRI	Reporter:	Marta Löfstedt <marta.lofstedt>
Component:	DRM/Intel	Assignee:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Status:	CLOSED WORKSFORME	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	critical
Priority:	high	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	SKL	i915 features:	display/atomic

Description Marta Löfstedt 2017-10-04 09:57:17 UTC

On CI_DRM_3171 fi-skl-6700k

[  328.925135] i915 0000:00:02.0: DP-1: EDID is invalid:
[  328.925140] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.925143] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.925145] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.925147] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.925149] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.925152] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.925154] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.925156] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  328.939253] Setting dangerous option reset - tainting kernel
[  328.939476] Setting dangerous option reset - tainting kernel
[  329.006466] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe C FIFO underrun
[  329.015197] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun
[  329.799638] Setting dangerous option reset - tainting kernel

Full data:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3171/fi-skl-6700k/igt@kms_busy@basic-flip-c.html

Comment 1 Marta Löfstedt 2017-10-10 05:59:18 UTC

[  459.553335] i915 0000:00:02.0: DP-1: EDID is invalid:
[  459.553359] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.553373] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.553385] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.553396] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.553407] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.553418] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.553429] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.553440] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720636] i915 0000:00:02.0: DP-1: EDID is invalid:
[  459.720661] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720673] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720684] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720695] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720706] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720717] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720728] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.720739] 	[00] ZERO 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
[  459.759676] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=39 end=40) time 117 us, min 1073, max 1079, scanline start 1071, end 1079
[  459.821118] [drm] Atomic update on pipe (B) took 105 us, max time under evasion is 100 us
[  460.359142] [drm] Atomic update on pipe (B) took 102 us, max time under evasion is 100 us
[  460.505060] [drm] Atomic update on pipe (B) took 102 us, max time under evasion is 100 us
[  460.677502] [drm] Atomic update on pipe (A) took 104 us, max time under evasion is 100 us
[  460.682371] [drm] Atomic update on pipe (B) took 111 us, max time under evasion is 100 us


https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3196/fi-skl-6700k/igt@kms_pipe_crc_basic@read-crc-pipe-b.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3198/fi-skl-6700k/igt@kms_pipe_crc_basic@nonblocking-crc-pipe-c.html

Comment 2 Marta Löfstedt 2017-11-17 08:54:20 UTC

The issue hasn't been seen since CI_DRM_3198: 2017-10-09

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.