damnit, X is crashing *every* time I run 3dmark2000

[Dan Kegel]

And always after test 17 of 20, I think.  I updated to the latest
nvidia driver supported by Ubuntu 10.04, no change.

The crash persists even with WINEDEBUG=+d3d,+d3d7,+synchronous.

I guess my next move is to drop 3dmark2000.

[Edward Savage]

On Tue, Jun 22, 2010 at 1:48 PM, Dan Kegel  wrote:
> And always after test 17 of 20, I think.  I updated to the latest
> nvidia driver supported by Ubuntu 10.04, no change.
>
> The crash persists even with WINEDEBUG=+d3d,+d3d7,+synchronous.
>
> I guess my next move is to drop 3dmark2000.

This is on the Steam page and covers your issue I believe.

WARNING Nvidia 185 Driver Series Crash
If you are using nVidia 185.x series drivers your X may crash when
attempting to run this application.  This is not a Wine bug and the
solution is to upgrade your drivers.  You can do this via nvidia.com
or your distros package management system.  Ubuntu 9.10 users can add
the nvidia-vdpau PPA to obtain the upgrade.

[Scott Ritchie]

On 06/21/2010 08:48 PM, Dan Kegel wrote:
> And always after test 17 of 20, I think.  I updated to the latest
> nvidia driver supported by Ubuntu 10.04, no change.
>
> The crash persists even with WINEDEBUG=+d3d,+d3d7,+synchronous.
>
> I guess my next move is to drop 3dmark2000.

This is exactly what I had hoped to happen when I experimented with
putting Wine's test suite in checkbox (Ubuntu's main QA tool).  I'll see
if I can add yagmark to it too and then send it upstream so the tests
get run semi-regularly on maverick.

Maybe then we won't end up with a crashing driver in the release.

Thanks,
Scott Ritchie

[Maarten Lankhorst]

Hi Scott,

2010/6/22 Scott Ritchie :
> On 06/21/2010 08:48 PM, Dan Kegel wrote:
> > And always after test 17 of 20, I think.  I updated to the latest
> > nvidia driver supported by Ubuntu 10.04, no change.
> >
> > The crash persists even with WINEDEBUG=+d3d,+d3d7,+synchronous.
> >
> > I guess my next move is to drop 3dmark2000.
>
> This is exactly what I had hoped to happen when I experimented with
> putting Wine's test suite in checkbox (Ubuntu's main QA tool).  I'll see
> if I can add yagmark to it too and then send it upstream so the tests
> get run semi-regularly on maverick.
>
> Maybe then we won't end up with a crashing driver in the release.

Depends, all d3d tests still seem a bit flaky on open source drivers,
sometimes even crashing Xorg entirely. :)

Cheers,
Maarten

[Scott Ritchie]

On 06/22/2010 01:44 AM, Maarten Lankhorst wrote:
> Hi Scott,
>
> 2010/6/22 Scott Ritchie :
> > On 06/21/2010 08:48 PM, Dan Kegel wrote:
> > > And always after test 17 of 20, I think.  I updated to the latest
> > > nvidia driver supported by Ubuntu 10.04, no change.
> > >
> > > The crash persists even with WINEDEBUG=+d3d,+d3d7,+synchronous.
> > >
> > > I guess my next move is to drop 3dmark2000.
> >
> > This is exactly what I had hoped to happen when I experimented with
> > putting Wine's test suite in checkbox (Ubuntu's main QA tool).  I'll see
> > if I can add yagmark to it too and then send it upstream so the tests
> > get run semi-regularly on maverick.
> >
> > Maybe then we won't end up with a crashing driver in the release.
>
> Depends, all d3d tests still seem a bit flaky on open source drivers,
> sometimes even crashing Xorg entirely. :)
>
> Cheers,
> Maarten

That was exactly the point - to use Wine's test suite as a "make X
crash" tool.  That way Ubuntu can detect when it's shipping a buggy
driver well before release.

Thanks,
Scott Ritchie