https://bugs.freedesktop.org/show_bug.cgi?id=102646
Martin Peres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #116 from tempel.jul...@gmail.com ---
Ahzo's patch is now merged in drm-next-5.5-wip branch:
https://cgit.freedesktop.org/~agd5f/linux/commit/?h=drm-next-5.5-wip=f659bb6dae58c113805f92822e4c16ddd3156b79
Big thanks for including!
--
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #115 from tempel.jul...@gmail.com ---
There is a new patch series that should allow memclock switching with same
refreshrate multi monitor setup:
https://lists.freedesktop.org/archives/amd-gfx/2019-August/038995.html
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #114 from Yuxuan Shui ---
(In reply to magist3r from comment #111)
> (In reply to tempel.julian from comment #110)
> > (In reply to magist3r from comment #109)
> > > My patch fixes a bug that breaks this behavior when OverDrive mask
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #113 from Adrian Przekwas ---
(In reply to tempel.julian from comment #108)
> I suppose also the Windows driver enforces maximum VRAM clock in your case
> all the time?
Windows users are reporting max vram clock if 2 (especially
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #112 from tempel.jul...@gmail.com ---
(In reply to magist3r from comment #111)
> It's not caused by my patch. Try to disable overdrive mask, revert the patch
> and you will see the same behavior.
There is dynamic VRAM clocking
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #111 from magist3r ---
(In reply to tempel.julian from comment #110)
> (In reply to magist3r from comment #109)
> > My patch fixes a bug that breaks this behavior when OverDrive mask is
> > enabled, nothing more.
>
> It
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #110 from tempel.jul...@gmail.com ---
(In reply to magist3r from comment #109)
> My patch fixes a bug that breaks this behavior when OverDrive mask is
> enabled, nothing more.
It unfortunately also forces my single display 1440p
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #109 from magist3r ---
(In reply to tempel.julian from comment #108)
> I suppose also the Windows driver enforces maximum VRAM clock in your case
> all the time? If that is true, it would definitely be a cool thing if we
> could get
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #108 from tempel.jul...@gmail.com ---
I suppose also the Windows driver enforces maximum VRAM clock in your case all
the time? If that is true, it would definitely be a cool thing if we could get
a patch into upstream to cover that
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #107 from magist3r ---
(In reply to reject5514 from comment #106)
> (In reply to magist3r from comment #105)
> > (In reply to reject5514 from comment #103)
> > > I have this problem on Archlinux 5.2.8-arch1-1-ARCH when connected 2
>
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #106 from reject5...@naver.com ---
(In reply to magist3r from comment #105)
> (In reply to reject5514 from comment #103)
> > I have this problem on Archlinux 5.2.8-arch1-1-ARCH when connected 2
> > monitors(1920x1080 @ 60Hz) and
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #105 from magist3r ---
(In reply to reject5514 from comment #103)
> I have this problem on Archlinux 5.2.8-arch1-1-ARCH when connected 2
> monitors(1920x1080 @ 60Hz) and amdgpu.ppfeaturemask=0x option
> enabled. Patch didn't
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #104 from Adrian Przekwas ---
The patch fixed the issue for me - Radeon RX 580, 1920x1080@75Hz, connected via
DisplayPort.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #103 from reject5...@naver.com ---
I have this problem on Archlinux 5.2.8-arch1-1-ARCH when connected 2
monitors(1920x1080 @ 60Hz) and amdgpu.ppfeaturemask=0x option enabled.
Patch didn't work for me.
My GPU is RX570.
--
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #102 from Maxim Ivanov ---
I have also compiled a kernel for myself with this patch and I can confirm it
is working correctly under amdgpu with my monitor (1920x1080 @ 75Hz) !
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #101 from Maxim Ivanov ---
(In reply to Ahzo from comment #97)
> Created attachment 144950 [details] [review]
> Patch to fix the problem
>
> TLDR: A script to reproduce and a patch to fix this problem are attached.
>
> The problem
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #100 from timm...@gmail.com ---
Ahzo, I also verified your patch using my monitor's max resolution/freq
2560x1440/75Hz (my preferred settings), on Manjaro 5.2.6-arch1-1-custom.
Thanks!
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #99 from tempel.jul...@gmail.com ---
Wow, finally a fix. It seems to work without issues for me now with 2560x1440
75Hz. You're a true hero! =)
Will test some higher refreshrates tomorrow, I can overclock my display to
100Hz or
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #98 from a...@tutanota.com ---
Created attachment 144951
--> https://bugs.freedesktop.org/attachment.cgi?id=144951=edit
Script to reproduce the problem
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
a...@tutanota.com changed:
What|Removed |Added
CC||a...@tutanota.com
--- Comment #97
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #96 from magist3r ---
(In reply to tempel.julian from comment #95)
> but it forces VRAM into highest state with amdgpu.dc=1
Yes, and this is what the kernel code does to prevent flickering. My patch is
only about doing the same
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #95 from tempel.jul...@gmail.com ---
This is probably what some people want, but it forces VRAM into highest state
with amdgpu.dc=1, while it has no effect with amdgpu.dc=0 (still flickers).
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #94 from magist3r ---
Created attachment 144565
--> https://bugs.freedesktop.org/attachment.cgi?id=144565=edit
proposed fix
FINALLY!!! I fixed the issue. A small patch with a fix is in the attachment.
Feel free to suggest a
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Seth Lorecanth changed:
What|Removed |Added
CC||issethloreca...@gmail.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #92 from magist3r ---
Just for the reference: screen flickering appears for me only with
amdgpu.ppfeaturemask=0x.
I think to flash my card with OC'ed BIOS and disable buggy OverDrive
completely.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=102646
magist3r changed:
What|Removed |Added
Attachment #144237|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #90 from tempel.jul...@gmail.com ---
Same issue:
patching file drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
Hunk #5 FAILED at 3943.
Hunk #6 succeeded at 3954 (offset -4 lines).
Hunk #7 succeeded at 4038 (offset -4 lines).
Hunk
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #89 from Alex Deucher ---
Try against this branch:
https://cgit.freedesktop.org/~agd5f/linux/log/?h=amd-staging-drm-next
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #88 from bmil...@gmail.com ---
(In reply to tempel.julian from comment #87)
> Applying the patch to 5.0, 5.1 and drm-next-5.2-wip fails with
>
> patching file drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
> Hunk #5 FAILED at
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #87 from tempel.jul...@gmail.com ---
Applying the patch to 5.0, 5.1 and drm-next-5.2-wip fails with
patching file drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c
Hunk #5 FAILED at 3943.
Hunk #6 succeeded at 3951 (offset -7 lines).
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #86 from evan.q...@amd.com ---
Can anyone give the attachment 144237 a try and let me know the result?
And if the issue still exists, please apply attachment 144238 also which can
provide more debug outputs.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #85 from evan.q...@amd.com ---
Created attachment 144238
--> https://bugs.freedesktop.org/attachment.cgi?id=144238=edit
Added some verbose debugs
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #84 from evan.q...@amd.com ---
Created attachment 144237
--> https://bugs.freedesktop.org/attachment.cgi?id=144237=edit
Clean up the fast uclk switch settings on SMU7 asics
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #83 from Tom B ---
I have a similar problem with my Radeon VII. My testing/experiments are
outlined here: https://bugs.freedesktop.org/show_bug.cgi?id=110510 sorry for
the long post!
However my bug seems slightly different albeit
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #82 from kyrotti...@yahoo.com ---
My solution, well more of a workaround and since I had this problem even with
default MESA that comes packaged with Kernel 5.05.XX, was to retune my monitor
to my GPU instead of letting my GPU try to
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #81 from tempel.jul...@gmail.com ---
I really hope this bug is not just not occurring with Vega because it uses
HBM2, so that we won't see it again with Navi GPUs which probably will use
GDDR5/6.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #80 from Garrett ---
well...even better solution: install Radeon-Profile
sudo su
cd /usr/bin
radeon-profile
boom...manual control with the radeon-profile GUI...something i've not once
seen mentioned in any tutorials. as long as
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #79 from Garrett ---
turns out if you just echo "0" for both sclk and mclk it fixes it at 75hz. cant
say for higher refresh rate, but my GPU is running stock now. what a weird
problem to have :/
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #78 from Garrett ---
(In reply to IvvanVG from comment #76)
> problem because of this commit
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/
> ?h=linux-4.18.y=d9ef158adf04b81772a7e9d682a054614ebac2fd
>
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #77 from Garrett ---
small change to a comment above:
sudo -i
echo "manual" > /sys/class/drm/card0/device/power_dpm_force_performance_level
echo "2" > /sys/class/drm/card0/device/pp_dpm_sclk (notice NOT pp_dpm_mclk)
allows my
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #76 from IvvanVG ---
problem because of this commit
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-4.18.y=d9ef158adf04b81772a7e9d682a054614ebac2fd
discussion on Ubuntu was here
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #75 from Antonio ---
Something I've noticed is that on my system, playing games doesn't flicker
(Bordelands 2 for example) when there's a lot of action/movement.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #74 from bmil...@gmail.com ---
(In reply to Bastian from comment #73)
> (In reply to Bastian from comment #69)
> > Distro/Kernel: Ubuntu 18.04.2/5.0.2
> > GPU AMD: Readon RX570 - Mesa 19.0
> > Display: Iiyama G23530HSU
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #73 from Bastian ---
(In reply to Bastian from comment #69)
> Distro/Kernel: Ubuntu 18.04.2/5.0.2
> GPU AMD: Readon RX570 - Mesa 19.0
> Display: Iiyama G23530HSU 75hz
> Desktop: Gnome
>
> video:
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #72 from tempel.jul...@gmail.com ---
Well, I just accepted to lose 2Hz and use a custom edid with 73Hz instead of
75.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #71 from bmil...@gmail.com ---
(In reply to George Scorer from comment #70)
> Building on julien tempel's workaround, here's a somewhat more complex
> script to manage the memory p-state jumps. It switches between low and high
>
https://bugs.freedesktop.org/show_bug.cgi?id=102646
George Scorer changed:
What|Removed |Added
Priority|low |high
Severity|minor
https://bugs.freedesktop.org/show_bug.cgi?id=102646
George Scorer changed:
What|Removed |Added
Priority|high|low
Severity|major
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #69 from Bastian ---
Distro/Kernel: Ubuntu 18.04.2/5.0.2
GPU AMD: Readon RX570 - Mesa 19.0
Display: Iiyama G23530HSU 75hz
Desktop: Gnome
video: https://www.youtube.com/watch?v=gNJ2kJ8hsHA
Have the same problem
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #68 from bmil...@gmail.com ---
At this point we need at least a workaround. Add a runtime kernel parameter
that keeps memory clock maxed up always, even after sleep/wake and resolution
changes.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Maxim Ivanov changed:
What|Removed |Added
Priority|medium |high
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #67 from Maxim Ivanov ---
Any updates on this? It seems like this bug has been around for quite a while
now.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #66 from Lefteris Chatzimparmpas ---
While the workaround with power_dpm_force_performance_level/pp_dpm_mclk works
for me, I found another way to stop the flickering, which I mention here in
case it helps debugging.
My monitor has
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #65 from bmil...@gmail.com ---
Please look at this devs, still no solution in mind?
--
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=102646
--- Comment #64 from marlo...@gmail.com ---
Just received 4.20 kernel in ArchLinux and got the same problem. High
performance profile or manual with max memory clock works around.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Michel Dänzer changed:
What|Removed |Added
CC|mic...@daenzer.net |
--- Comment #63 from Michel Dänzer
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #62 from Alex Deucher ---
(In reply to Scias from comment #60)
> I also noticed it doesn't happen if using dual/multiple screens. Looks like
> the vram clock is forced to the highest state in this case. Is this a normal
> behavior?
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #61 from Tim Writer ---
I'm out-of-office, returning on Jan. 3. I will be checking e-mail but responses
will be delayed.
Regards,
Tim
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #60 from Scias ---
Still happening on Linux-amd-staging 4.21 unfortunately. Even with
VariableRefresh/Freesync working.
I also noticed it doesn't happen if using dual/multiple screens. Looks like the
vram clock is forced to the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #59 from bmil...@gmail.com ---
4.20 released with this still, no fix in the way?
--
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=102646
--- Comment #58 from tempel.jul...@gmail.com ---
I've written a small script to only write into pp_dpm_mclk when it's not forced
into pstate 2:
#!/bin/bash
if ! cat /sys/class/drm/card0/device/pp_dpm_mclk |
grep -xqFe "2: 2250Mhz *"
then
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #57 from tempel.jul...@gmail.com ---
Instead of my usual DL-DVI display, I connected a Samsung C27H711 via Display
Port. It officially offers 2560x1440 75Hz and the very same flickering issue
occurs.
I suspect the Polaris Windows
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #56 from tempel.jul...@gmail.com ---
(In reply to bmilreu from comment #55)
> (In reply to Alex Deucher from comment #53)
> > Created attachment 142662 [details] [review] [review]
> > possible fix
> >
> > How about this patch?
>
>
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #55 from bmil...@gmail.com ---
(In reply to Alex Deucher from comment #53)
> Created attachment 142662 [details] [review]
> possible fix
>
> How about this patch?
for me it still flickers after sleep/wake @75hz unless I lock mclck
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Alex Deucher changed:
What|Removed |Added
CC||almo...@gmail.com
--- Comment #54 from
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #53 from Alex Deucher ---
Created attachment 142662
--> https://bugs.freedesktop.org/attachment.cgi?id=142662=edit
possible fix
How about this patch?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #52 from tempel.jul...@gmail.com ---
It still flickers with 4.21-wip build including this patch.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #51 from Alex Deucher ---
Does this patch help?
https://patchwork.freedesktop.org/patch/264781/
or this patch for older kernels:
https://bugs.freedesktop.org/attachment.cgi?id=142660
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #50 from tempel.jul...@gmail.com ---
Or just watch pp_dpm_mclk e.g. every second instead of constantly writing into
it, and write only in case of a change?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #49 from bmil...@gmail.com ---
(In reply to tempel.julian from comment #46)
> As a workaround, a timer job/script writing every few seconds might do the
> trick.
I tried a systemd timer but it floods my dmesg every time it triggers
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #47 from tempel.jul...@gmail.com ---
I had the chance to test three different GPUs:
RX 560: flickers
RX 580: flickers
RX Vega 56: doesn't flicker (and saves way more power than Polaris at the same
time)
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #48 from Tim Writer ---
I'm out-of-office for jury duty Nov. 19 - Dec. 11, returning on Dec. 12. I will
be checking e-mail daily and will endeavour to route important e-mail to my
team.
Regards,
Tim
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #46 from tempel.jul...@gmail.com ---
As a workaround, a timer job/script writing every few seconds might do the
trick.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #45 from bmil...@gmail.com ---
A temporary way to at least lock mclck forever would be great until this is
fixed. There is no sane way to do it permanently (some events switch it back to
auto, IE resolution changes and sleep/wake)
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #44 from tempel.jul...@gmail.com ---
I have this issue also without amdgpu.ppfeaturemask=0x.
amdgpu.dc 0 or 1 doesn't make a difference for me.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #43 from afm ---
OK really sorry for the noise on this ticket. It seems I did this to myself
with featuremask 0xfff . All is working without it. (i had been using
watman gtk)
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #42 from afm ---
Just to add. I noticed the corruption during the plymouth boot screen too.
After just waking the monitors from DPMS i got corruption until I echo'd 0
again.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #41 from afm ---
RX 570
1002:67df [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev
ef)
Kernel: 4.19.2-300.fc29.x86_64
1920x1080 59.93*+
Lots of strange flickering and black lines with dc=1. Strange ghosting
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #40 from tempel.jul...@gmail.com ---
Still having this issue with 2560 x 1440 @ 75Hz and latest 4.21-wip kernel.
Manually forcing a single VRAM clock state eliminates the flicker artifacts. As
soon as there is dynamic VRAM clocking
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #39 from bmil...@gmail.com ---
Another interesting info, even with amdgpu.dc=0 I get flickering @75hz.
Difference is the flickering immediatly stops when I switch back to 60hz (no
need to reboot or switch monitor off/on)
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #38 from bmil...@gmail.com ---
(In reply to Alex Deucher from comment #36)
> *** Bug 105300 has been marked as a duplicate of this bug. ***
https://bugs.freedesktop.org/show_bug.cgi?id=108322 - Also related.
When I tested 4.18
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #37 from bmil...@gmail.com ---
(In reply to Alex Deucher from comment #35)
> (In reply to bmilreu from comment #34)
> > The flickering issues I have with 75hz are gone after forcing profile to
> > high.
>
> The disables mclk
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Alex Deucher changed:
What|Removed |Added
CC||tempel.jul...@gmail.com
--- Comment #36
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #35 from Alex Deucher ---
(In reply to bmilreu from comment #34)
> The flickering issues I have with 75hz are gone after forcing profile to
> high.
The disables mclk switching by forcing the clocks to high. What modes and
refresh
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #34 from bmil...@gmail.com ---
Alex this bug looks like the same I reported here
https://bugs.freedesktop.org/show_bug.cgi?id=108322
The flickering issues I have with 75hz are gone after forcing profile to high.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #33 from Alex Deucher ---
The mclk switching needs to happen during the vblank period to avoid the
flickering. If there is not enough time in the vblank period, you may see
flickering outside of the blanking period. Can you figure
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #32 from Peter ---
(In reply to L.Y. Sim from comment #30)
> I have this issue on a 3840x1600 Acer XR382CQK with an RX560 with Kernel
> 4.18.5-1 on Manjaro.
>
> When I set the refresh rate to 75Hz, severe artifacts and flickering
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #31 from Timothy Pearson ---
(In reply to L.Y. Sim from comment #30)
> I have this issue on a 3840x1600 Acer XR382CQK with an RX560 with Kernel
> 4.18.5-1 on Manjaro.
>
> When I set the refresh rate to 75Hz, severe artifacts and
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #30 from L.Y. Sim ---
I have this issue on a 3840x1600 Acer XR382CQK with an RX560 with Kernel
4.18.5-1 on Manjaro.
When I set the refresh rate to 75Hz, severe artifacts and flickering appear.
Both
echo high >
https://bugs.freedesktop.org/show_bug.cgi?id=102646
--- Comment #29 from Hadrien Lacour ---
For what it's worth, the problem seems gone since I switched from 4.16.16 to
4.17.2 (with CONFIG_DRM_AMD_DC=y).
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Justin Mitzel changed:
What|Removed |Added
Summary|[dc] Screen flickering |Screen
https://bugs.freedesktop.org/show_bug.cgi?id=102646
Justin Mitzel changed:
What|Removed |Added
Summary|Screen flickering under |Screen
93 matches
Mail list logo