https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #105 from pub...@redaril.me ---
I have installed xf86-video-amdgpu 19.0.0 on Solus but the issue is still
present. I'm running Plasma 5.14 and kernel 4.20.10 with mesa 18.3.3. Is there
something else I should to fix the stuttering?
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #104 from Michel Dänzer ---
(In reply to Hans D from comment #103)
> With the latest xf86 DDX driver 3d works better in amdgpu.dc=0, but still
> lags, even though a built-in counter is showing high fps. Does amdgpu.dc=1
> improve
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #103 from Hans D ---
With the latest xf86 DDX driver 3d works better in amdgpu.dc=0, but still lags,
even though a built-in counter is showing high fps. Does amdgpu.dc=1 improve
3d performance that much?
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #102 from tempel.jul...@gmail.com ---
Is that with latest git version of the xf86 DDX driver, including the PR Michel
posted?
I had subpar game performance (looked like half of the fps) too without vsync
the last time I checked
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #101 from Hans D ---
For me the TearFree Option works flawlessly with amdgpu.dc=0 on 5.0rc2 and
4.20.1, but 3d games lag. With amdgpu.dc=1 there are some slight hiccups every
2-3 seconds (Firefox`s autoscrolling, video playback
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #100 from Brandon Wright ---
(In reply to tempel.julian from comment #99)
> Does the trick for me too, TearFree with amdgpu.dc=0 seems to be completely
> smooth now. Delay / input latency seems to be the same between amdgpu.dc=1
>
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #99 from tempel.jul...@gmail.com ---
Does the trick for me too, TearFree with amdgpu.dc=0 seems to be completely
smooth now. Delay / input latency seems to be the same between amdgpu.dc=1 and
0, I suppose this is as low as it can be
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #98 from Michel Dänzer ---
(In reply to Brandon Wright from comment #95)
> For me, at least, it hiccups regularly every second and introduces
> noticeable latency. With dc=1 it's smooth
Thanks, I was able to reproduce the hiccups
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #97 from Michel Dänzer ---
(In reply to tempel.julian from comment #96)
> I also noticed that sometimes switching between Vulkan fullscreen windows
> (radv) and desktop can break TearFree, it needs to be reactivated then. I
>
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #96 from tempel.jul...@gmail.com ---
Yep, that's my observation as well (no compositor vsync enbled at the same
time).
I also noticed that sometimes switching between Vulkan fullscreen windows
(radv) and desktop can break TearFree,
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #95 from Brandon Wright ---
(In reply to Michel Dänzer from comment #94)
> (In reply to tempel.julian from comment #88)
> > (TearFree however doesn't work well in general without amdgpu.dc=1).
>
> Can you elaborate on that? Maybe
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #94 from Michel Dänzer ---
(In reply to tempel.julian from comment #88)
> (TearFree however doesn't work well in general without amdgpu.dc=1).
Can you elaborate on that? Maybe file another report on it.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=106175
tempel.jul...@gmail.com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #92 from tempel.jul...@gmail.com ---
This is the commit with which the stutter is introduced:
https://gitlab.freedesktop.org/xorg/driver/xf86-video-amdgpu/commit/0d60233d26ec70d4e1faa343b438e33829c6d5e4
(But it seems amdgpu.dc=1
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #91 from tempel.jul...@gmail.com ---
I suppose I could narrow down the culprit:
The issue does not occur with stable version 18.1.0 of xf86-video-amdgpu DDX
driver.
But it does occur with both xorg modesetting and latest git commit
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #90 from tempel.jul...@gmail.com ---
Created attachment 143081
--> https://bugs.freedesktop.org/attachment.cgi?id=143081=edit
new xorg.0 log for reopened cursor issue
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=106175
tempel.jul...@gmail.com changed:
What|Removed |Added
Attachment #138987|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #88 from tempel.jul...@gmail.com ---
Well, there's no compositor to blame, as the issue also occurs with just
TearFree enabled without any compositor. Then you just have to avoid moving
another window on top of the browser window, as
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #87 from Brandon Wright ---
It's important to distinguish between when the compositor and application
desync and when there's actually a driver hiccup.
If the compositor and application swaps get switched around briefly, it'll
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #86 from tempel.jul...@gmail.com ---
Thanks for trying to reproduce.
Hm, that leaves me clueless. It's 100% reproducible here and I tried things
like forcing high performance profile, using plain 60Hz edid and disabling
overclock,
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #85 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #82)
> Could you please try the following?
>
> -disable Plasma compositing with Ctr + Alt + F12 (or in the compositor
> settings and log out and in again)
>
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #84 from Michel Dänzer ---
(In reply to Nicholas Kazlauskas from comment #81)
> As for the difference between dc=1 and dc=0, that might just be a difference
> in behavior on the DRM level for atomic vs non-atomic drivers. Or a
>
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #83 from tempel.jul...@gmail.com ---
Edit: Sorry, I meant disabling KWin compositing via Shift + Alt F12, not Ctrl.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #82 from tempel.jul...@gmail.com ---
Could you please try the following?
-disable Plasma compositing with Ctr + Alt + F12 (or in the compositor settings
and log out and in again)
-get the latest Compton release by yshui:
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #81 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #80)
> It seems like the issue is actually not 100% resolved (linux 5.0-rc1).
> The moving of windows is free of stutter now, but moving of windows can
> still
https://bugs.freedesktop.org/show_bug.cgi?id=106175
tempel.jul...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #79 from bmil...@gmail.com ---
any chance to backport the last version of the patch to 4.20?
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing
https://bugs.freedesktop.org/show_bug.cgi?id=106175
tempel.jul...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #77 from bmil...@gmail.com ---
@Nicholas Kazlauskas
is there anything important in the new patch vs the first one? it fails a hunk
on 4.19 for me
thanks for submiting it to amd-gfx
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #76 from Brandon Wright ---
https://patchwork.freedesktop.org/series/53589/
A new patch has been submitted. So it's in the pipeline for inclusion now.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #75 from tempel.jul...@gmail.com ---
Any update, please?
--
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=106175
--- Comment #74 from Brandon Wright ---
Is anyone from the AMD driver team still following this?
Could we please have a review of Nicholas's patch and try to get it into 4.20?
It's not that disruptive code-wise, but it makes a big smoothness
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #73 from tempel.jul...@gmail.com ---
Yeah, I'd be extremely disappointing if this wouldn't land before linux 4.21
DRM merging window closes.
Like I already said, I think this is even worth getting backported to older
kernels, as I'd
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #72 from Brandon Wright ---
(In reply to bmilreu from comment #71)
> @Nicholas Kazlauskas
> any reason not to push this fix to staging or next?
I agree. This will reduce stuttering for everyone, especially those who think
the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #71 from bmil...@gmail.com ---
@Nicholas Kazlauskas
any reason not to push this fix to staging or next?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106175
Brandon Wright changed:
What|Removed |Added
Attachment #142558|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #69 from tempel.jul...@gmail.com ---
(In reply to bmilreu from comment #68)
> try 0001-drm-amd-display-Add-fast-path-for-legacy-cursor-plan.patch
That one works, also with modesetting driver.
Regarding your question if modesetting
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #68 from bmil...@gmail.com ---
(In reply to tempel.julian from comment #67)
> Just wanted to note that applying
> [PATCH 1/2] drm/amd/display: Use private obj helpers for dm_atomic_state
> [PATCH 2/2] drm/amd/display: Remove wait for
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #67 from tempel.jul...@gmail.com ---
Just wanted to note that applying
[PATCH 1/2] drm/amd/display: Use private obj helpers for dm_atomic_state
[PATCH 2/2] drm/amd/display: Remove wait for hw/flip done in atomic check
does not
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #66 from Brandon Wright ---
(In reply to bmilreu from comment #65)
> Is there an easy way to backport this to 4.19 mainline? Would be very useful
> to integrate the fix into stable kernels.
>
> As it is currently it wont work on
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #65 from bmil...@gmail.com ---
(In reply to Nicholas Kazlauskas from comment #64)
> Created attachment 142574 [details] [review]
> 0001-drm-amd-display-Add-fast-path-for-legacy-cursor-plan.patch
>
> This patch is similar to the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #64 from Nicholas Kazlauskas ---
Created attachment 142574
--> https://bugs.freedesktop.org/attachment.cgi?id=142574=edit
0001-drm-amd-display-Add-fast-path-for-legacy-cursor-plan.patch
This patch is similar to the async_update
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #63 from bmil...@gmail.com ---
(In reply to Brandon Wright from comment #62)
> (In reply to tempel.julian from comment #61)
> > I just noticed that it works fine with xf86-video-amdgpu driver, but with
> > modesetting driver, xorg or
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #62 from Brandon Wright ---
(In reply to tempel.julian from comment #61)
> I just noticed that it works fine with xf86-video-amdgpu driver, but with
> modesetting driver, xorg or the driver freezes when starting/logging in. Not
>
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #61 from tempel.jul...@gmail.com ---
Thanks a lot @ Brandon Wright, your patch really does the trick. I also totally
agree on your opinion that it should be mainlined as at least a temporary
solution (and also get backported to older
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #60 from Brandon Wright ---
> There are larger problems within amdgpu_dm's commit tail that if addressed
> should resolve this issue for compton I'd imagine.
Honestly, I don't care about compton. I don't think you realize the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #59 from bmil...@gmail.com ---
(In reply to Nicholas Kazlauskas from comment #58)
> (In reply to Brandon Wright from comment #55)
> > Created attachment 142558 [details] [review] [review]
> > Patch that "fixes" the problem.
> >
> >
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #58 from Nicholas Kazlauskas ---
(In reply to Brandon Wright from comment #55)
> Created attachment 142558 [details] [review]
> Patch that "fixes" the problem.
>
> I've attached a patch that fixes the problem for me. It copies
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #57 from bmil...@gmail.com ---
@Brandon Wright
Sorry for double posting, but I think if you send the patch to amd-gfx
mailing-list directly it might get reviewed faster.
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #56 from bmil...@gmail.com ---
(In reply to Brandon Wright from comment #55)
> Created attachment 142558 [details] [review]
> Patch that "fixes" the problem.
>
> I've attached a patch that fixes the problem for me. It copies parts
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #55 from Brandon Wright ---
Created attachment 142558
--> https://bugs.freedesktop.org/attachment.cgi?id=142558=edit
Patch that "fixes" the problem.
I've attached a patch that fixes the problem for me. It copies parts from the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #54 from tempel.jul...@gmail.com ---
You should btw. also set CPU clock governor to either acpi-cpufreq performance
or intel_pstate performance, since governors like powersave, ondemand or
schedutil can already cause severe
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #53 from bmil...@gmail.com ---
(In reply to rropid from comment #45)
> (In reply to bmilreu from comment #43)
> > If devs want an easy test case, use these links for reproducing it in
> > chromium:
> >
> >
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #52 from Brandon Wright ---
Ok, I think I understand what's going on. Forgive me if this sounds stupid, I'm
looking at the DRM code for the first time.
The old KMS interface uses what's flagged as "legacy" cursor updates. These are
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #51 from Alex Deucher ---
DC uses the atomic KMS interface, the old code uses the legacy KMS interface.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #50 from Brandon Wright ---
> I have this issue too, disabling page flipping fixes it for me on my vega10.
> It started with 4.16rc1 IIRC
Negative. I checked back as far as the DC/DAL was integrated (4.15) and it's
been there from
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #49 from Brandon Wright ---
I'm going to speculate that maybe the hardware cursor updates are triggering an
update to the vsync timestamp counter or msc that's incorrect and throwing off
the timing.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #48 from tempel.jul...@gmail.com ---
With amdgpu.dc=0, TearFree works as expected for me (no tearing without
compositor, scrolling in Firefox windowed is free of stutter, no issues with
compositor vsync either).
I think we should
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #47 from Michel Dänzer ---
FWIW, note that TearFree can be toggled at runtime using the RandR output
property of the same name. At its default value "auto", TearFree is
automatically enabled for an output using rotation / scaling /
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #46 from Brandon Wright ---
I've never run TearFree, so that's not the case here. My Xorg config is similar
to yours, just amdgpu and DRI 3. I did have an extra section to use evdev
instead of libinput, but I tried removing that and
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #45 from rro...@gmail.com ---
(In reply to bmilreu from comment #43)
> If devs want an easy test case, use these links for reproducing it in
> chromium:
>
> https://www.vsynctester.com/
> https://www.testufo.com/photo
>
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #44 from Brandon Wright ---
You're too late, I already tried it. But as you say, there's no improvement.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #43 from bmil...@gmail.com ---
(In reply to Brandon Wright from comment #42)
> This is pretty serious. Just moving the mouse cursor around while something
> slightly GPU-heavy is running at 60hz can produce frame-skipping.
>
> I
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #42 from Brandon Wright ---
This is pretty serious. Just moving the mouse cursor around while something
slightly GPU-heavy is running at 60hz can produce frame-skipping.
I switched the display core off with amdgpu.dc=0 and
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #41 from bmil...@gmail.com ---
Guys, please take a closer look at this, its actually a lot worse than what OP
describes and affect a lot of other use cases, vsync is a vital feature for any
kind of PC activity, literally everything
https://bugs.freedesktop.org/show_bug.cgi?id=106175
Michel Dänzer changed:
What|Removed |Added
CC||nicholas.kazlaus...@amd.com
---
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #39 from gr...@sub.red ---
(In reply to Michel Dänzer from comment #34)
>
> Right, you'd have to disable TearFree as well.
Then I think the logs should represent that, even when the manpage tells me
that tearfree is using page
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #38 from bmil...@gmail.com ---
(In reply to tempel.julian from comment #37)
> I think software cursor would also be unusable even if it left pageflipping
> on. It causes nasty issues like flickering cursor or other visual corruption.
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #37 from tempel.jul...@gmail.com ---
I think software cursor would also be unusable even if it left pageflipping on.
It causes nasty issues like flickering cursor or other visual corruption.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #36 from bmil...@gmail.com ---
So, to help find the origin of the issue, there are a few options that get rid
of stutter when compositing:
1 - amdgpu.dc=0 - The old DC seems unaffected by the bug.
2 - SWcursor on - Unaffected by bug
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #35 from bmil...@gmail.com ---
(In reply to Michel Dänzer from comment #31)
> Note that SWcursor completely disables page flipping, at least with
> xf86-video-amdgpu, because the two things are fundamentally incompatible
> with each
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #34 from Michel Dänzer ---
(In reply to tempel.julian from comment #33)
> I suppose TearFree forces pageflipping regardless, as we don't see any
> tearing with that configuration.
Right, you'd have to disable TearFree as well. Can
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #33 from tempel.jul...@gmail.com ---
I suppose TearFree forces pageflipping regardless, as we don't see any tearing
with that configuration.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #32 from gr...@sub.red ---
(In reply to Michel Dänzer from comment #31)
> Does only disabling page flipping also avoid the problem?
Not from what I can tell.
> Option "EnablePageFlip" "off"
results in
>[ 35496.178] (II)
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #31 from Michel Dänzer ---
Note that SWcursor completely disables page flipping, at least with
xf86-video-amdgpu, because the two things are fundamentally incompatible with
each other. Does only disabling page flipping also avoid
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #30 from bmil...@gmail.com ---
https://github.com/yshui/compton/issues/25 - related to this issue
Some tests me and others did in compton shows there is some relation with vsync
issues and the HW cursor. When I turn swcursor on in
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #29 from tempel.jul...@gmail.com ---
I gave it a try again: Unfortunately, there are no improvements to report with
latest 4.21-wip vs. the status of some months ago.
I really wonder how you can have trouble reproducing. This is not
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #28 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #27)
> Is this commit related to it?
> https://lists.freedesktop.org/archives/amd-gfx/2018-October/027726.html
It shouldn't be. You would likely be
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #27 from tempel.jul...@gmail.com ---
Is this commit related to it?
https://lists.freedesktop.org/archives/amd-gfx/2018-October/027726.html
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #26 from gr...@sub.red ---
Yes, I'm using DP (required for 144 Hz with WQHD).
However, I just reproduced the issue on a 19" monitor with 1280x1024 at 60 Hz
and with a cheap old mouse with a 100 Hz polling rate. The issue is no
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #25 from tempel.jul...@gmail.com ---
It doesn't seem to be related to a certain GCN generation, as there are exactly
matching reports of at least Hawaii, Polaris 10/11 and Vega 10 (probably also
Fiji).
It probably neither is related
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #24 from Jordan L ---
The challenge here is that we still can't seem to reproduce this internally on
any of our setups. Can anyone identify a commonality in setup to help isolate
the reproducing behaviour?
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #23 from tempel.jul...@gmail.com ---
If I bought Vega, Raven Ridge or, in the future, Navi, I'd be really annoyed by
this bug because I had to turn off page flipping, resulting in unacceptable
tearing. :(
Could we please get an
https://bugs.freedesktop.org/show_bug.cgi?id=106175
gr...@sub.red changed:
What|Removed |Added
CC||gr...@sub.red
--- Comment #22 from
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #21 from tempel.jul...@gmail.com ---
Don't want to nag at anyone, but this bug still makes DC unusable for me and
thus is a real dealbreaker. Does implementing a fix for it require lots of
efforts?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #20 from Michel Dänzer ---
Note that the ioctls don't literally run "in parallel"; both ioctls are called
by the Xorg main thread, so they can't preempt each other. What I mean is that
any number of cursor ioctls can happen while a
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #19 from Michel Dänzer ---
(In reply to David Francis from comment #18)
> My hypothesis is that has something to do with the mouse polling rate.
What is that hypothesis based on?
The kernel is supposed to be able to process any
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #18 from David Francis ---
My hypothesis is that has something to do with the mouse polling rate.
Could you set the polling rate to 125 Hz (8 ms) and see if the problem
persists?
This information will help us troubleshoot the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #17 from Michel Dänzer ---
https://patchwork.freedesktop.org/patch/227925/ might provide inspiration for
how this could be solved.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #16 from ejr.ph...@gmail.com ---
I have this issue too, disabling page flipping fixes it for me on my vega10. It
started with 4.16rc1 IIRC
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #15 from tempel.jul...@gmail.com ---
I just tried that option with the xf86 amdgpu DDX driver and as expected,
stuttering disappears in exchange for tearing close to the very top of the
screen.
I'm really glad you could confirm the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #14 from Michel Dänzer ---
(In reply to tempel.julian from comment #13)
> So there might be an actual connection to pageflipping?
Yeah, the problem seems to be a bad interaction between page flipping and
cursor
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #13 from tempel.jul...@gmail.com ---
When I use modesetting driver with Option "PageFlip" "false", the stuttering is
gone (however, as expected tearing is not fully prevented anymore).
So there might be an actual connection to
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #12 from tempel.jul...@gmail.com ---
Latest drm-next-4.18-wip aa1bce17d841a362d40da940487e13affe4c7b3b still shows
the same behavior.
I'd be happy if more users would comment on this, since it makes use of
amdgpu.dc totally
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #11 from tempel.jul...@gmail.com ---
I noticed that this issue also exists apart from Xorg compositors.
When I run Serious Sam: Fusion (both OpenGL and Vulkan) in fullscreen (no Xorg
compositor enabled in the background), the mouse
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #10 from Mike Bendel ---
I have the same issue. For me amdgpu.dc=0 does not really fix it either. I have
a 3840x1600 monitor running at 75 Hz. This is the different behavior I noticed
when toggling the DC setting:
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #9 from tempel.jul...@gmail.com ---
I got them too. Before those commits, my issue was way more severe. It's still
really nasty stutter though.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #8 from Mariusz Ceier ---
I had these patches in the kernel tree - mine is from 22nd April, while these
patches were committed on 12th April.
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #7 from Harry Wentland ---
Does your kernel tree have the following patches?
90fef6476917 Revert "drm/amd/display: disable CRTCs with NULL FB on their
primary plane (V2)"
c7bd22893408 Revert
https://bugs.freedesktop.org/show_bug.cgi?id=106175
--- Comment #6 from Mariusz Ceier ---
I forgot about - I have Radeon Fury X graphics card.
--
You are receiving this mail because:
You are the assignee for the bug.___
1 - 100 of 107 matches
Mail list logo