dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 209019] [drm:dpcd_set_source_specific_data [amdgpu]] *ERROR* Error in DP aux read transaction, not writing source specific data
Date: Wed, 26 Aug 2020 20:04:02 +0000	[thread overview]
Message-ID: <bug-209019-2300-WU3bA0Z5Lv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209019-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=209019

--- Comment #6 from rtmasura+kernel@hotmail.com ---
Hmm, new wire did not help. And it always recovers during shutdown of the
kernel, so when it leaves graphical mode. I don't think that rules out
hardware, though, so still testing.

Also didn't realize they had backported the hack to the LTS kernel.. so it also
is not ruled out.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-08-26 20:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24  4:03 [Bug 209019] New: [drm:dpcd_set_source_specific_data [amdgpu]] *ERROR* Error in DP aux read transaction, not writing source specific data bugzilla-daemon
2020-08-24 15:27 ` [Bug 209019] " bugzilla-daemon
2020-08-24 19:42 ` bugzilla-daemon
2020-08-24 20:17 ` bugzilla-daemon
2020-08-25  2:01 ` bugzilla-daemon
2020-08-26 18:23 ` bugzilla-daemon
2020-08-26 20:04 ` bugzilla-daemon [this message]
2020-08-27  3:19 ` 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-209019-2300-WU3bA0Z5Lv@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox