https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #86 from tempel.jul...@gmail.com ---
While the Gallium performance overlay clearly shows a spike in the game's GPU
render time, I'm fairly certain it doesn't exist in the actual display output.
It's not limited to the character
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #85 from tempel.jul...@gmail.com ---
Thanks for the new Proton release including your fix (didn't realize you are
the release manager :) ). As far as I can judge until now, the result is good
enough in practice. There is this this
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #84 from Andrew Eikum ---
If one call every five seconds is causing a problem, surely it's not Wine's
bug, right?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #83 from tempel.jul...@gmail.com ---
Andrew, with your patch the issue is still there in a weak shape:
When I open the inventory in TES IV Oblivion, don't move the cursor for some
seconds and then move it again, there is always a
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #82 from tempel.jul...@gmail.com ---
(In reply to Andrew Eikum from comment #81)
> I've submitted a patch to Wine to throttle our calls to XResetScreenSaver to
> once every five seconds: https://source.winehq.org/patches/data/169958
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #81 from Andrew Eikum ---
(In reply to Nicholas Kazlauskas from comment #74)
> (In reply to Michel Dänzer from comment #73)
> > Looks like some client repeatedly calls XForceScreenSaver (probably to
> > prevent the monitors from
https://bugs.freedesktop.org/show_bug.cgi?id=110659
tempel.jul...@gmail.com changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #79 from Pierre-Eric Pelloux-Prayer
---
(In reply to Michel Dänzer from comment #76)
> (In reply to tempel.julian from comment #75)
> > Is it possible that Wine or the affected programs in Wine are the clients
> > that are at fault
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #78 from Michel Dänzer ---
(In reply to tempel.julian from comment #77)
> I turned DPMS off in Xorg config which leaves the issue unchanged. Is this
> to be expected?
Yeah, this isn't directly related to X's DPMS functionality.
--
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #77 from tempel.jul...@gmail.com ---
(In reply to Michel Dänzer from comment #76)
> Certainly. It looks like the intention is to prevent the monitors from
> entering power saving mode.
I turned DPMS off in Xorg config which leaves
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #76 from Michel Dänzer ---
(In reply to tempel.julian from comment #75)
> Is it possible that Wine or the affected programs in Wine are the clients
> that are at fault for this?
Certainly. It looks like the intention is to prevent
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #75 from tempel.jul...@gmail.com ---
Is it possible that Wine or the affected programs in Wine are the clients that
are at fault for this?
As it happens with my Arch Plasma setup and also a fresh Fedora Gnome
installation, it seems
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #74 from Nicholas Kazlauskas ---
(In reply to Michel Dänzer from comment #73)
> Looks like some client repeatedly calls XForceScreenSaver (probably to
> prevent the monitors from blanking), which results in the DPMS property
>
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #73 from Michel Dänzer ---
Looks like some client repeatedly calls XForceScreenSaver (probably to prevent
the monitors from blanking), which results in the DPMS property getting re-set
over and over. Nicholas, maybe the kernel could
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #72 from tempel.jul...@gmail.com ---
Created attachment 145280
--> https://bugs.freedesktop.org/attachment.cgi?id=145280=edit
2nd gdb backtrace log, now with debug symbols
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #71 from tempel.jul...@gmail.com ---
Hope this helps:
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #70 from Michel Dänzer ---
(In reply to tempel.julian from comment #68)
> I did it, but it stopped after hitting the two breakpoints the first time
> without me having moved the mouse at all. I suppose this isn't enough? Would
> it
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #69 from tempel.jul...@gmail.com ---
Created attachment 145278
--> https://bugs.freedesktop.org/attachment.cgi?id=145278=edit
1st gdb log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #68 from tempel.jul...@gmail.com ---
I did it, but it stopped after hitting the two breakpoints the first time
without me having moved the mouse at all. I suppose this isn't enough? Would it
be possible to provide me with a short
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #67 from tempel.jul...@gmail.com ---
(In reply to Michel Dänzer from comment #66)
> They still use page flipping though, similar to TearFree. Which Wayland
> compositor(s) have you tried?
I have tried a Wayland Gnome and Plasma
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #66 from Michel Dänzer ---
(In reply to tempel.julian from comment #65)
> Since this commit, the modesetting driver shows the same behavior as
> xf86-video-amdgpu:
> https://gitlab.freedesktop.org/xorg/xserver/commit/
>
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #65 from tempel.jul...@gmail.com ---
@Nicholas
Since this commit, the modesetting driver shows the same behavior as
xf86-video-amdgpu:
https://gitlab.freedesktop.org/xorg/xserver/commit/f0d78b47ac49977a6007f5fe081f00c6eb19a12e
So,
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #64 from tempel.jul...@gmail.com ---
I can try that. But I really wonder why there are differences between systems
showing the issue or not.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #63 from Michel Dänzer ---
Can you find out which property is getting set? If there's no (easy) way to get
that out of the kernel, one possibility is to (from another machine via SSH)
attach gdb to the Xorg process while an affected
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #62 from tempel.jul...@gmail.com ---
I could reproduce the issue on a system with a Radeon RX 5700 XT Navi 10 GPU +
drm-next kernel in Hitman 2. Really devastating.
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #61 from tempel.jul...@gmail.com ---
Did I get it right that modesetting DDX and xwayland aren't affected by this
problem because xf86-video-amdgpu technically differs in some substantial
aspects?
Apart from FreeSync (which is
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #60 from tempel.jul...@gmail.com ---
I've applied your patch to current drm-next branch head (tag
drm-next-5.4-2019-08-30), situation is still unchanged. I've also attached a
new log with it. This time I ran Oblivion with Gallium
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #59 from tempel.jul...@gmail.com ---
Created attachment 145222
--> https://bugs.freedesktop.org/attachment.cgi?id=145222=edit
debug dmesg output for patch applied to drm-next
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #58 from tempel.jul...@gmail.com ---
Created attachment 145209
--> https://bugs.freedesktop.org/attachment.cgi?id=145209=edit
new ioctl log with patch applied
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #57 from tempel.jul...@gmail.com ---
Unfortunately unchanged :( . New log:
--
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=110659
--- Comment #56 from Nicholas Kazlauskas ---
It seems to be the frequent calls to DRM_IOCTL_MODE_SETPROPERTY that's causing
the issue but I'm not entirely sure what specifically it's trying to set that's
doing this.
This probably isn't
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #55 from tempel.jul...@gmail.com ---
Created attachment 145208
--> https://bugs.freedesktop.org/attachment.cgi?id=145208=edit
hopefully extended dmesg ioctl log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #54 from tempel.jul...@gmail.com ---
Not sure if it was helpful, but I tried setting log_buf_len=131072 and ran
sleep 5s && dmesg in background while I was provoking the issue in Oblivion
(dmesg-ioctl_2.log).
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #53 from tempel.jul...@gmail.com ---
Hm, it seems that maximum log size isn't enough for even one whole second?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #52 from tempel.jul...@gmail.com ---
Created attachment 145207
--> https://bugs.freedesktop.org/attachment.cgi?id=145207=edit
dmesg ioctl log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #51 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #50)
> Are we already out of options for debug output? :)
Might help to see what IOCTLs are being specifically called by userspace. I
think you can enable
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #50 from tempel.jul...@gmail.com ---
Are we already out of options for debug output? :)
--
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=110659
--- Comment #49 from tempel.jul...@gmail.com ---
Instead of my Arch installation, I tried a fresh Fedora 30 Workstation Gnome
installation. It shows the same behavior, so I think we can rule out a
packaging issue.
Too bad, this issue makes me
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #48 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #47)
> I got a new 1440p 144 Hz FreeSync display, and as expected, the issue is
> unchanged with it.
>
> With it, I've created a new debug dmesg log for
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #47 from tempel.jul...@gmail.com ---
I got a new 1440p 144 Hz FreeSync display, and as expected, the issue is
unchanged with it.
With it, I've created a new debug dmesg log for render stutter in Oblivion,
this time with your patch
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #46 from tempel.jul...@gmail.com ---
Created attachment 145152
--> https://bugs.freedesktop.org/attachment.cgi?id=145152=edit
new debug dmesg log saved after running Oblivion with drm-next kernel
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #45 from tempel.jul...@gmail.com ---
Created attachment 145140
--> https://bugs.freedesktop.org/attachment.cgi?id=145140=edit
new dmesg log with debug patch applied after starting Hitman 2
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #44 from tempel.jul...@gmail.com ---
I applied the patch to linux 5.2 (among
0001-drm-amd-display-Allow-fast-updates-again-for-swappin.patch) and as
expected, gamma adjustments have stopped working.
Unfortunately, the games still
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #43 from Nicholas Kazlauskas ---
Created attachment 145139
--> https://bugs.freedesktop.org/attachment.cgi?id=145139=edit
0001-drm-amd-display-Test-patch-for-disabling-color-adjus.patch
>From your video it looks like something is
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #42 from tempel.jul...@gmail.com ---
(In reply to Nicholas Kazlauskas from comment #39)
> Disabling the compositor doesn't make a difference as far as stuttering goes
> for Hitman 2's DXVK - I don't see any commits in the log that
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #41 from tempel.jul...@gmail.com ---
Created attachment 145138
--> https://bugs.freedesktop.org/attachment.cgi?id=145138=edit
debug dmesg.log after running Hitman 2 with the issue
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #40 from tempel.jul...@gmail.com ---
Created attachment 145137
--> https://bugs.freedesktop.org/attachment.cgi?id=145137=edit
video demonstrating the issue in Hitman 2 (different to Oblivion/Skyrim)
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #39 from Nicholas Kazlauskas ---
Disabling the compositor doesn't make a difference as far as stuttering goes
for Hitman 2's DXVK - I don't see any commits in the log that are lock the
connector and all the planes.
I don't have
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #38 from tempel.jul...@gmail.com ---
Huh, that seems suspicious. I'm not aware of any such a tool which would be
active for me all the time. I had redshift installed, but it wasn't running in
background, so not surprisingly
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #37 from Nicholas Kazlauskas ---
Are you running a color management tool in the background?
The difference between my setup and yours is that there isn't anything locking
the connectors hundreds of times per second and performing
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #36 from tempel.jul...@gmail.com ---
The log now starts at [ 2788.164016], I hope nothing important is cut out. Else
I'd have to recheck my log size limits.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #35 from tempel.jul...@gmail.com ---
Created attachment 145119
--> https://bugs.freedesktop.org/attachment.cgi?id=145119=edit
debug dmesg.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #34 from tempel.jul...@gmail.com ---
Thank you for being still with me on this.
I've downgraded to stock packages provided by Arch stable repository, which is:
xorg-server 1.20.5
xf86-video-amdgpu 19.0.1
mesa 19.1.4
stock (read:
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #33 from Nicholas Kazlauskas ---
I haven't seen anything like the video in my testing. It also doesn't seem to
happen every time so I'm wondering if something else is going on in the
background that's issuing atomic commits.
Do you
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #32 from tempel.jul...@gmail.com ---
Created attachment 145118
--> https://bugs.freedesktop.org/attachment.cgi?id=145118=edit
issue demonstrated with D9VK frametime graph in game Oblivion
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #31 from tempel.jul...@gmail.com ---
Created attachment 145117
--> https://bugs.freedesktop.org/attachment.cgi?id=145117=edit
new dmesg log with staging-drm-next kernel default parameters
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #30 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #29)
> The patches by Nicholas are now merged in drm-next-5.4 branch (tested with
> recent commit that bases the branch on 5.3-rc3), but the mouse input issue
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #29 from tempel.jul...@gmail.com ---
The patches by Nicholas are now merged in drm-next-5.4 branch (tested with
recent commit that bases the branch on 5.3-rc3), but the mouse input issue in
certain games is still unaffected.
I was
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #28 from tempel.jul...@gmail.com ---
Situation is still unchanged with latest drm-next-5.4-wip kernel branch from a
few minutes ago. :(
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #27 from tempel.jul...@gmail.com ---
(In reply to Michel Dänzer from comment #26)
> It's a kernel issue, not an xf86-video-amdgpu one.
Thanks for clarifying.
I could also reproduce this issue with Doom OpenGL in Steam Play/Proton
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #26 from Michel Dänzer ---
(In reply to tempel.julian from comment #25)
> I also reported the bug to the wine devs (still I think this is rather a bug
> of xf86-video-amdgpu):
It's a kernel issue, not an xf86-video-amdgpu one.
--
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #25 from tempel.jul...@gmail.com ---
Applying this MR and disabling HW cursor "fixes" the mouse skipping in the menu
of Hitman 2 (as there is a cursor visible and thus pageflipping is turned off):
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #24 from tempel.jul...@gmail.com ---
I've mentioned kwin-lowlatency in this ticket:
https://bugs.freedesktop.org/show_bug.cgi?id=108917#add_comment
It can be used as some kind of workaround for this wine issue, as the stutter
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #23 from tempel.jul...@gmail.com ---
Any news on this? I'd really like to have this sorted out before I
wholeheartedly recommended Navi for Linux gaming.
I can imagine that Navi causes a ton of work, but still this issue is painful.
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #22 from tempel.jul...@gmail.com ---
The Witcher 3 is affected as well (a bit less obvious, but still quite bad vs.
modesetting or amdgpu.dc=0). So, it seems this is a real dealbreaker for
playing games on Linux, which imho justifies
https://bugs.freedesktop.org/show_bug.cgi?id=110659
tempel.jul...@gmail.com changed:
What|Removed |Added
Priority|medium |high
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #21 from tempel.jul...@gmail.com ---
I'm open to trying out other patches, e.g. concerning double buffering for the
cursor. :)
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #20 from tempel.jul...@gmail.com ---
I forgot that I patched this PR into my Xserver:
https://gitlab.freedesktop.org/xorg/xserver/merge_requests/36
It is responsible for the blocked gamma adjustment and the better desktop
window
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #19 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #18)
> Huh, with modesetting driver, those patches eliminate the stutter when new
> windows are shown. Does the xf86-video-amdgpu driver need adjustments for
>
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #18 from tempel.jul...@gmail.com ---
Huh, with modesetting driver, those patches eliminate the stutter when new
windows are shown. Does the xf86-video-amdgpu driver need adjustments for this?
However, turning on nightlight in Plasma
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #17 from tempel.jul...@gmail.com ---
I applied your patch and patches 1 and 3 of that series on linux 5.2-rc2, but
it unfortunately doesn't show any effect:
-There is still the mouse input issue for the games described in this
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #16 from Nicholas Kazlauskas ---
Created attachment 144354
--> https://bugs.freedesktop.org/attachment.cgi?id=144354=edit
0001-drm-amd-display-Allow-fast-updates-again-for-swappin.patch
Sure, you can try the patch I've attached
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #15 from tempel.jul...@gmail.com ---
Well, hope on the horizon.
If applying debug patches would be helpful for trying to shed light into this
issue, I would of course do it.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #14 from Nicholas Kazlauskas ---
(In reply to tempel.julian from comment #13)
> Thanks for letting me know!
> Could you please provide me with a loose estimate if those general atomic
> modesetting performance limitations can be
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #13 from tempel.jul...@gmail.com ---
Thanks for letting me know!
Could you please provide me with a loose estimate if those general atomic
modesetting performance limitations can be overcome in the next months? Would
really put my
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #12 from Nicholas Kazlauskas ---
I'm wondering if this is the async cursor update bug again. Maybe something
with WINE or the game is trying to swap cursor buffers frequently and it's
interacting with the cursor double buffering in
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #11 from tempel.jul...@gmail.com ---
Happens also with plain wined3d inside official Steam Proton builds. In case of
Skyrim, it is also affects the rendering performance and thus is visible in the
frametime graph (unlike Hitman 2
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #10 from tempel.jul...@gmail.com ---
Nope, not related to it. Happens also with stable versions.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #9 from tempel.jul...@gmail.com ---
Until I get a new GPU or a FreeSync display, I use amdgpu.dc=1 only for testing
purposes. So I can't judge if this is a regression or has always existed.
But I gave Linux 4.19.46 LTS a try and it
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #8 from Nicholas Kazlauskas ---
Do you happen to know if this was a regression?
--
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=110659
--- Comment #7 from tempel.jul...@gmail.com ---
Playing Skyrim with Gallium Nine also shows this issue, it makes the games
unplayable.
Is it really certain that it's an amdgpu.dc problem when the modesetting DDX
doesn't show this issue?
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #6 from tempel.jul...@gmail.com ---
Situation is unchanged with 5.3-wip.
It also occurs with amdvlk instead of radv if you turn on pageflipping via
UseFlipHint,1 in amdPalSettings.cfg (for incomprehensible reasons it is
disabled by
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #5 from tempel.jul...@gmail.com ---
Yes, it also happens with Linux 5.1.
It btw. runs fine on xwayland inside a Plasma Wayland session.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #4 from Nicholas Kazlauskas ---
What's the latest commit in your WIP kernel?
I know there was a regression caused by:
https://patchwork.freedesktop.org/patch/304544/
that forces full updates on every commit leading to pretty poor
https://bugs.freedesktop.org/show_bug.cgi?id=110659
Michel Dänzer changed:
What|Removed |Added
Version|git |unspecified
85 matches
Mail list logo
