https://bugs.freedesktop.org/show_bug.cgi?id=107978
Shmerl changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #58 from Shmerl ---
The fix now merged in release branch:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6ee2846cb4e7c6e8acdcb265299ad1c6de42b437
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #57 from Alex Deucher ---
(In reply to Shmerl from comment #56)
> I see the fix in this submission though:
> https://lists.freedesktop.org/archives/amd-gfx/2019-February/031437.html
This patch missed the window for last week's
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #56 from Shmerl ---
I see the fix in this submission though:
https://lists.freedesktop.org/archives/amd-gfx/2019-February/031437.html
So it's coming in 5.1 only?
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #55 from Shmerl ---
Looks like the fix didn't make it into 5.0-rc7:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c?h=v5.0-rc7#n789
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #54 from Shmerl ---
(In reply to Jerry Zuo from comment #53)
> The fix should show up in the coming release.
Great, thanks!
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #53 from Jerry Zuo ---
The fix should show up in the coming release.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #52 from Shmerl ---
(In reply to Jerry Zuo from comment #51)
> Good to hear that the patch fixes your issue. The official patch will be
> merged to the next kernel release. Thank you so much for your dedicated
> testing and prompt
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #51 from Jerry Zuo ---
Good to hear that the patch fixes your issue. The official patch will be merged
to the next kernel release. Thank you so much for your dedicated testing and
prompt feedback ^_^
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #50 from Shmerl ---
I think I know what happened. When I was rebooting, I still had the older
kernel running (without the fix), to actually test the new one, so probably the
bug still kicked in after reboot.
I now rebooted a few
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #49 from Shmerl ---
Though my tests mostly focused on reboots. Let me double check what happens
after actual cold off and boot.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #48 from Shmerl ---
(In reply to Jerry Zuo from comment #47)
> You observed the monitor goes to sleep right after reboot, did you? Hotplug
> will have the display back on. Is that what you observed?
After any boot, not necessarily
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #47 from Jerry Zuo ---
You observed the monitor goes to sleep right after reboot, did you? Hotplug
will have the display back on. Is that what you observed?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #46 from Shmerl ---
(In reply to Jerry Zuo from comment #45)
> Please try the patch and see if that fixes your issue. We will come up with
> proper solution later.
I tested the patch, and it didn't fix the issue for me.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #45 from Jerry Zuo ---
Please try the patch and see if that fixes your issue. We will come up with
proper solution later.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
Alex Deucher changed:
What|Removed |Added
Attachment #143225|application/mbox|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #44 from Jerry Zuo ---
Created attachment 143225
--> https://bugs.freedesktop.org/attachment.cgi?id=143225=edit
Patch for fixing MST reboot/poweroff sequence
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #43 from Jerry Zuo ---
We observed MST cannot light up in every reboot since 4.20, and we've already
got the reboot/poweroff sequence fixed. The fix will show up soon ...
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #42 from Jerry Zuo ---
We are currently looking at the startup issue now.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #41 from Shmerl ---
Same thing still happen with 5.0-rc2. Does anyone else experience this race
condition when the monitor goes to sleep right after boot? It is related to the
same setup (DisplayPort 1.2), since it's not happening
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #40 from Shmerl ---
Just tested kernel 5.0-rc1, the boot problem with monitor going to sleep is
still happening. Same workaround (turn the monitor off / on, switch to tty1,
restart sddm) helps.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #39 from Shmerl ---
FYI: the dmesg message fix should be already included in 5.0-rc1:
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #38 from Shmerl ---
(In reply to Jerry Zuo from comment #30)
> Please try the patch, and see if you can see reg_wait timeout
> dce110_stream_encoder_dp_blank()
Do you plan to backport at least this patch to 4.20.x?
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #37 from Shmerl ---
I wonder if it's some kind of distro specific race condition that happens
during boot. Happens to me in Debian testing (you can try reproducing it
there).
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #36 from Shmerl ---
(In reply to Jerry Zuo from comment #35)
> "startup monitor sleep regression". Please give more details on that. Thanks.
This behavior used to happen in the previous kernerls but got fixed at one
point. Now it's
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #35 from Jerry Zuo ---
"startup monitor sleep regression". Please give more details on that. Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #34 from Shmerl ---
I tested the patch. I don't see the error message now, but the startup monitor
sleep regression is still present. Is it a separate issue? I can open another
bug if needed.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #33 from Sibren Vasse ---
Just tried the patch, so far no reg_wait warnings. Looking good!
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=107978
Alex Deucher changed:
What|Removed |Added
Attachment #142834|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=107978
Alex Deucher changed:
What|Removed |Added
Attachment #142835|0 |1
is patch|
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #32 from Jerry Zuo ---
Created attachment 142835
--> https://bugs.freedesktop.org/attachment.cgi?id=142835=edit
Patch for dp_blank timeout
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #31 from Alex Deucher ---
(In reply to Jerry Zuo from comment #30)
> Please try the patch, and see if you can see reg_wait timeout
> dce110_stream_encoder_dp_blank()
Can you attach a non-zipped version?
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #30 from Jerry Zuo ---
Please try the patch, and see if you can see reg_wait timeout
dce110_stream_encoder_dp_blank()
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #29 from Jerry Zuo ---
Created attachment 142834
--> https://bugs.freedesktop.org/attachment.cgi?id=142834=edit
parch for reg_wait timeout for dce
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #28 from Shmerl ---
Not sure if it's related, but with 4.20.0-rc6 the regression when monitor goes
to sleep before reaching sddm is back. It's erratic, i.e. doesn't happen on
every boot. And I do see this REG_WAIT in dmesg when it
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #27 from Jerry Zuo ---
The dce110_stream_encoder_dp_blank timeout is something I am working on. It
doesn't break anything, but pretty annoying.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #26 from Shmerl ---
And I don't see ERROR* REG_WAIT anymore. I'm using latest Vega firmware.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #25 from Shmerl ---
Just built 4.20-rc5+. This is indeed fixed, and KWin Wayland session is finally
working with DisplayPort 1.2 enabled!
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #24 from Shmerl ---
Does KWin Wayland session work for you now? It was crashing also because of
this.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #23 from Sibren Vasse ---
Switching to tty now works for me , I still get the [drm:generic_reg_wait
[amdgpu]] *ERROR* REG_WAIT timeout 10us * 3000 tries -
dce110_stream_encoder_dp_blank line:944 message though
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #22 from Shmerl ---
Great news! Debian didn't get 4.20 rc kernels yet, but I can try building one
from source to test.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #21 from Sibren Vasse ---
(In reply to Jerry Zuo from comment #20)
> The fix is showing up since 4.20-rc5. Please give a try.
4.20-rc5 solves the problem for me!
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #20 from Jerry Zuo ---
The fix is showing up since 4.20-rc5. Please give a try.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #19 from Shmerl ---
This seem to commonly affect Dell monitors. Do they not follow DisplayPort 1.2
spec, or amdgpu is doing something incorrectly after all?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #18 from Robin ---
Same problem for me.
Using 2 identical DELL U2415 and a Radeon RX 580.
On Arch with 4.18.x Daisychainig both monitors worked like a charm.
After upgrading to 4.19 the monitors only work when I`m disableing DP1.2.
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #17 from Shmerl ---
(In reply to Nicholas Kazlauskas from comment #13)
>
> This does help narrow down the problem, thanks.
Is there any chance of fixing this in 4.20?
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #16 from Daniel Exner ---
I own a Dell U3415W also connected via DisplayPort and I have the same issue.
Worked like a charm in the past.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #15 from freedesk...@sibrenvasse.nl ---
I own a DELL U2414H and a U2913WM, and are daisy chained via DisplayPort. I'm
currently running into this issue.
A quick bisect gave this result:
# first bad commit:
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #14 from Shmerl ---
(In reply to Nicholas Kazlauskas from comment #13)
>
> If I had to guess I would say this is an issue specific to that monitor - DP
> 1.2 should generally work without issue.
It did work fine before in DP 1.2
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #13 from Nicholas Kazlauskas ---
(In reply to Shmerl from comment #12)
> @Nicholas Kazlauskas: does it help to identify the source of the problem?
If I had to guess I would say this is an issue specific to that monitor - DP
1.2
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #12 from Shmerl ---
@Nicholas Kazlauskas: does it help to identify the source of the problem?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=107978
--- Comment #11 from george ---
(In reply to Shmerl from comment #10)
> I just found something. My monitor - Dell U2413 has a setting for toggling
> DisplayPort 1.2. It was enabled until now. When I disable that setting, tty
> starts working!
>
https://bugs.freedesktop.org/show_bug.cgi?id=107978
Shmerl changed:
What|Removed |Added
Summary|[amdgpu] Switching to tty |[amdgpu] Switching to tty
53 matches
Mail list logo
