[Bug 103558] [IGT] [KBL only] igt@* - dmesg-warn *ERROR* Link Training Unsuccessful

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=103558

--- Comment #53 from Marta Löfstedt <marta.lofstedt at intel.com> ---
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4177/shard-kbl3/igt@gem_sync@basic-store-each.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4177/shard-kbl5/igt@gem_eio@hibernate.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4177/shard-kbl5/igt@kms_rmfb@close-fd.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4177/shard-kbl5/igt@kms_vblank@pipe-c-ts-continuation-modeset-rpm.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4177/shard-kbl5/igt@prime_vgem@basic-fence-mmap.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4176/shard-kbl3/igt@kms_vblank@pipe-a-query-forked-hang.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4176/shard-kbl3/igt@kms_plane@pixel-format-pipe-a-planes.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3683/shard-kbl5/igt@kms_vblank@pipe-a-accuracy-idle.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3683/shard-kbl5/igt@kms_vblank@pipe-c-ts-continuation-idle.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3682/shard-kbl2/igt@syncobj_wait@wait-all-snapshot.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3682/shard-kbl2/igt@kms_vblank@pipe-b-query-idle.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3682/shard-kbl2/igt@gem_mmap_wc@write-cpu-read-wc.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3681/shard-kbl3/igt@kms_atomic@crtc_invalid_params_fence.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3681/shard-kbl3/igt@kms_vblank@pipe-c-ts-continuation-modeset-hang.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3681/shard-kbl3/igt@kms_vblank@pipe-c-query-forked-busy-hang.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20180125/6666289b/attachment.html>