[Bug 27848] New: Crysis2 freezes/hangs since wine 1.3.22 (ReportFault 0xc65de0c)
http://bugs.winehq.org/show_bug.cgi?id=27848 Summary: Crysis2 freezes/hangs since wine 1.3.22 (ReportFault 0xc65de0c) Product: Wine Version: 1.3.24 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs(a)winehq.org ReportedBy: rockorequin(a)hotmail.com Crysis 2 runs fine on wine 1.3.21 on my PC with an nvidia 540M card, but in versions 1.3.22 and onwards it freezes at a random point usually less than a minute after gameplay starts with the error: fixme:faultrep:ReportFault 0xc65de0c 0x0 stub At this point, the music continues to play (it doesn't appear to be looping) but the graphics are frozen, so I'm guessing it's a d3d issue. I have the various directX 9 and 10 native libraries enabled via winetricks and the Crysis patch applied to wine. Running it in wine 1.3.24, I also get "fixme:d3d_texture:wined3d_texture_generate_mipmaps texture 0x6aa3928 stub!" errors, but these don't appear to cause the freeze. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression --- Comment #1 from Austin English <austinenglish(a)gmail.com> 2011-07-22 23:26:33 CDT --- Please run a regression test: http://wiki.winehq.org/RegressionTesting -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #2 from rocko <rockorequin(a)hotmail.com> 2011-07-23 07:33:09 CDT --- I'm pretty sure this is the commit that causes the problem: 52fd36b68b3f115d2e5fe3040b6abc51bad862e0 is the first bad commit commit 52fd36b68b3f115d2e5fe3040b6abc51bad862e0 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Thu Jun 23 00:02:33 2011 +0200 d3d9: Implement IDirect3DVolume9 private data handling on top of wined3d_resource. although that commit is actually between wine 1.3.22 and 1.3.23, not before 1.3.22 like I thought. I double-checked it by doing a git checkout to the commit just before (7a8a7b920e4c4f5ed7dcf750f9cf712a6e614172). The crash didn't happen in 5-10 minutes of playing, but with 52fd36b68b3f115d2e5fe3040b6abc51bad862e0 it happened fairly quickly. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 Jerome Leclanche <adys.wh(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh(a)gmail.com, | |hverbeet(a)gmail.com --- Comment #3 from Jerome Leclanche <adys.wh(a)gmail.com> 2011-07-23 07:36:25 CDT --- CC henri as usual. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #4 from rocko <rockorequin(a)hotmail.com> 2011-07-24 07:01:37 CDT --- I've now found that it crashes with the supposed 'good' commit (7a8a7b920e4c4f5ed7dcf750f9cf712a6e614172) and earlier, so I need to keep bisecting. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #5 from rocko <rockorequin(a)hotmail.com> 2011-07-25 00:29:43 CDT --- The bad commit might be be here or nearby: 26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 is the first bad commit commit 26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Thu Jun 16 00:40:32 2011 +0200 wined3d: Check the correct debug class in checkGLcall. :040000 040000 6a22b35e6d518f2e5c42d6cdeedc2ba41bcd9094 2da11cafd991229dc13ccfb8a01740a5d4eafead M dlls It's hard to be completely sure because while bisecting I found with commits near to that commit the game freezes but there is also an nvidia crash relating to interrupts that brings down the entire kernel and so this might be the cause of the freeze. eg this happened when I compiled wine up to and including commits 26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 and e532c55995989f9ad4625e876fe93b71d6b476f1. I know for sure that when I compiled up to commit ffb8f4bedf709dd63f6f9ec1569dc99873021a11 (rpcrt4: Add support for float parameters in client calls on x86_64) I have experienced the non-nvidia wine freeze, ie this bug. Running with wine compiled up to 46215689221aa820b94d2ce288613d6e0b373f77 (wined3d: Only invert viewport y for onscreen destinations in surface_depth_b) so far seems good. I'll report back if I manage to crash it. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #6 from Henri Verbeet <hverbeet(a)gmail.com> 2011-07-25 09:31:23 CDT --- (In reply to comment #5)
The bad commit might be be here or nearby:
26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 is the first bad commit commit 26eb6c8eeae6ba8c24f001edb94b2e6e9cf7c4a4 Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Thu Jun 16 00:40:32 2011 +0200
wined3d: Check the correct debug class in checkGLcall.
:040000 040000 6a22b35e6d518f2e5c42d6cdeedc2ba41bcd9094 2da11cafd991229dc13ccfb8a01740a5d4eafead M dlls
That commit is very unlikely to be the cause. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #7 from rocko <rockorequin(a)hotmail.com> 2011-07-25 20:04:01 CDT --- Is there anything before ffb8f4bedf709dd63f6f9ec1569dc99873021a11 (rpcrt4: Add support for float parameters in client calls on x86_64)? I know for sure the bug is present by that commit. I experienced the nvidia crash with commit 46215689221aa820b94d2ce288613d6e0b373f77 just now btw. The nvidia crash is making it hard to bisect the actual bug. I can try bisecting assuming that the bisect is good if I hit the nvidia crash after a long time playing if that will help. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 eurekafag(a)eureka7.ru changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 --- Comment #8 from eurekafag(a)eureka7.ru 2011-08-18 13:58:43 CDT --- *** This bug has been confirmed by popular vote. *** -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |26eb6c8eeae6ba8c24f001edb94 | |b2e6e9cf7c4a4 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 Henri Verbeet <hverbeet(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1|26eb6c8eeae6ba8c24f001edb94 | |b2e6e9cf7c4a4 | -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nerv(a)dawncrow.de --- Comment #9 from André H. <nerv(a)dawncrow.de> 2011-10-23 12:07:39 CDT --- (In reply to comment #7)
I experienced the nvidia crash with commit 46215689221aa820b94d2ce288613d6e0b373f77 just now btw. The nvidia crash is making it hard to bisect the actual bug. I can try bisecting assuming that the bisect is good if I hit the nvidia crash after a long time playing if that will help.
yes, already results? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #10 from rocko <rockorequin(a)hotmail.com> 2011-10-23 16:45:17 CDT --- I can still crash the game every time (sometimes it takes five minutes or more), but the entire machine locks up not long afterwards, which makes it look like I am hitting the nvidia bug. The message "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" often appears in the syslog, and I occasionally see Xid 13 as well, which I think is a segfault in the nvidia driver. The upshot is that I can't reproduce this at the moment because another more serious bug occurs instead. I assume that wine shouldn't be able to cause the nvidia driver to crash? -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #11 from Artem S. Tashkinov <t.artem(a)mailcity.com> 2011-10-26 04:40:46 CDT --- (In reply to comment #10)
I can still crash the game every time (sometimes it takes five minutes or more), but the entire machine locks up not long afterwards, which makes it look like I am hitting the nvidia bug. The message "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" often appears in the syslog, and I occasionally see Xid 13 as well, which I think is a segfault in the nvidia driver.
The upshot is that I can't reproduce this at the moment because another more serious bug occurs instead. I assume that wine shouldn't be able to cause the nvidia driver to crash?
Error messages that you see indicate a problem either with NVIDIA drivers or X server or (much less possible) with your hardware. Please, report your problem here: http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 --- Comment #12 from rocko <rockorequin(a)hotmail.com> 2011-10-26 05:47:34 CDT --- OK, I already reported the bug to nvidia four months ago but I'll report it again. If they ever fix it I might be able to reproduce this one... -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 rocko <rockorequin(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #13 from rocko <rockorequin(a)hotmail.com> 2011-10-28 21:39:09 CDT --- I found what seems to be a workaround for the nvidia crash (renice the wine process to -15), and I have been able to play Crysis2 on two occasions now for more than 20 minutes without any crashes. This is using the latest wine. So this bug may be fixed now, or maybe the crash was always an nvidia one that became more likely to occur after to a change in wine. Originally, the crash didn't lock up the whole system so it might not have been an nvidia issue. Either way, I'll mark this invalid for now. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 André H. <nerv(a)dawncrow.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #14 from André H. <nerv(a)dawncrow.de> 2011-10-29 08:17:55 CDT --- closing invalid -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.
http://bugs.winehq.org/show_bug.cgi?id=27848 K1773R <K1773R(a)darkgamex.ch> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |K1773R(a)darkgamex.ch -- 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)
-
wine-bugs＠winehq.org