From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 64471] New: Radeon HD6570 lockup in Brütal Legend
Date: Sat, 11 May 2013 13:02:12 +0000 [thread overview]
Message-ID: <bug-64471-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1558 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=64471
Priority: medium
Bug ID: 64471
Assignee: dri-devel@lists.freedesktop.org
Summary: Radeon HD6570 lockup in Brütal Legend
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: zboszor@pr.hu
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 79165
--> https://bugs.freedesktop.org/attachment.cgi?id=79165&action=edit
Lockup from "new game"
I tried Brütal Legend on Fedora 18/x86_64, the game itself if i386.
The system has these newer-than-Fedora18 components:
kernel 3.9+ (commit 51a26ae7a14b85c99c9be470c2d28eeeba0f26a3)
libdrm 2.4.44 from 2.4.44-2.fc20 SRPM from Koji recompiled on F18
llvm-3.3 from May 7, before branching to 3.3 was done
mesa 9.2 from May 7, commit was around 03ef60681e61a52dee7fa3285618c313cf13f50c
compiled into an RPM with float textures enabled:
$ rpm -q mesa-libGL
mesa-libGL-9.2-0.1.fc18.x86_64
mesa-libGL-9.2-0.1.fc18.i686
The game makes the Radeon chip lock up, reliably at the same point,
which is when the game starts after the long cutscene.
Attached are two dmesgs, showing the same lockup.
The first occurred when I started a new game and watched through the cutscene.
The second occurred when I tried to continue the auto-saved game.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3093 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2013-05-11 13:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 13:02 bugzilla-daemon [this message]
2013-05-11 13:02 ` [Bug 64471] Radeon HD6570 lockup in Brütal Legend bugzilla-daemon
2013-05-11 19:36 ` bugzilla-daemon
2013-05-12 6:27 ` bugzilla-daemon
2013-05-12 6:47 ` bugzilla-daemon
2013-05-24 17:08 ` bugzilla-daemon
2013-05-29 3:29 ` [Bug 64471] Radeon HD6570 lockup in Brütal Legend with HyperZ bugzilla-daemon
2013-05-29 3:30 ` bugzilla-daemon
2013-06-10 22:43 ` bugzilla-daemon
2013-08-05 9:01 ` bugzilla-daemon
2013-10-30 14:14 ` bugzilla-daemon
2013-10-31 2:51 ` bugzilla-daemon
2013-10-31 2:53 ` bugzilla-daemon
2013-11-12 11:19 ` bugzilla-daemon
2013-12-25 16:10 ` bugzilla-daemon
2014-01-23 20:39 ` bugzilla-daemon
2014-02-06 16:50 ` bugzilla-daemon
2014-02-07 17:58 ` bugzilla-daemon
2014-02-10 21:19 ` bugzilla-daemon
2014-02-17 18:58 ` bugzilla-daemon
2014-02-17 21:09 ` bugzilla-daemon
2014-02-18 6:42 ` bugzilla-daemon
2014-02-18 6:48 ` bugzilla-daemon
2014-02-18 7:32 ` bugzilla-daemon
2014-02-18 15:36 ` bugzilla-daemon
2014-02-18 16:05 ` bugzilla-daemon
2014-08-24 13:40 ` bugzilla-daemon
2014-08-25 19:07 ` bugzilla-daemon
2014-09-01 19:35 ` bugzilla-daemon
2014-12-29 21:34 ` bugzilla-daemon
2014-12-29 23:00 ` bugzilla-daemon
2014-12-30 10:00 ` bugzilla-daemon
2014-12-31 1:30 ` bugzilla-daemon
2015-02-07 13:43 ` 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-64471-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).