http://bugs.winehq.org/show_bug.cgi?id=13608
Summary: Test tool on windows makes XP completely reboot Product: Wine Version: unspecified Platform: PC-x86-64 URL: http://test.winehq.com/data/0b6acfbce7b0bf2aedb5176bfa95 9edc3f0d74f6/ OS/Version: Windows XP Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: saintk@specialattack.net CC: saintk@specialattack.net
Running this test; Main summary for build 0b6acfbce7b0bf2aedb5176bfa959edc3f0d74f6
Results in a full system reboot at my end.
This is what i can capture from my windows event log; Faulting application d3d9_test.exe, version 0.0.0.0, faulting module d3d9.dll, version 5.3.3790.3959, fault address 0x000a488a.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Any additional info;
OS: Windows XP x64 SP2
Hardware used; Asus Maximus Formula Unknown 350GB Sata disk Asus EAX1950XTX PCI-E 4GB DDR2 Geil RAM @ 800MHz
Everything is clocked default (no overclocking applied). System runs stable during stability tests both on the GPU and CPU.
If any more information or testing is required don't hessitate to contact me. Only 'downside' i don't know anything about debugging of any kind. Neither am I an active wine user. I just ran the test because i do support the idea behind the project.
http://bugs.winehq.org/show_bug.cgi?id=13608
Paul Vriens Paul.Vriens.Wine@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Paul.Vriens.Wine@gmail.com
--- Comment #1 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-06-02 09:44:07 --- Is there a res[number] file in C:\Documents and Settings<username>\Local Settings\Temp? If so, could you zip that file and attach it to this bug report?
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #2 from SaintK saintk@specialattack.net 2008-06-02 09:49:28 --- Created an attachment (id=13570) --> (http://bugs.winehq.org/attachment.cgi?id=13570) res2.zip - as requested
As requested.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #3 from SaintK saintk@specialattack.net 2008-06-02 09:50:11 --- Hi,
I have found 1 res* file in my temp dir named 'res2'. I have zipped this up and attached it to the bug report.
Regards,
http://bugs.winehq.org/show_bug.cgi?id=13608
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-02 22:43:59 --- You have filed the bug report in wrong place, we don't fix Windows bugs.
http://bugs.winehq.org/show_bug.cgi?id=13608
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-02 22:44:19 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #6 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-06-03 00:55:37 --- Although I agree it could be a Windows (driver) bug there are now several people that reported that our winetest crashes their system. As winetest is an aid in our efforts to conform to Windows it would be nice if we would make the effort not to to crash people's systems.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #7 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-03 01:06:31 --- We certainly can't debug broken Windows setups, and that's just a waste of Wine developer's efforts.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #8 from SaintK saintk@specialattack.net 2008-06-03 01:47:42 --- I have posted this bug report in effort to help the wine project with their tools to make the project better. If this is not appriciated, fine with me.
http://bugs.winehq.org/show_bug.cgi?id=13608
Juan Lang juan_lang@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|INVALID |
--- Comment #9 from Juan Lang juan_lang@yahoo.com 2008-06-03 11:35:34 --- Dmitry, the log has many failures in it before the crash. The regression tests can't fail on Windows or Wine, and therefore this is clearly a bug in our tests.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #10 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-03 20:01:37 --- (In reply to comment #9)
Dmitry, the log has many failures in it before the crash. The regression tests can't fail on Windows or Wine, and therefore this is clearly a bug in our tests.
Failures should be investigated, yes, and a separate bug should be opened for it.
Regarding Windows reboot caused by running Wine tests: all the bug reports going from Linux users that mention kernel bugs (machine hang or X11 crash) we close as invalid. What's so different about Windows in that case?
http://bugs.winehq.org/show_bug.cgi?id=13608
Alexander Dorofeyev alexd4@inbox.lv changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alexd4@inbox.lv
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #11 from KuSh kush.knowledge@laposte.net 2008-06-10 21:18:33 --- Created an attachment (id=13897) --> (http://bugs.winehq.org/attachment.cgi?id=13897) minidump analyze with windbg
Same is happening here. ATI card with latest drivers.
d3d9_test.exe crash with a timeout as indicated previously but I did use windbg on the generated minidumps and it says ddraw_test.exe is the culprit.
Log attached, the only directx related symbol in the thread stack is dxg!dwDdCreateSurfaceOrBuffer+0x56d.
Hope it could help, regards, KuSh
http://bugs.winehq.org/show_bug.cgi?id=13608
KuSh kush.knowledge@laposte.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #13897|application/octet-stream |text/plain mime type| |
http://bugs.winehq.org/show_bug.cgi?id=13608
KuSh kush.knowledge@laposte.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kush.knowledge@laposte.net
--- Comment #12 from KuSh kush.knowledge@laposte.net 2008-06-10 21:27:26 --- Forgot to say I did test with latest winetest.exe (winetest-200806101005-paul-mingw.exe)
res files are available if needed (ending just after d3d9/tests/visual test)
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #13 from Dmitry Timoshkov dmitry@codeweavers.com 2008-06-10 23:35:33 --- All the kernel crashes are the kernel/driver bugs by definition. User mode application should not be able to crash the kernel no matter how badly it behaves.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #14 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-06-11 00:59:51 --- KuSh, are you running a 64bit version of XP? And you're using the 8.5 drivers? Together with SaintK I'm trying to find out which test in ddraw actually starts the crash (laborious task).
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #15 from KuSh kush.knowledge@laposte.net 2008-06-11 03:12:02 --- No, I'm running standard XP with SP3 and latest ATI drivers (8.5). Didn't listed it as I don't think this is relevant.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #16 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-06-11 03:15:25 --- The thing is that we now have at least 3 people seeing this crash. Apart from finding the test that triggers the issue I'd also like to know the common denominator. What ATI card do you have?
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #17 from KuSh kush.knowledge@laposte.net 2008-06-11 11:25:42 --- I have a Radeon HD 3850. Even if I think this is purely a driver bug caused by not 'normal use' of ddraw api.
Unfortunately minidumps didn't point out which test is faulty.
Being able to launch the ddraw tests alone will already permit to see if we are right, then enabling only one test at a time will point out the culprit etc etc.
Perhaps flushing the log after each write on it could help also.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #18 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-06-13 07:34:50 --- Thanks to SaintK for all the tedious testing. It turns out that the culprit are 2 tests in DeviceLoadTest:
2067 ddsd.ddsCaps.dwCaps2 = DDSCAPS2_CUBEMAP | DDSCAPS2_CUBEMAP_POSITIVEX; ... 2070 hr = IDirectDraw7_CreateSurface(lpDD, &ddsd, &cube_face_levels[0][0][0], NULL);
and 2078 ddsd.ddsCaps.dwCaps2 = DDSCAPS2_CUBEMAP | DDSCAPS2_CUBEMAP_POSITIVEX | DDSCAPS2_CUBEMAP_POSITIVEY; ... 2081 hr = IDirectDraw7_CreateSurface(lpDD, &ddsd, &cube_face_levels[1][0][0], NULL);
Both of these make the system crash (with what appears to be a division by zero judging the minidumps).
Changing the DDSCAPS2_CUBEMAP_POSITIVEX and DDSCAPS2_CUBEMAP_POSITIVEY to DDSCAPS2_CUBEMAP_ALLFACES makes the tests run again (but that's not the purpose of this test of course)
The ATI driver of SaintK is version 8.4 but KuSh is running 8.5 and sees the same issues.
Anybody with an idea what to try next? Can we check for these caps and not run the tests if they are not available? (no idea what I'm talking about btw).
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #19 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-06-13 08:28:30 --- The failing module is ATI3DUAG.DLL. Googling for 'ATI3DUAG.DLL crash' gives a lot of hits.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #20 from KuSh kush.knowledge@laposte.net 2008-06-17 06:19:09 --- Did SaintK have the output log of the test without this two CreateSurface call ?
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #21 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-06-17 06:59:22 --- No full logs but there were never any errors reported on the subsets of tests. The only thing worth mentioning maybe:
d3d.c:2477: Tests skipped: IDirect3DDevice7_Load is broken (happens on some modern Windows installations like XP). Skipping affected tests.
I've sent SaintK the 'normal' ddraw_test.exe and asked him if he can run the other tests manually (so not the d3d one) and provide me with the output.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #22 from KuSh kush.knowledge@laposte.net 2008-06-18 03:38:03 --- Sent a "feedback" to "ATI Catalyst Crew" explaining the crash.
--- Comment #23 from KuSh kush.knowledge@laposte.net 2008-06-20 04:37:21 --- Tested with new 8.6 drivers. Crash is still present.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #24 from Austin English austinenglish@gmail.com 2008-08-15 12:24:58 --- Any progress on this?
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #25 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-08-19 05:40:36 --- I haven't heard anything after running the tests with the help of saintk.
I did find I have the same problem with my parents PC (ATI RADEON XPRESS 200 Series) though. I will run some tests this weeks and see what I can come up with.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #26 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-08-22 03:58:25 --- I saw that there were some changes committed for these tests (testing for cubemap support). I will try if it makes a difference tonight.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #27 from KuSh kush.knowledge@laposte.net 2008-08-23 14:22:49 --- Tested with 8.7 and just released 8.8 drivers with latest d3d9 test. Crash is still present.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #28 from Dmitry Timoshkov dmitry@codeweavers.com 2008-08-24 06:42:19 --- (In reply to comment #27)
Tested with 8.7 and just released 8.8 drivers with latest d3d9 test. Crash is still present.
Have you reported the bug to ATI/AMD?
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #29 from Alexander Dorofeyev alexd4@inbox.lv 2008-08-24 06:52:55 --- (In reply to comment #21)
No full logs but there were never any errors reported on the subsets of tests. The only thing worth mentioning maybe:
d3d.c:2477: Tests skipped: IDirect3DDevice7_Load is broken (happens on some modern Windows installations like XP). Skipping affected tests.
Just for the record, the above message is (somewhat) normal, I get this situation on windows XP with nvidia drivers. That's why I added it to the test. It is not related to the crash.
The crash, I suspect, is related to anything else than ALLFACES flag hitting some fatal bug in ati driver.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #30 from Alexander Dorofeyev alexd4@inbox.lv 2008-08-24 06:59:45 --- (In reply to comment #26)
I saw that there were some changes committed for these tests (testing for cubemap support). I will try if it makes a difference tonight.
It's not supposed to make any difference for this crash. It wasn't (and shouldn't be) crashing on correct drivers that have no cubemap support before the patch you mention, because trying to create an unsupported surface normally just returns an error (there is no excuse for the driver to crash in such situation). But previously test would have a failure on correct drivers without cubemap support. The patch was to avoid "make test" failing on cards like geforce 2 mx (no cubemaps).
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #31 from KuSh kush.knowledge@laposte.net 2008-08-24 15:40:08 --- (In reply to comment #28)
(In reply to comment #27)
Tested with 8.7 and just released 8.8 drivers with latest d3d9 test. Crash is still present.
Have you reported the bug to ATI/AMD?
Yes. See comment #22.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #32 from KuSh kush.knowledge@laposte.net 2008-09-20 05:39:29 --- Tested with 8.9. Crash is still present.
http://bugs.winehq.org/show_bug.cgi?id=13608
chris ahrendt celticht32@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |celticht32@aol.com
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #33 from Jeff Zaroyko jeffz@jeffz.name 2008-12-02 18:48:54 --- Tested with 8.11 (11/12/2008) on XP - still present.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #34 from Jeff Zaroyko jeffz@jeffz.name 2008-12-02 19:18:42 --- Logged ticket 737-1380499 with ATI detailing the steps to reproduce.
http://bugs.winehq.org/show_bug.cgi?id=13608
Vincent Povirk madewokherd@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #35 from Jeff Zaroyko jeffz@jeffz.name 2008-12-07 18:47:15 --- Re-submitted as #737-1381494 after logging a ticket in the wrong department, they however confirmed the issue and forwarded the details to the driver team.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #36 from Dmitry Timoshkov dmitry@codeweavers.com 2008-12-09 04:07:41 --- *** Bug 16395 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #37 from Paul Vriens Paul.Vriens.Wine@gmail.com 2008-12-22 05:05:47 --- Could somebody check if the latest release of the ATI drivers 8.12) still make the system crash?
I've found one box on http://test.winehq.org that has an ATI card: http://test.winehq.org/data/0b3b6e67ea663e853cc6bb93f4da447ab934e50d/xp_rs-s...
http://bugs.winehq.org/show_bug.cgi?id=13608
Michal Seliga selmi@centrum.sk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #38 from Michal Seliga selmi@centrum.sk 2008-12-22 05:57:31 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #39 from Rico kgbricola@web.de 2008-12-22 07:11:02 ---
http://test.winehq.org/data/0b3b6e67ea663e853cc6bb93f4da447ab934e50d/xp_rs-s...
That's my laptop. I removed the ddraw_test.exe (after the extraction) before the ddraw_test was started. You could see it here http://test.winehq.org/data/0b3b6e67ea663e853cc6bb93f4da447ab934e50d/#group_... all ddraw test failed because the exe was missing.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #40 from Paul Vriens Paul.Vriens.Wine@gmail.com 2009-03-18 04:05:23 --- Is this still an issue? I do see a Vista box with a Radeon X1600 card that happily runs the test:
http://test.winehq.org/data/3d35a630c4ae65fb4ab3aaf408a09051d5067b4f/vista_r...
I'm not sure if Vista crashed in the past as well.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #41 from chris ahrendt celticht32@aol.com 2009-03-18 12:05:04 --- Latest Drivers : 8.582-090203a-075974C-ATI Catalyst Ver 09.2 2D Driver 6.14.10.6912 Direct 3D 6.14.10.0643 Open GL 6.14.10.8484
Latest Conformancy Test
Latest XP patches
Reboots after the D3D 9 test.. I get a timeout warning.. click continue and it then reboots
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #42 from Nikolay Sivov bunglehead@gmail.com 2009-03-18 12:19:37 --- (In reply to comment #41)
Latest Drivers : 8.582-090203a-075974C-ATI Catalyst Ver 09.2 2D Driver 6.14.10.6912 Direct 3D 6.14.10.0643 Open GL 6.14.10.8484
Latest Conformancy Test
Latest XP patches
Reboots after the D3D 9 test.. I get a timeout warning.. click continue and it then reboots
I've got exactly the same behavior: x1950 on Catalyst 9.2 dx 9.0c Clean XP SP2 without any updates
It reboots exactly when I pressed continue after timeout as I remember.
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #43 from chris ahrendt celticht32@aol.com 2009-04-28 16:02:25 --- Created an attachment (id=20794) --> (http://bugs.winehq.org/attachment.cgi?id=20794) these are my res files from the last few builds of the winetest including April 28th
All these runs end up with the same result Windows XP SP3 with ATI rebooting the machine
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #44 from Austin English austinenglish@gmail.com 2009-10-29 14:10:28 --- Is this still an issue in current (1.1.32 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #45 from chris ahrendt celticht32@aol.com 2009-10-29 14:28:03 --- Will have to test when I get home from business trip... will let you know
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #46 from chris ahrendt celticht32@aol.com 2009-12-07 05:25:40 --- yes this is still an issue... it reboots with the latest ATI driver and the latest wine test
http://bugs.winehq.org/show_bug.cgi?id=13608
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #47 from Wylda wylda@volny.cz 2009-12-07 06:04:41 ---
Hi, this is just to join the club... It happend on my notebook with ATI MOBILITY FireGL V5000 and winetest suite 1.1.33. Because i was running latest drivers i downgraded to to notebook's defaults, but notebook restarted anyway. Did not bother with opening bug report - awaited closing as invalid. But when it's already in NEW state why not to join... :)
http://bugs.winehq.org/show_bug.cgi?id=13608
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Alias|SaintK |
--- Comment #48 from Jeff Zaroyko jeffz@jeffz.name 2009-12-07 06:22:28 --- (In reply to comment #35)
Re-submitted as #737-1381494 after logging a ticket in the wrong department, they however confirmed the issue and forwarded the details to the driver team.
One year since this comment, have heard no further response from ATI since submitting the ticket.
http://bugs.winehq.org/show_bug.cgi?id=13608
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Test tool on windows makes |d3d9_test.exe makes XP |XP completely reboot |completely reboot (Not a | |Wine bug)
http://bugs.winehq.org/show_bug.cgi?id=13608
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #49 from Xavier Vachon xvachon@gmail.com 2010-10-27 14:48:49 CDT --- Is this still an issue in current git (1.3.5)?
http://bugs.winehq.org/show_bug.cgi?id=13608
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #50 from joaopa jeremielapuree@yahoo.fr 2011-05-29 00:53:10 CDT --- no answer since 1year and half. ANyway, it is an invalid bug. Can be closed as INVALID
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #51 from Jeff Zaroyko jeffz@jeffz.name 2011-05-29 02:39:41 CDT --- I don't have ati hardware anymore. Still no response from ati/amd regarding my report to them about this.
If the problem is still present it does prevent people from running winetest on Windows successfully, so the question would still remain whether or not the crashing test should be modified to not run at all.
http://bugs.winehq.org/show_bug.cgi?id=13608
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- OS/Version|Windows XP |Windows
http://bugs.winehq.org/show_bug.cgi?id=13608
--- Comment #52 from Austin English austinenglish@gmail.com 2013-11-13 16:49:29 CST --- This is your friendly reminder that there has been no bug activity for 2 years. Is this still an issue in current (1.7.6 or newer) wine? If so, please attach the terminal output in 1.7.6 (see http://wiki.winehq.org/FAQ#get_log).
https://bugs.winehq.org/show_bug.cgi?id=13608
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |ABANDONED
--- Comment #53 from Austin English austinenglish@gmail.com --- Abandoned.
https://bugs.winehq.org/show_bug.cgi?id=13608
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #54 from Austin English austinenglish@gmail.com --- Closing.
-
wine-bugs＠winehq.org