Bug 112101

Summary: [CI][RESUME] igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen|igt@i915_suspend@fence-restore-untiled - dmesg-warn - *ERROR* failed to get link status
Product: DRI Reporter: Lakshmi <lakshminarayana.vudum>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: RESOLVED MOVED QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: minor    
Priority: low CC: intel-gfx-bugs, jose.souza
Version: DRI git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: TGL i915 features: display/FBC

Description Lakshmi 2019-10-22 13:45:05 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen.html
<3> [837.552221] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status
Comment 1 CI Bug Log 2019-10-22 18:14:27 UTC
The CI Bug Log issue associated to this bug has been updated.

### New filters associated

* TGL: igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen - dmesg-warn - *ERROR* failed to get link status
  - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7104/re-tgl-u/igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen.html
Comment 2 Jose Roberto de Souza 2019-10-24 19:47:02 UTC
Not sure if this is bug, the aux transaction failed on the external DP port when doing the probing to setup the test environment probably due to some issue on the monitor as 100ms later the monitor triggered a long pulse and then i915 was able to probe the monitor.

So a real user it would have no impact, for CI it could have caused the test to fail if the external monitors was being used on the test. It is very likely this a issue on the monitor that auto recovered itself and send the long pulse.
Comment 3 CI Bug Log 2019-10-25 11:57:38 UTC
A CI Bug Log filter associated to this bug has been updated:

{- TGL: igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen - dmesg-warn - *ERROR* failed to get link status -}
{+ TGL: igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen|igt@i915_suspend@fence-restore-untiled - dmesg-warn - *ERROR* failed to get link status +}

New failures caught by the filter:

  * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/re-tgl-u/igt@i915_suspend@fence-restore-untiled.html
Comment 4 Lakshmi 2019-10-25 11:59:32 UTC
(In reply to CI Bug Log from comment #3)
> A CI Bug Log filter associated to this bug has been updated:
> 
> {- TGL: igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen -
> dmesg-warn - *ERROR* failed to get link status -}
> {+ TGL:
> igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-
> fullscreen|igt@i915_suspend@fence-restore-untiled - dmesg-warn - *ERROR*
> failed to get link status +}
> 
> New failures caught by the filter:
> 
>   *
> https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/re-tgl-u/
> igt@i915_suspend@fence-restore-untiled.html

How to do you see this issue? Is it having the same impact as above?
Comment 5 Jose Roberto de Souza 2019-10-25 19:56:01 UTC
(In reply to Lakshmi from comment #4)
> (In reply to CI Bug Log from comment #3)
> > A CI Bug Log filter associated to this bug has been updated:
> > 
> > {- TGL: igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-fullscreen -
> > dmesg-warn - *ERROR* failed to get link status -}
> > {+ TGL:
> > igt@kms_frontbuffer_tracking@psr-1p-primscrn-spr-indfb-
> > fullscreen|igt@i915_suspend@fence-restore-untiled - dmesg-warn - *ERROR*
> > failed to get link status +}
> > 
> > New failures caught by the filter:
> > 
> >   *
> > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7144/re-tgl-u/
> > igt@i915_suspend@fence-restore-untiled.html
> 
> How to do you see this issue? Is it having the same impact as above?

The same thing as described in comment 2 happened but this time it took more 10sec to i915/display to recover it self.
Comment 6 Martin Peres 2019-11-29 19:43:17 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/542.

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.