From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66961] radeon gpu stall with Legend of Grimrock
Date: Mon, 19 Aug 2013 07:43:51 +0000 [thread overview]
Message-ID: <bug-66961-502-13hLlRfp3m@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66961-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 665 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=66961
--- Comment #4 from Knut Andre Tidemann <knut.tidemann@gmail.com> ---
This might be due to a overheat issue.
I just got another GPU lockup while playing the game (after a few hours) and it
did not cause the kernel OOPS/Bug in question, so everything went on as normal
after the GPU recovered.
However, after a few minutes I lost the display (it went black). Logging in
over SSH and checking the temperature sensor revealed that the radeon GPU
reported 127.5C.
So unless someone else has seen this issue, I think it can be discarded.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1431 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 prev parent reply other threads:[~2013-08-19 7:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 13:09 [Bug 66961] New: Kernel BUG/Oops during radeon gpu stall bugzilla-daemon
2013-07-16 13:15 ` [Bug 66961] radeon gpu stall with Legend of Grimrock bugzilla-daemon
2013-07-16 13:17 ` bugzilla-daemon
2013-07-16 13:19 ` bugzilla-daemon
2013-08-19 7:43 ` bugzilla-daemon [this message]
2019-09-18 19:04 ` 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-66961-502-13hLlRfp3m@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).