From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 108014] AMD WX4150 - Hotplugging on an MST hub doesn't work Date: Tue, 09 Oct 2018 23:41:21 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0362298870==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 72BCD6E12B for ; Tue, 9 Oct 2018 23:41:21 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0362298870== Content-Type: multipart/alternative; boundary="15391284812.b8464.25311" Content-Transfer-Encoding: 7bit --15391284812.b8464.25311 Date: Tue, 9 Oct 2018 23:41:21 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D108014 Lyude Paul changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|AMD WX4150 - MST is |AMD WX4150 - Hotplugging on |entirely nonfunctional, |an MST hub doesn't work |spams dmesg with errors | Priority|high |medium Severity|major |normal --- Comment #8 from Lyude Paul --- (In reply to Jerry Zuo from comment #4) > Created attachment 141903 [details] [review] > MST patch First off sorry for this taking so long. I had been prepared to test this pretty quickly originally, but there was a mixup in the office and the lapt= op I needed to reproduce this got sent to another office until today. So this mi= ght not get done in the time I was hoping for, but that's ok as that isn't AMD's fault. Additionally, the problem is less severe then I originally thought anyway. So, after testing a couple of kernels mst seems to work now that I'm back f= rom XDC. I think what must have happened is I didn't get enough time to look at= it closely, and got confused by two things: - The external monitors on the MST hub not coming on were most likely cause= d by the keypress spam from the ACPI hotplug events and I just didn't notice at = the time. I have a fix for this by the way which still needs reviews! https://patchwork.freedesktop.org/patch/251897/ - I /thought/ I was actually testing hotplugging by removing the entire topology instead of just downstream sinks, as downstream sink hotplugging i= sn't nearly as important as the former and I kind of expected downstream sink hotplugging to be broken anyway. But, I guess not? Weird. All of that being said, that means this is a lot more severe then I thought! :), phew. ---- Now onto the actual patch that you sent: what exactly is this supposed to be doing? Are we dereferencing an mstb's port too early somewhere in the DRM M= ST core? --=20 You are receiving this mail because: You are the assignee for the bug.= --15391284812.b8464.25311 Date: Tue, 9 Oct 2018 23:41:21 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated Lyude Paul changed bug 10801= 4
What Removed Added
Summary AMD WX4150 - MST is entirely nonfunctional, spams dmesg with= errors AMD WX4150 - Hotplugging on an MST hub doesn't work
Priority high medium
Severity major normal

Commen= t # 8 on bug 10801= 4 from Lyude Paul 
(In reply to Jerry Zuo from comment #4)
> Created attachment 14190=
3 [details] [review] [review]
> MST patch

First off sorry for this taking so long. I had been prepared to test this
pretty quickly originally, but there was a mixup in the office and the lapt=
op I
needed to reproduce this got sent to another office until today. So this mi=
ght
not get done in the time I was hoping for, but that's ok as that isn't AMD's
fault. Additionally, the problem is less severe then I originally thought
anyway.

So, after testing a couple of kernels mst seems to work now that I'm back f=
rom
XDC. I think what must have happened is I didn't get enough time to look at=
 it
closely, and got confused by two things:

- The external monitors on the MST hub not coming on were most likely cause=
d by
the keypress spam from the ACPI hotplug events and I just didn't notice at =
the
time. I have a fix for this by the way which still needs reviews!
https://patchwo=
rk.freedesktop.org/patch/251897/
- I /thought/ I was actually testing hotplugging by removing the entire
topology instead of just downstream sinks, as downstream sink hotplugging i=
sn't
nearly as important as the former and I kind of expected downstream sink
hotplugging to be broken anyway. But, I guess not? Weird.

All of that being said, that means this is a lot more severe then I thought!
:), phew.

----
Now onto the actual patch that you sent: what exactly is this supposed to be
doing? Are we dereferencing an mstb's port too early somewhere in the DRM M=
ST
core?

You are receiving this mail because:
  • You are the assignee for the bug.
= --15391284812.b8464.25311-- --===============0362298870== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0362298870==--