Summary: | [NV92] Psychonauts (native) segfaults on start when DRI3 enabled | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Béla Gyebrószki <gyebro69> | ||||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | gyebro69 | ||||||||
Version: | unspecified | Keywords: | bisected, regression | ||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Béla Gyebrószki
2015-07-05 03:28:02 UTC
Created attachment 116945 [details]
XOrg.log
The assertion is regarding PIPE_BIND_SCANOUT + nr_samples != 0. I suspect this might be a dri st bug which only surfaces with the new mechanisms that dri3 enables. Created attachment 116946 [details]
backtrace from the game and glretrace
If you have a Steam account and Steam for Linux installed you can reproduce the segfault with these native Linux demos on Steam:
- 'Running with Rifles' demo (note: I had to remove libstdc++.so.6 and libxcb.so.1 from ./lib).
- Torchlight II demo (the game starts with default settings, you need to enable anti-aliasing in-game option and restart the game to reproduce this bug).
All those games crash on start with
>nv50/nv50_miptree.c:132: nv50_mt_choose_storage_type: Assertion `ms == 0' failed.
when DRI3 is enabled.
Marek posted a patch for this at http://patchwork.freedesktop.org/patch/53843/ (In reply to Ilia Mirkin from comment #5) > Marek posted a patch for this at > http://patchwork.freedesktop.org/patch/53843/ The patch works and fixes the problem in all the affected games that I know of. Thank you both for your help fixing this bug. Patch committed, marking the bug as fixed. http://cgit.freedesktop.org/mesa/mesa/commit/?id=6611f65047575054a38ce83ebfe0331e39e1774f |
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.