[Bug 110751] New: AMD Radeon HD 7670M, power_profile: Invalid argument

https://bugs.freedesktop.org/show_bug.cgi?id=110751 Bug ID: 110751 Summary: AMD Radeon HD 7670M, power_profile: Invalid argument Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status:

[Bug 110720] The "Oops" error popup is displayed after uploading document in the Reader

https://bugs.freedesktop.org/show_bug.cgi?id=110720 Aleksandra changed: What|Removed |Added Assignee|xorg-driver-ati@lists.x.org |aleksandra.botsulyak@qatest

[Bug 110720] The "Oops" error popup is displayed after uploading document in the Reader

https://bugs.freedesktop.org/show_bug.cgi?id=110720 --- Comment #1 from Aleksandra --- Created attachment 144314 --> https://bugs.freedesktop.org/attachment.cgi?id=144314=edit Oops -- You are receiving this mail because: You are the assignee for the

[Bug 110720] New: The "Oops" error popup is displayed after uploading document in the Reader

https://bugs.freedesktop.org/show_bug.cgi?id=110720 Bug ID: 110720 Summary: The "Oops" error popup is displayed after uploading document in the Reader Product: xorg Version: 6.7.0 Hardware: Other OS: All

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 --- Comment #8 from Peter --- I can't reproduce the problem any more. I updated to Plasma 5.15.5 from 5.15.0 and now Freesync is properly working whenever I switch back to a game. I had the issue with Freesync not re-activating properly ever

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 Michel Dänzer changed: What|Removed |Added Attachment #144119|0 |1 is obsolete|

[Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=110659 Michel Dänzer changed: What|Removed |Added Version|git |unspecified

[Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=110659 Michel Dänzer changed: What|Removed |Added Attachment #144214|text/x-log |text/plain mime type|

[Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=110659 Michel Dänzer changed: What|Removed |Added Attachment #144213|text/x-log |text/plain mime type|

[Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=110659 --- Comment #2 from tempel.jul...@gmail.com --- Funny, this MR leads to the same behavior with the modesetting driver: https://gitlab.freedesktop.org/xorg/xserver/merge_requests/180 -- You are receiving this mail because: You are the assignee

[Bug 110659] pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=110659 --- Comment #1 from tempel.jul...@gmail.com --- Created attachment 144214 --> https://bugs.freedesktop.org/attachment.cgi?id=144214=edit dmseg log -- You are receiving this mail because: You are the assignee for the

[Bug 110659] New: pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1

https://bugs.freedesktop.org/show_bug.cgi?id=110659 Bug ID: 110659 Summary: pageflipping seems to cause jittering on mouse input when running Hitman 2 in Wine/DXVK with amdgpu.dc=1 Product: xorg Version: git Hardware:

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 Michel Dänzer changed: What|Removed |Added Attachment #144141|text/x-log |text/plain mime type|

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 Peter changed: What|Removed |Added CC||zuro...@gmail.com --- Comment #6 from Peter

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 --- Comment #5 from Michel Dänzer --- Created attachment 144119 --> https://bugs.freedesktop.org/attachment.cgi?id=144119=edit VRR debugging output Please build the driver with this patch attached, reproduce the problem and attach the

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected

https://bugs.freedesktop.org/show_bug.cgi?id=110478 Michel Dänzer changed: What|Removed |Added Component|Driver/AMDgpu |DRM/AMDgpu QA

[Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected

https://bugs.freedesktop.org/show_bug.cgi?id=110478 Michel Dänzer changed: What|Removed |Added Attachment #144053|text/x-log |text/plain mime type|

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 Michel Dänzer changed: What|Removed |Added Attachment #144049|text/x-log |text/plain mime type|

[Bug 110490] application crash overload

https://bugs.freedesktop.org/show_bug.cgi?id=110490 Andre Klapper changed: What|Removed |Added Attachment #144068|0 |1 is obsolete|

[Bug 110490] application crash overload

https://bugs.freedesktop.org/show_bug.cgi?id=110490 Vsw changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[Bug 110490] New: application crash overload

https://bugs.freedesktop.org/show_bug.cgi?id=110490 Bug ID: 110490 Summary: application crash overload Product: xorg Version: unspecified Hardware: x86 (IA32) OS: Linux (All) Status: UNCONFIRMED Severity:

[Bug 110478] AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected

https://bugs.freedesktop.org/show_bug.cgi?id=110478 --- Comment #1 from cmdr...@gmail.com --- I guess this could also be in dri->drm/amdgpu. I'm not sure how to narrow it down, I've tried with breakpoints for drmModeSetCrtc and drmmode_set_mode_major but I'm not seeing anything that sticks out.

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #11 from tempel.jul...@gmail.com --- (In reply to Mike Lothian from comment #10) > What about the modesetting DDX? This PR by yshui fixes the tearing for modesetting: https://gitlab.freedesktop.org/xorg/xserver/merge_requests/131

[Bug 110478] New: AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected

https://bugs.freedesktop.org/show_bug.cgi?id=110478 Bug ID: 110478 Summary: AMDGPU error(failed to set mode: cannot allocate memory) when hdmi connected Product: xorg Version: unspecified Hardware: x86-64 (AMD64)

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 --- Comment #4 from bmil...@gmail.com --- Created attachment 144050 --> https://bugs.freedesktop.org/attachment.cgi?id=144050=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 --- Comment #3 from bmil...@gmail.com --- Created attachment 144049 --> https://bugs.freedesktop.org/attachment.cgi?id=144049=edit xorg log -- You are receiving this mail because: You are the assignee for the

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #10 from Mike Lothian --- What about the modesetting DDX? -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 --- Comment #2 from Michel Dänzer --- Please attach the corresponding Xorg log file and output of dmesg, captured after reproducing the problem. -- You are receiving this mail because: You are the assignee for the

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #9 from Michel Dänzer --- (In reply to Yuxuan Shui from comment #8) > Just curious, was paging flipping not implemented prior to linux 5.2? It was, but it wasn't being used due to the xf86-video-amdgpu bug. -- You are receiving

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #8 from Yuxuan Shui --- (In reply to Michel Dänzer from comment #5) > There's no kernel issue to be fixed. Without page flipping, it was just luck > that you didn't get tearing in some cases. Just curious, was paging flipping not

[Bug 110473] FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 --- Comment #1 from Peter --- As discussed in https://gitlab.freedesktop.org/bnieuwenhuizen/mesa/commit/260d6f0e3c270ebfd7319f2f8fa67beececa68f5#note_145169 I can get Freesync back in World of Warcraft by maximizing other windows over top of

[Bug 110473] New: FreeSync / VRR stops working after window switching or minimizing

https://bugs.freedesktop.org/show_bug.cgi?id=110473 Bug ID: 110473 Summary: FreeSync / VRR stops working after window switching or minimizing Product: xorg Version: unspecified Hardware: Other OS: All

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #7 from Alex Deucher --- (In reply to tempel.julian from comment #6) > Ha, curious. I really could never spot any tearing before the 5.2-wip > branch. Glad that bisecting is not required. > > Well, there is one little exception

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #6 from tempel.jul...@gmail.com --- Ha, curious. I really could never spot any tearing before the 5.2-wip branch. Glad that bisecting is not required. Well, there is one little exception (independent of the compositor): When I turn

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #5 from Michel Dänzer --- There's no kernel issue to be fixed. Without page flipping, it was just luck that you didn't get tearing in some cases. -- You are receiving this mail because: You are the assignee for the

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 --- Comment #4 from tempel.jul...@gmail.com --- The fix provided by Michel seems to work flawlessly. Would a kernel fix still be desirable? -- You are receiving this mail because: You are the assignee for the

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 Mike Lothian changed: What|Removed |Added CC||m...@fireburn.co.uk --- Comment #3 from

[Bug 110417] regression drm-next-5.2-wip: breaks vsync of new Compton xrender backend

https://bugs.freedesktop.org/show_bug.cgi?id=110417 Michel Dänzer changed: What|Removed |Added Component|DRM/AMDgpu |Driver/AMDgpu Version|DRI

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #10 from Michel Dänzer --- (In reply to tempel.julian from comment #9) > Thanks for looking into it. Is it possible for xorg/mesa to just show solid > black instead of "modern art" in such cases? Xorg can't know that the client

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #9 from tempel.jul...@gmail.com --- Thanks for looking into it. Is it possible for xorg/mesa to just show solid black instead of "modern art" in such cases? Of course not an important matter at all, compared to other things like

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 Michel Dänzer changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|NEW

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #7 from Michel Dänzer --- Can you try if this also happens with Mesa 19.0 or older? -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #6 from tempel.jul...@gmail.com --- Seems to happen less likely with KWin than with Compton or no compositor. My guess as a layman would be that the program initializes GL rendering inside the window, but freezes for a moment while

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #5 from tempel.jul...@gmail.com --- Created attachment 143996 --> https://bugs.freedesktop.org/attachment.cgi?id=143996=edit dmesg -- You are receiving this mail because: You are the assignee for the

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #4 from tempel.jul...@gmail.com --- Created attachment 143995 --> https://bugs.freedesktop.org/attachment.cgi?id=143995=edit glxinfo log -- You are receiving this mail because: You are the assignee for the

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #3 from tempel.jul...@gmail.com --- Created attachment 143994 --> https://bugs.freedesktop.org/attachment.cgi?id=143994=edit xorg log -- You are receiving this mail because: You are the assignee for the

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #2 from Michel Dänzer --- (In reply to tempel.julian from comment #0) > Happens with both amdgpu DDX and modesetting. That indicates against it being an xf86-video-amdgpu bug then. It sounds like a blender or Mesa issue most

[Bug 110448] brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 --- Comment #1 from tempel.jul...@gmail.com --- Forgot to mention: Happens with and without compositor. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati

[Bug 110448] New: brief corruption when opening Blender benchmark window

https://bugs.freedesktop.org/show_bug.cgi?id=110448 Bug ID: 110448 Summary: brief corruption when opening Blender benchmark window Product: xorg Version: git Hardware: Other OS: All Status: NEW Severity:

[Bug 110362] Need an option to set HDMI out to Full RGB 4:4:4

https://bugs.freedesktop.org/show_bug.cgi?id=110362 Michel Dänzer changed: What|Removed |Added Assignee|xorg-driver-ati@lists.x.org |dri-devel@lists.freedesktop

[Bug 110362] New: Need an option to set HDMI out to Full RGB 4:4:4

https://bugs.freedesktop.org/show_bug.cgi?id=110362 Bug ID: 110362 Summary: Need an option to set HDMI out to Full RGB 4:4:4 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 110138] Adaptive Sync, VRR, FreeSync out of range

https://bugs.freedesktop.org/show_bug.cgi?id=110138 Michel Dänzer changed: What|Removed |Added Product|xorg|DRI Component|Driver/AMDgpu

[Bug 110138] Adaptive Sync, VRR, FreeSync out of range

https://bugs.freedesktop.org/show_bug.cgi?id=110138 --- Comment #1 from gr...@sub.red --- Created attachment 143689 --> https://bugs.freedesktop.org/attachment.cgi?id=143689=edit parsed edid -- You are receiving this mail because: You are the assignee for the

[Bug 110138] New: Adaptive Sync, VRR, FreeSync out of range

https://bugs.freedesktop.org/show_bug.cgi?id=110138 Bug ID: 110138 Summary: Adaptive Sync, VRR, FreeSync out of range Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity:

[Bug 110103] [CI][BAT] [ICL only] igt@* - incomplete - timeout/system hang?

https://bugs.freedesktop.org/show_bug.cgi?id=110103 Michel Dänzer changed: What|Removed |Added Component|Driver/AMDgpu-pro |Two

[Bug 110103] New: [CI][BAT] [ICL only] igt@* - incomplete - timeout/system hang?

https://bugs.freedesktop.org/show_bug.cgi?id=110103 Bug ID: 110103 Summary: [CI][BAT] [ICL only] igt@* - incomplete - timeout/system hang? Product: xorg Version: unspecified Hardware: Other OS: All

[Bug 109909] New: Login

https://bugs.freedesktop.org/show_bug.cgi?id=109909 Bug ID: 109909 Summary: Login Product: xorg Version: 7.6 (2010.12) Hardware: x86 (IA32) URL: www.facebook.com OS: Windows (All) Status: NEW

[Bug 109207] `override_redirect` windows are not visible on amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=109207 Levi Webb changed: What|Removed |Added Resolution|--- |FIXED Status|NEEDINFO

[Bug 109207] `override_redirect` windows are not visible on amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=109207 Michel Dänzer changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this

[Bug 109207] `override_redirect` windows are not visible on amdgpu

https://bugs.freedesktop.org/show_bug.cgi?id=109207 --- Comment #2 from Michel Dänzer --- I'm afraid there can be no progress on this without the information I asked for. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 84770] Typo in src/radeon_dri2.c

https://bugs.freedesktop.org/show_bug.cgi?id=84770 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 104519] crash of the computer

https://bugs.freedesktop.org/show_bug.cgi?id=104519 Andre Klapper changed: What|Removed |Added Status|NEW |NEEDINFO -- You are receiving this

[Bug 84770] Typo in src/radeon_dri2.c

https://bugs.freedesktop.org/show_bug.cgi?id=84770 Andre Klapper changed: What|Removed |Added Summary|typo? |Typo in src/radeon_dri2.c -- You are

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

https://bugs.freedesktop.org/show_bug.cgi?id=109680 --- Comment #5 from toberepla...@gmail.com --- Thank you for all of the help. I have come to a resolution based on your hunch about removing Screen lines in the device sections. The segmentation fault appears to occur if there is no "Screen 0"

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

https://bugs.freedesktop.org/show_bug.cgi?id=109680 --- Comment #4 from Michel Dänzer --- (In reply to ToBeReplaced from comment #3) > Thank you for the quick reply. I'll post an issue there, then close this one. This one's already resolved, no need to close it. > Removing the Screen sections

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

https://bugs.freedesktop.org/show_bug.cgi?id=109680 --- Comment #3 from toberepla...@gmail.com --- Thank you for the quick reply. I'll post an issue there, then close this one. Removing the Screen sections does not help, unfortunately. I'll post another log in a bit. The end goal is to use it

[Bug 109687] New: CMPE 287 Bug Testing

https://bugs.freedesktop.org/show_bug.cgi?id=109687 Bug ID: 109687 Summary: CMPE 287 Bug Testing Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority:

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

https://bugs.freedesktop.org/show_bug.cgi?id=109680 Michel Dänzer changed: What|Removed |Added Resolution|--- |NOTOURBUG Status|NEW

[Bug 109680] Multiple cards with modesetting results in Segmentation Fault

https://bugs.freedesktop.org/show_bug.cgi?id=109680 --- Comment #1 from toberepla...@gmail.com --- Whoops, forgot to add that I attempted to receive support through #xorg on freenode (no responses), then later at

[Bug 109680] New: Multiple cards with modesetting results in Segmentation Fault

https://bugs.freedesktop.org/show_bug.cgi?id=109680 Bug ID: 109680 Summary: Multiple cards with modesetting results in Segmentation Fault Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS:

[Bug 109678] build error: /usr/include/xorg/xf86Opt.h:44:10: error: two or more data types in declaration specifiers

https://bugs.freedesktop.org/show_bug.cgi?id=109678 Michel Dänzer changed: What|Removed |Added QA Contact|xorg-t...@lists.x.org | Product|xorg

[Bug 109678] New: build error: /usr/include/xorg/xf86Opt.h:44:10: error: two or more data types in declaration specifiers

https://bugs.freedesktop.org/show_bug.cgi?id=109678 Bug ID: 109678 Summary: build error: /usr/include/xorg/xf86Opt.h:44:10: error: two or more data types in declaration specifiers Product: xorg Version: git Hardware: All

[Bug 109496] XWayland broken vsync frequency

https://bugs.freedesktop.org/show_bug.cgi?id=109496 Niklas Haas changed: What|Removed |Added Resolution|--- |MOVED Status|NEW

[Bug 109496] New: XWayland broken vsync frequency

https://bugs.freedesktop.org/show_bug.cgi?id=109496 Bug ID: 109496 Summary: XWayland broken vsync frequency Product: xorg Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #38 from Michel Dänzer --- According to the 6-month release cycle, the 19.0 release is expected around March. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #37 from tempel.jul...@gmail.com --- Really appreciate how well issues are sorted out for the xf86 DDX driver. It'd be nice if the next release wasn't very far away, as there seem to be a lot of really helpful fixes included. --

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #35 from tempel.jul...@gmail.com --- All fine again. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati mailing list xorg-driver-ati@lists.x.org

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #34 from Michel Dänzer --- Ugh yeah, had a brain fart in patch 2. :} Fixed up now, please try again. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #33 from tempel.jul...@gmail.com --- Created attachment 143226 --> https://bugs.freedesktop.org/attachment.cgi?id=143226=edit drm handle error log -- You are receiving this mail because: You are the assignee for the

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #32 from tempel.jul...@gmail.com --- It breaks again with the mentioned error in the log. -- You are receiving this mail because: You are the assignee for the bug.___ xorg-driver-ati

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #31 from Michel Dänzer --- I updated the branch with the final fixes for review, please test that it still fixes the problem. If any log message about drmHandleEvent appears during testing, please provide it. -- You are receiving

[Bug 109235] Using named pixmap of window right after resizing results in garbage content

https://bugs.freedesktop.org/show_bug.cgi?id=109235 --- Comment #20 from tempel.jul...@gmail.com --- While I haven't seen this corruption anymore when doing certain window operations, it occasionally very briefly still occurs when starting 3D applications (Xorg session). I suppose I can't provide

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #30 from tempel.jul...@gmail.com --- Definitely fixed, thanks. I'd say TearFree works flawlessly here now. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #29 from tempel.jul...@gmail.com --- Created attachment 143203 --> https://bugs.freedesktop.org/attachment.cgi?id=143203=edit latest xorg log -- You are receiving this mail because: You are the assignee for the

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #28 from tempel.jul...@gmail.com --- I tried with amdgppu.dc=1 & 0 once each time, and it looks like you did it, no anomalies showed up. Yey! :) Will test it a few more times to be sure. -- You are receiving this mail because: You

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #27 from Michel Dänzer --- Had another idea what could cause the problem. Branch updated, please re-test and attach the resulting log file (regardless of whether the problem still occurs). -- You are receiving this mail because:

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #26 from tempel.jul...@gmail.com --- Created attachment 143198 --> https://bugs.freedesktop.org/attachment.cgi?id=143198=edit amdgpu.dc=0 xorg log -- You are receiving this mail because: You are the assignee for the

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #25 from tempel.jul...@gmail.com --- Ok, it doesn't seem to matter if fps are capped below refreshrate by the game's fps limiter. However, it's easier to spot tearing when there is no judder due to repeated frames. With amdgpu.dc=0

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #24 from Michel Dänzer --- (In reply to tempel.julian from comment #22) > If we can't manage to find the root of the problem, perhaps automatically > re-initializing TearFree after it detects failure would be a viable > workaround?

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #23 from tempel.jul...@gmail.com --- Ok, the difference between amdgpu.dc=1 & 0 is also there with normal git-master of xf86-video-amdgpu. -- You are receiving this mail because: You are the assignee for the

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #22 from tempel.jul...@gmail.com --- Yes, I think one of your changes introduced a difference between amdgpu.dc=1 and 0 in that regard: With amdgpu.dc=0, TearFree remains enabled after switching vsync in vkquake on and off and then

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #21 from Michel Dänzer --- (In reply to tempel.julian from comment #18) > So I tried the latest PR update with vkquake and to me it seems the errors > logged haven't changed: That's bad news, as it means I'm running out of ideas

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #20 from tempel.jul...@gmail.com --- Thank you for the hint. I tried building xorg with autotools, but the situation is unchanged for me. -- You are receiving this mail because: You are the assignee for the

[Bug 109392] modesetting driver + amdgpu.dc=1 always enforces vsync

https://bugs.freedesktop.org/show_bug.cgi?id=109392 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #19 from Darek --- (In reply to tempel.julian from comment #15) > The warzone2100 build provided by Arch.. Maybe this bug is somehow related to this [1]? [1] https://bugs.archlinux.org/task/58782 Have you tried xorg-server

[Bug 109392] modesetting driver + amdgpu.dc=1 always enforces vsync

https://bugs.freedesktop.org/show_bug.cgi?id=109392 --- Comment #1 from tempel.jul...@gmail.com --- Created attachment 143159 --> https://bugs.freedesktop.org/attachment.cgi?id=143159=edit xorg log -- You are receiving this mail because: You are the assignee for the

[Bug 109392] New: modesetting driver + amdgpu.dc=1 always enforces vsync

https://bugs.freedesktop.org/show_bug.cgi?id=109392 Bug ID: 109392 Summary: modesetting driver + amdgpu.dc=1 always enforces vsync Product: xorg Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 109364] switching vsync on and off in vkquake breaks TearFree

https://bugs.freedesktop.org/show_bug.cgi?id=109364 --- Comment #18 from tempel.jul...@gmail.com --- I tried with warzone2100, but for some reason the vsync setting in the options menu became unclickable after clicking it once. So I tried the latest PR update with vkquake and to me it seems the

<    1   2   3   4   5   6   7   8   9   10   >