Bug 100402 - [d3d9 bisected] Diablo III fails to start after commit 0630d3600bfb770cf3b23761c45b3add3b277c6b
Summary: [d3d9 bisected] Diablo III fails to start after commit 0630d3600bfb770cf3b237...
Status: RESOLVED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: 17.0
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-26 16:28 UTC by Nick Tenney
Modified: 2017-06-08 17:41 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Git Bisect Log of the issue (2.62 KB, text/x-log)
2017-03-26 16:28 UTC, Nick Tenney
Details
NINE_DEBUG=all output (10.33 MB, text/html)
2017-03-26 17:12 UTC, Nick Tenney
Details

Description Nick Tenney 2017-03-26 16:28:01 UTC
Created attachment 130468 [details]
Git Bisect Log of the issue

After much ado, I was finally able to figure out bisecting issues with nine (not really easy to figure out, that). Looks like commit id 0630d3600bfb770cf3b23761c45b3add3b277c6b removed a call that still had an impact for nouveau. Reverting the commit on newer versions did not work as the call had been removed elsewhere.  Attached is the bisection log. Note that this is on NVA5.

Point of reference: there was no breakage with my RV790 radeon box.
Comment 1 Nick Tenney 2017-03-26 17:12:11 UTC
Created attachment 130469 [details]
NINE_DEBUG=all output

The attachment includes stderr and stdout with WINEDEBUG=-all and NINE_DEBUG=all.
Comment 2 Ilia Mirkin 2017-04-02 15:20:08 UTC
Please retest with https://cgit.freedesktop.org/mesa/mesa/commit/?id=7a0c1eee0c25e343d8c276e4471e4a113d61f233 and let me know if that's fixed now.
Comment 3 Nick Tenney 2017-06-08 17:41:18 UTC
Finally (a) got a chance to test and (b) had success with latest mesa from git. Closing out as fixed. Thanks!


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.