From: bugzilla-daemon@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, 03 Aug 2022 15:31:42 +0000 [thread overview]
Message-ID: <bug-211807-2300-NBOlU0i3Sz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-211807-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=211807
--- Comment #23 from crptdngl71@gmx.net ---
Further details:
After logging into spinchat the issue does not occur straight away. It takes a
bit, use all buttons a while.
This seems to suggest that the issue is related to a memory buffer that leaks
somehow or gets corrupted, because after that has been reached the issue occurs
more frequently.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-08-03 15:32 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
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 [this message]
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-NBOlU0i3Sz@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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;
as well as URLs for NNTP newsgroup(s).