From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 110381] Failed to updateMST allocation table forpipe idx:0
Date: Thu, 09 May 2019 13:13:09 +0000 [thread overview]
Message-ID: <bug-110381-502-GuNeFdAyll@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110381-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 693 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #5 from Nicholas Kazlauskas <nicholas.kazlauskas@amd.com> ---
(In reply to Paul Menzel from comment #4)
> (In reply to Nicholas Kazlauskas from comment #3)
> > We're able to reproduce the problem.
> >
> > I believe that we found the issue was caused by the new common helper DRM
> > for DP MST hotplug. A fix is in the works for this issue.
>
> Great news! Thank you for the update.
>
> Is there another bug report this should be merged with?
Not that I'm aware of at least - I think this was the first user report for the
issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1640 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-05-09 13:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-10 13:44 [Bug 110381] Failed to updateMST allocation table forpipe idx:0 bugzilla-daemon
2019-04-29 8:36 ` bugzilla-daemon
2019-05-09 12:52 ` bugzilla-daemon
2019-05-09 13:00 ` bugzilla-daemon
2019-05-09 13:03 ` bugzilla-daemon
2019-05-09 13:13 ` bugzilla-daemon [this message]
2019-06-11 19:38 ` bugzilla-daemon
2019-06-11 19:56 ` bugzilla-daemon
2019-06-12 15:42 ` bugzilla-daemon
2019-07-29 16:16 ` bugzilla-daemon
2019-08-28 1:21 ` bugzilla-daemon
2019-11-01 21:03 ` bugzilla-daemon
2019-11-09 13:14 ` bugzilla-daemon
2019-11-19 9:18 ` 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-110381-502-GuNeFdAyll@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox