[Bug 103429] [drm:intel_dp_start_link_train [i915]] *ERROR* failed to get link status

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Nov 3 19:43:54 UTC 2017


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

--- Comment #2 from Anatol <anatol.pomozov at gmail.com> ---
I've been trying to use my computer with i3 desktop manager (I believe it does
not use Mutter). And I was able to get into "monitor does not wake up state". I
believe it is the same as with Mutter crash before.

I have logs per your request. I see messages like this one

Nov 01 20:00:34 argo kernel: [drm:intel_dp_aux_ch [i915]] dp_aux_ch timeout
status 0x7d4003ff
Nov 01 20:00:34 argo kernel: [drm:intel_dp_aux_ch [i915]] dp_aux_ch timeout
status 0x7d4003ff
Nov 01 20:00:34 argo kernel: [drm:intel_dp_aux_ch [i915]] dp_aux_ch timeout
status 0x7d4003ff
Nov 01 20:00:34 argo kernel: [drm:intel_dp_aux_ch [i915]] dp_aux_ch timeout
status 0x7d4003ff
Nov 01 20:00:34 argo kernel: [drm:intel_dp_aux_ch [i915]] dp_aux_ch timeout
status 0x7d4003ff
Nov 01 20:00:34 argo kernel: [drm:intel_dp_aux_ch [i915]] dp_aux_ch timeout
status 0x7d4003ff
Nov 01 20:00:34 argo kernel: [drm:intel_dp_aux_ch [i915]] dp_aux_ch timeout
status 0x7d4003ff
Nov 01 20:00:34 argo kernel: [drm:drm_dp_dpcd_access [drm_kms_helper]] Too many
retries, giving up. First error: -110
Nov 01 20:00:34 argo kernel: [drm:intel_dp_start_link_train [i915]] *ERROR*
failed to enable link training
Nov 01 20:00:34 argo kernel: [drm:intel_dp_start_link_train [i915]] Link
Training failed at link rate = 540000, lane count = 4




Here is the full log
https://gist.githubusercontent.com/anatol/ef5d273506bea731d45066e2110211cd/raw/5d588032bc9f7b6dd435a2bccc3e0b0bbd4a9c0e/monitor_does_not_wakeup.txt

-- 
You are receiving this mail because:
You are the assignee for the bug.
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/20171103/dedfd7cc/attachment-0001.html>


More information about the intel-gfx-bugs mailing list