All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 211807] [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed
Date: Fri, 19 Nov 2021 12:25:30 +0000	[thread overview]
Message-ID: <bug-211807-2300-JMTF70Cc1f@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211807-2300@https.bugzilla.kernel.org/>

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

Daan (daandelombaert@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daandelombaert@gmail.com

--- Comment #14 from Daan (daandelombaert@gmail.com) ---
I also had this in my logs yesterday, right before my system locked completely
(had to do a hard reset).

I also have a Lenovo Thinkpad Thunderbolt Dock, which connects my Thinkpad T480
with two external monitors (one Hdmi, one Displayport). I didn't have this
lockup before, in the past both monitors were hdmi so maybe Displayport is the
culprit here?

Exact message:  i915 0000:00:02.0: [drm] *ERROR* mstb 00000000afedfd20 port 3:
DPCD read on addr 0x4b0 for 1 bytes NAKed

Setup: 
Thinkpad T480, i7, UHD Graphics 620 + Nvidia Mx150
Fedora (5.14.16-201.fc34.x86_64)

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2021-11-19 12:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 20:53 [Bug 211807] New: [drm:drm_dp_mst_dpcd_read] *ERROR* mstb 000000004e6288dd port 3: DPCD read on addr 0x60 for 1 bytes NAKed bugzilla-daemon
2021-04-25  2:50 ` [Bug 211807] " bugzilla-daemon
2021-07-20 12:19 ` bugzilla-daemon
2021-08-27 22:02 ` bugzilla-daemon
2021-09-16 21:48 ` bugzilla-daemon
2021-09-16 21:49 ` bugzilla-daemon
2021-09-17 19:09 ` bugzilla-daemon
2021-09-17 19:13 ` bugzilla-daemon
2021-09-17 20:55 ` bugzilla-daemon
2021-09-18 11:59 ` bugzilla-daemon
2021-09-18 12:56 ` bugzilla-daemon
2021-10-23 21:03 ` bugzilla-daemon
2021-10-26  9:27 ` bugzilla-daemon
2021-10-26 13:09 ` bugzilla-daemon
2021-11-19 12:25 ` bugzilla-daemon [this message]
2021-11-19 14:35 ` bugzilla-daemon
2021-11-23 15:48 ` bugzilla-daemon
2021-11-24 13:22 ` bugzilla-daemon
2021-12-13 11:22 ` bugzilla-daemon
2021-12-13 11:23 ` bugzilla-daemon
2022-03-13  8:08 ` bugzilla-daemon
2022-04-07 15:48 ` bugzilla-daemon
2022-07-30 16:29 ` bugzilla-daemon
2022-08-03 15:31 ` 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-211807-2300-JMTF70Cc1f@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 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.