Bug 25355 - sauerbraten segfaults after 63c00c53a3019b801c5eee8a12f7862422f79f10
Summary: sauerbraten segfaults after 63c00c53a3019b801c5eee8a12f7862422f79f10
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/R100 (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
: 25478 (view as bug list)
Depends on:
Reported: 2009-11-30 02:39 UTC by Fabio Pedretti
Modified: 2009-12-10 00:48 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

sauerbraten gdb backtrace (2.43 KB, text/plain)
2009-11-30 02:39 UTC, Fabio Pedretti
proposed patch (1011 bytes, text/plain)
2009-12-02 14:10 UTC, Maciej Cencora

Description Fabio Pedretti 2009-11-30 02:39:41 UTC
Created attachment 31575 [details]
sauerbraten gdb backtrace

Since this commit sauerbraten crashes when loading every map. Backtrace is attached. Using current mesa_7_7_branch without KMS with:
GL_RENDERER   = Mesa DRI R300 (RV530 71C5) 20090101 x86/MMX/SSE2 TCL

63c00c53a3019b801c5eee8a12f7862422f79f10 is first bad commit
commit 63c00c53a3019b801c5eee8a12f7862422f79f10
Author: Maciej Cencora <m.cencora@gmail.com>
Date:   Sun Nov 29 15:40:13 2009 +0100

    radeon: update miptree code a little
    Simplify gl image level <-> miptree level mapping (are equal now).
    Don't allocate miptree for images that won't fit in it (fixes #25230).

:040000 040000 6a0ace3925115784b57071e132af539d1e0c3536 5cdd6fd66a93b76ffc55386fb5fcd1c506be87d8 M	src
Comment 1 Maciej Cencora 2009-12-02 14:10:27 UTC
Created attachment 31685 [details]
proposed patch

Attached patch should fix the problem.
Comment 2 Fabio Pedretti 2009-12-03 00:17:24 UTC
It works indeed, thanks!
Comment 3 Maciej Cencora 2009-12-03 11:25:21 UTC
Patch landed on mesa_7_7_branch. Closing.
Comment 4 Fabio Pedretti 2009-12-10 00:48:26 UTC
*** Bug 25478 has been marked as a duplicate of this bug. ***

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.