Bug 101515

Summary:	[BAT][SKL] ERROR Failed to get link status
Product:	DRI	Reporter:	Martin Peres <martin.peres>
Component:	DRM/Intel	Assignee:	Manasi <manasi.d.navare>
Status:	CLOSED FIXED	QA Contact:	Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity:	critical
Priority:	highest	CC:	intel-gfx-bugs
Version:	DRI git
Hardware:	Other
OS:	All
Whiteboard:	ReadyForDev
i915 platform:	SKL	i915 features:	display/DP

Description Martin Peres 2017-06-20 13:15:34 UTC

The machine fi-skl-6700hq started randomly generating the dmesg error message "[drm:intel_dp_check_link_status [i915]] *ERROR* Failed to get link status".

First seen on IGT_1218 (based on CI_DRM_2742): http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/IGT_1218/fi-skl-6700hq/igt@prime_busy@basic-wait-after-default.html

This however does not seem to be due to an IGT change:
http://benchsrv.fi.intel.com/archive/results/CI_IGT_test/IGT_1218/commits_short.log

It all looks like the fi-skl-6700hq is dying slowly but surely :D

Comment 1 Jani Saarinen 2017-06-21 06:26:42 UTC

3 more test cases added:
https://intel-gfx-ci.01.org/CI/CI_DRM_2746/fi-skl-6700hq/igt@prime_vgem@basic-sync-default.html

https://intel-gfx-ci.01.org/CI/CI_DRM_2745/fi-skl-6700hq/igt@drv_module_reload@basic-reload.html

https://intel-gfx-ci.01.org/CI/CI_DRM_2745/fi-skl-6700hq/igt@prime_self_import@basic-llseek-bad.html

Comment 2 Martin Peres 2017-07-05 07:44:01 UTC

This fixed the issue:
c99a259 drm/i915/edp: Add a T12 panel delay quirk to fix DP AUX CH timeouts

Comment 3 Martin Peres 2017-07-05 07:44:17 UTC

No need to ask QA to verify, so forcing to CLOSED.

Comment 4 Marta Löfstedt 2017-09-18 05:57:24 UTC

Reproduced on:

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3095/fi-skl-6700hq/igt@prime_self_import@basic-llseek-size.html

Comment 5 Jani Saarinen 2017-10-05 06:59:56 UTC

Series merger:
https://patchwork.freedesktop.org/series/31361/

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.