From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70411] New: 7970M PRIME: lockup with Distance game, recovery doesn't work
Date: Tue, 11 Feb 2014 21:38:15 +0000 [thread overview]
Message-ID: <bug-70411-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=70411
Bug ID: 70411
Summary: 7970M PRIME: lockup with Distance game, recovery
doesn't work
Product: Drivers
Version: 2.5
Kernel Version: 3.13-3.14-rc2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: haagch.christoph@googlemail.com
Regression: Yes
Created attachment 125651
--> https://bugzilla.kernel.org/attachment.cgi?id=125651&action=edit
dmesg of radeon getting stuck
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Wimbledon XT [Radeon HD 7970M]
Using PRIME to render on the gpu etc.
This has been going on for a while and I sadly don't really know since when,
maybe later I'll test older kernels.
It has worked some time ago (again, no specifics, but I think it was 3.12
(without dpm, maybe it's relevant).
I report this because this is specifically happening with the Distance game in
the Alpha version only available to kickstarter backers (I believe).
http://survivethedistance.com/ (Surely there is a way to get this into the
hands of driver developers if it is useful for finding out if more GPUs and
configurations are affected and fixing bugs!)
Well, it's alpha so it's maybe buggy, but it shouldn't bring the radeon driver
down to an unrecoverable status... (I believe restarting X doesn't help and
rmmod radeon doesn't really work currently)
I don't really see lockups with other 3D programs so this is specifically for
Distance.
It's reproducible every time so I can later get more detail. For now there's
the dmesg: Starting the game and showing some intro works, but shortly before
displaying the menu X freezes for a few seconds and after it is usable again, I
see the stuff starting at 82688.801309 in dmesg. The game window is still
there, but frozen and killable with -9.
Unfortunately the gpu has not recovered and e.g. trying to run DRI_PRIME=1
glxgears results in the message:
radeon: The kernel rejected CS, see dmesg for more information.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2014-02-11 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 21:38 bugzilla-daemon [this message]
2014-02-12 3:49 ` [Bug 70411] 7970M PRIME: lockup with Distance game, recovery doesn't work bugzilla-daemon
2014-02-12 7:58 ` bugzilla-daemon
2014-02-12 8:20 ` bugzilla-daemon
2014-02-12 14:59 ` bugzilla-daemon
2014-05-26 23:24 ` 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-70411-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.