All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103949] REG_WAIT timeout - dce110_stream_encoder_dp_blank line:930 - 4.15-rc1
Date: Mon, 17 Dec 2018 16:52:41 +0000	[thread overview]
Message-ID: <bug-103949-502-9nSlg9mdXt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103949-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 637 bytes --]

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

--- Comment #4 from Patrik Jakobsson <patrik.r.jakobsson@gmail.com> ---
Hi, I'm getting the same error on upstream 4.18, 4.19 and drm-fixes-4.20
whenever I hotplug a DP monitor. Can you point me to the patch that is supposed
to fix this? I took a quick look at the mailing list and found "[PATCH]
drm/amdgpu:Improves robustness of SOC15_WAIT_ON_RREG". Unfortunately this
doesn't work for me. I also tried something similar as that patch but in
generic_reg_wait(). Still no luck.

Thanks
Patrik

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1483 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2018-12-17 16:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  3:54 [Bug 103949] REG_WAIT timeout - dce110_stream_encoder_dp_blank line:930 - 4.15-rc1 bugzilla-daemon
2017-11-28  3:57 ` bugzilla-daemon
2018-09-22 16:47 ` bugzilla-daemon
2018-12-14 18:24 ` bugzilla-daemon
2018-12-17 16:52 ` bugzilla-daemon [this message]
2019-01-28 14:56 ` bugzilla-daemon
2019-11-19  8:26 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-103949-502-9nSlg9mdXt@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.