https://bugs.freedesktop.org/show_bug.cgi?id=110381
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #12 from carben...@outlook.com ---
Still happening on 5.3.8-300.fc31.x86_64
[ 5800.613189] WARNING: CPU: 7 PID: 1924 at
drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc_link.c:2462
update_mst_stream_alloc_table.cold+0x15/0x28 [amdgpu
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #11 from carben...@outlook.com ---
Seems to happen as well on 5.3.7 when waking two daisy-chained monitors from
sleep.
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Ellesmere [Radeon RX 470/480/570/570X/58
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #10 from jamespharve...@gmail.com ---
Also occurred on 5.2.1.
05:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
[AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64] [1002:687f] (rev c1) (prog-if 00
[VGA controller])
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #9 from John Francis ---
I am still seeing this error on kernel 5.2.2. I think it happens when I switch
away the monitors to another host on the KVM switch.
Switching back later, I get only 1 display, problematic as some windows are
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #8 from Paul Menzel ---
Why can’t it be said for certain, if the issue is fixed? The commit message
should reference this report, but `git log --grep 110381` does not show
anything.
--
You are receiving this mail because:
You are t
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #7 from Nicholas Kazlauskas ---
I think this is fixed 5.2 and the latest amd-staging-drm-next.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel maili
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #6 from John Francis ---
I get this on kernel 5.1.8 when I use a KVM switch with DisplayPort
daisy-chained MST monitors. It occurs when I switch back.
I can workaround by powering off the last monitor in the chain, and then
powering
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #5 from Nicholas Kazlauskas ---
(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 c
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #4 from Paul Menzel ---
(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 wor
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #3 from Nicholas Kazlauskas ---
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.
--
You are receiving this mai
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #2 from Paul Menzel ---
This still happens with Linux 5.1. I had to give the system away, so won’t have
access to it.
I had hoped for more help of the AMD developers to track down regressions.
--
You are receiving this mail becaus
https://bugs.freedesktop.org/show_bug.cgi?id=110381
--- Comment #1 from Paul Menzel ---
This still happens with Linux 5.1-rc6.
```
[Fri Apr 26 16:02:16 2019] [drm] DM_MST: stopping TM on aconnector:
c53c37c4 [id: 59]
[Fri Apr 26 16:02:16 2019] [drm] DM_MST: Disabling connector: d
https://bugs.freedesktop.org/show_bug.cgi?id=110381
Bug ID: 110381
Summary: Failed to updateMST allocation table forpipe idx:0
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: n
14 matches
Mail list logo
