[Bug 53428] New: 18ae96e5fb causes deadlocking on nvidia hardware
https://bugs.winehq.org/show_bug.cgi?id=53428 Bug ID: 53428 Summary: 18ae96e5fb causes deadlocking on nvidia hardware Product: Wine Version: 7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: d3d Assignee: wine-bugs(a)winehq.org Reporter: hibbsncc1701(a)gmail.com Distribution: --- This bug is split from Bug #53372. Testing in that bug (See Zeb's comment: https://bugs.winehq.org/show_bug.cgi?id=53372#c9) reveals that commit 18ae96e5fb3cbbd53f1a022ba81203de6b431228 causes deadlocking to occur in some programs on Nvidia hardware. Reverting the patch does fix it, but obviously that is not ideal. As per Zeb's request I've created this bug. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Patrick Hibbs <hibbsncc1701(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Regression SHA1| |18ae96e5fb3cbbd53f1a022ba81 | |203de6b431228 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|18ae96e5fb causes |Total War Shogun 2 |deadlocking on nvidia |deadlocks on nvidia |hardware |hardware -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com --- Comment #1 from Zeb Figura <z.figura12(a)gmail.com> --- I've tried to report this to NVidia here: <https://forums.developer.nvidia.com/t/deadlock-possibly-caused-by-x-display-...> -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |loothelion(a)nvidia.com, | |zzhang(a)codeweavers.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lvb.crd(a)protonmail.com --- Comment #2 from Dmitry Skvortsov (Iglu47) <lvb.crd(a)protonmail.com> --- Affect Epic Games Launcher (in OpenGL mode) - the authorization window does not appear properly. Probably only affects the proprietary Nvidia driver Please add the name of the application to the title. Reverts this commits help as temporal workaround: d328af75fee0f10dab67ab64fee78e2e2da7a447 18ae96e5fb3cbbd53f1a022ba81203de6b431228 ed546bf190cf5570df3086e4c7c42f7083c2a5a3 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Total War Shogun 2 |Multiple applications |deadlocks on nvidia |deadlock on nvidia hardware |hardware |(Total War Shogun 2, Epic | |Games launcher) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69(a)gmail.com -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |andrey.goosev(a)gmail.com --- Comment #3 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- *** Bug 53353 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Multiple applications |Multiple applications |deadlock on nvidia hardware |deadlock on nvidia hardware |(Total War Shogun 2, Epic |(Total War Shogun 2, Epic |Games launcher) |Games launcher, Rise of the | |Tomb Raider) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTOURBUG --- Comment #4 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Marking as NOTOURBUG. See https://forums.developer.nvidia.com/t/deadlock-possibly-caused-by-x-display-... -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cybermax(a)dexter.no --- Comment #5 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- *** Bug 55270 has been marked as a duplicate of this bug. *** -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 --- Comment #6 from Sveinar Søpler <cybermax(a)dexter.no> --- (In reply to Zhiyi Zhang from comment #4)
Marking as NOTOURBUG. See https://forums.developer.nvidia.com/t/deadlock-possibly-caused-by-x-display- lock-inversion-in-glxcreatecontext/222074
What a shame. Already 1 year has passed without change, so not holding my breath on that one.. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 --- Comment #7 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- I made a workaround at https://gitlab.winehq.org/wine/wine/-/merge_requests/5179 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 Zhiyi Zhang <zzhang(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Fixed by SHA1| |d287548c77350b81faa946b0977 | |dffcbfcce9b83 --- Comment #8 from Zhiyi Zhang <zzhang(a)codeweavers.com> --- Worked around by d287548c77350b81faa946b0977dffcbfcce9b83 -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=53428 --- Comment #9 from Sveinar Søpler <cybermax(a)dexter.no> --- I still have to revert: 18ae96e5fb3cbbd53f1a022ba81203de6b431228 even after this to get OptiX samples to show output window, so in that particular instance it did not fix anything for me. Other CUDA samples seem to work just fine, but it seems the OptiX samples use some other kind of method perhaps. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla