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: Wed, 24 Nov 2021 13:22:07 +0000	[thread overview]
Message-ID: <bug-211807-2300-PDwjSGerSP@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211807-2300@https.bugzilla.kernel.org/>

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

Chatty (mail@chatty.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mail@chatty.de

--- Comment #17 from Chatty (mail@chatty.de) ---
My setup: MS Surface Book 2 + AOC U2879G6 via Surface Dock via DisplayPort
Tested kernels: 5.10.0 / 5.15.3 / 5.16.0-rc1

When connecting I get random results of:
* monitor remains black
* monitor exhibits 1080p@60 as max resolution
* monitor exhibits 1440p@60 as max resolution
* monitor exhibits 2160p@30 as max resolution
* monitor exhibits 2160p@30 as max resolution <== desired

On boot of 5.16.0-rc1 its initialized with:
> i915 0000:00:02.0: [drm] Finished loading DMC firmware
> i915/kbl_dmc_ver1_04.bin (v1.4)
> [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0 on minor 0

In the first case I see following dmesg output (black monitor):
> i915 0000:00:02.0: [drm] *ERROR* mstb 0000000009cd3ca6 port 1: DPCD read on
> addr 0x4b0 for 1 bytes NAKed

In the last case I see following dmesg output (despite monitor working):
> i915 0000:00:02.0: [drm] *ERROR* mstb 00000000f4b4c9f1 port 1: DPCD read on
> addr 0x4b0 for 1 bytes NAKed
> i915 0000:00:02.0: [drm] *ERROR* mstb 00000000f4b4c9f1 port 1: DPCD read on
> addr 0x4b0 for 1 bytes NAKed
> i915 0000:00:02.0: [drm] *ERROR* mstb 00000000f4b4c9f1 port 1: DPCD read on
> addr 0x4b0 for 1 bytes NAKed
> i915 0000:00:02.0: [drm] *ERROR* mstb 00000000f4b4c9f1 port 1: DPCD read on
> addr 0x4b0 for 1 bytes NAKed
> i915 0000:00:02.0: [drm] *ERROR* mstb 00000000f4b4c9f1 port 1: DPCD read on
> addr 0x4b0 for 1 bytes NAKed

-- 
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-24 13:22 UTC|newest]

Thread overview: 34+ 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
2021-11-19 14:35 ` bugzilla-daemon
2021-11-23 15:48 ` bugzilla-daemon
2021-11-24 13:22 ` bugzilla-daemon [this message]
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
2024-06-11  4:51 ` bugzilla-daemon
2024-06-17 20:10 ` bugzilla-daemon
2024-06-19  5:48 ` bugzilla-daemon
2024-07-23  2:06 ` bugzilla-daemon
2024-07-24  7:55 ` bugzilla-daemon
2024-08-13 16:28 ` bugzilla-daemon
2024-12-06  4:59 ` bugzilla-daemon
2025-01-30 17:19 ` bugzilla-daemon
2025-05-26  8:44 ` bugzilla-daemon
2025-09-26  8:00 ` 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-PDwjSGerSP@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.