From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43341] New: CoreBreach: Crash in r600_update_derived_state
Date: Tue, 29 Nov 2011 17:49:08 +0000 [thread overview]
Message-ID: <bug-43341-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=43341
Bug #: 43341
Summary: CoreBreach: Crash in r600_update_derived_state
Classification: Unclassified
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: sa@whiz.se
Created attachment 53956
--> https://bugs.freedesktop.org/attachment.cgi?id=53956
backtrace
Hi,
The game CoreBreach crashes when the ships guns are fired, or when the walls of
the racetrack are hit. This only happens when Post Processing is turned on
(which it is by default). The crash happens with both git master and in Mesa
7.11.1.
The game is so far only available as a beta:
http://phoronix.com/forums/showthread.php?65016-A-New-Commercial-Game-For-Linux-That-s-Not-An-FPS&p=240440#post240440
A backtrace is attached.
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: REDWOOD
-- Model: XFX Radeon HD 5670 1GB
-- Display connector: DVI
-- xf86-video-ati: 6.14.2
-- xserver: 1.11.1.902
-- mesa: c8db5a3d535c347193556c0d4a8fad83d96be184
-- drm: 2.4.27
-- kernel: 3.1.1
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-11-29 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 17:49 bugzilla-daemon [this message]
2011-11-29 17:59 ` [Bug 43341] CoreBreach: Crash in r600_update_derived_state bugzilla-daemon
2011-11-30 11:05 ` bugzilla-daemon
2011-11-30 15:52 ` bugzilla-daemon
2011-12-01 3:04 ` bugzilla-daemon
2011-12-01 12:13 ` bugzilla-daemon
2013-09-19 16:42 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-43341-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).