https://bugs.freedesktop.org/show_bug.cgi?id=64471
Priority: medium
Bug ID: 64471
Assignee: dri-devel at lists.freedesktop.org
Summary: Radeon HD6570 lockup in Br?tal Legend
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: zboszor at 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.freedesktop.org/archives/dri-devel/attachments/20130511/a30a6fbc/attachment.html>
