Bug 26788 - Opengl Gallium driver for r500 crashes after "Loading Area" in NWN
Summary: Opengl Gallium driver for r500 crashes after "Loading Area" in NWN
Status: CLOSED FIXED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Other (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-27 05:13 UTC by Krzysztof A. Sobiecki
Modified: 2010-02-27 15:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Backtrace (2.25 KB, text/plain)
2010-02-27 05:13 UTC, Krzysztof A. Sobiecki
Details
Small patch (473 bytes, patch)
2010-02-27 05:15 UTC, Krzysztof A. Sobiecki
Details | Splinter Review
Possible fix (7.52 KB, patch)
2010-02-27 08:12 UTC, Marek Olšák
Details | Splinter Review

Description Krzysztof A. Sobiecki 2010-02-27 05:13:42 UTC
Created attachment 33620 [details]
Backtrace

Commit e6632b4bf7cba5fe8a77d54635a3b617fa67185f causes gallium driver to catch assert in 
*__GI___assert_fail (assertion=0xf6c26f34 "boi->space_accounted", file=0xf6c26f24 "radeon_cs_gem.c", line=129, function=0xf6c27039 "cs_gem_write_reloc#4  0xf6c258eb in cs_gem_write_reloc () from /usr/lib32/libdrm_radeon.so.1

Removing assert from radeon_cs_gem.c:129 in drm "fixes" this problem.
Comment 1 Krzysztof A. Sobiecki 2010-02-27 05:15:54 UTC
Created attachment 33621 [details] [review]
Small patch

It's only a workaround solution.
Comment 2 Marek Olšák 2010-02-27 08:12:58 UTC
Created attachment 33625 [details] [review]
Possible fix

Please let me know if the attached patch helps you.
Comment 3 Krzysztof A. Sobiecki 2010-02-27 14:35:10 UTC
After applying your patch, I was unable to reproduce this bug any more. I didn't saw any regressions so far.
Comment 4 Marek Olšák 2010-02-27 15:50:52 UTC
Thanks for testing, I pushed the patch to master. Closing...


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.