From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69723] Computer freezes with kernel 3.11.0 / 3.12-rc1 (with bug 68235's patches applied) when dpm=1 on r600g (Cayman)
Date: Fri, 08 Nov 2013 01:31:29 +0000 [thread overview]
Message-ID: <bug-69723-502-veQAl3eTK8@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69723-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1131 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69723
--- Comment #24 from Alex Deucher <agd5f@yahoo.com> ---
(In reply to comment #23)
> Well, maybe the first thing would be to identify when or what sequence leads
> to the hang. That's why I was suggesting to trace it. But if I understand
> you correctly, you are saying the GPU is programmed once and then we just
> move from state to another, right?
>
> I'm not sure, but I think I've read somewhere it was possible to set a power
> state manually, to force dpm to a given state in other words. Am I right?
A power state consists of several performance levels (generally 3 on cayman;
low, medium, and high). The driver loads a power state and then the GPU
dynamically changes between the performance levels within that state based on
GPU load. You can force the GPU to always stay in the low or high state via
sysfs. See:
http://www.botchco.com/agd5f/?p=57
for more info. That basically tells the GPU to stay in that performance level
and to not dynamically transition between performance levels.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2161 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-11-08 1:31 UTC|newest]
Thread overview: 128+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 16:36 [Bug 69723] New: Computer freezes with kernel 3.11.0 / 3.12-rc1 (with bug 68235's patches applied) when dpm=1 on r600g (Cayman) bugzilla-daemon
2013-09-23 23:20 ` [Bug 69723] " bugzilla-daemon
2013-09-25 1:05 ` bugzilla-daemon
2013-09-25 1:47 ` bugzilla-daemon
2013-09-25 1:57 ` bugzilla-daemon
2013-09-26 17:08 ` bugzilla-daemon
2013-09-26 17:27 ` bugzilla-daemon
2013-09-26 17:47 ` bugzilla-daemon
2013-09-29 1:29 ` bugzilla-daemon
2013-09-30 5:37 ` bugzilla-daemon
2013-10-01 3:09 ` bugzilla-daemon
2013-10-01 3:15 ` bugzilla-daemon
2013-10-01 13:19 ` bugzilla-daemon
2013-10-01 13:32 ` bugzilla-daemon
2013-10-01 17:42 ` bugzilla-daemon
2013-10-02 6:08 ` bugzilla-daemon
2013-10-26 4:32 ` bugzilla-daemon
2013-10-27 0:13 ` bugzilla-daemon
2013-10-27 0:39 ` bugzilla-daemon
2013-10-27 5:02 ` bugzilla-daemon
2013-11-07 20:23 ` bugzilla-daemon
2013-11-07 22:07 ` bugzilla-daemon
2013-11-07 22:10 ` bugzilla-daemon
2013-11-07 22:14 ` bugzilla-daemon
2013-11-08 0:15 ` bugzilla-daemon
2013-11-08 1:31 ` bugzilla-daemon [this message]
2013-11-08 4:13 ` bugzilla-daemon
2013-11-08 6:32 ` bugzilla-daemon
2013-11-08 6:44 ` bugzilla-daemon
2013-11-08 7:39 ` bugzilla-daemon
2013-11-14 5:31 ` bugzilla-daemon
2013-11-14 14:42 ` bugzilla-daemon
2013-11-14 15:06 ` bugzilla-daemon
2013-11-15 6:50 ` bugzilla-daemon
2013-11-19 5:50 ` [Bug 69723] GPU lockups " bugzilla-daemon
2013-11-24 7:06 ` bugzilla-daemon
2013-11-24 20:54 ` bugzilla-daemon
2013-11-24 20:57 ` bugzilla-daemon
2013-11-25 3:18 ` [Bug 69723] GPU lockups with kernel 3.11.0 / 3.12-rc1 " bugzilla-daemon
2013-11-25 18:12 ` bugzilla-daemon
2013-11-25 19:53 ` bugzilla-daemon
2013-11-26 22:47 ` bugzilla-daemon
2013-11-26 23:13 ` bugzilla-daemon
2013-11-27 1:39 ` bugzilla-daemon
2013-11-27 2:19 ` bugzilla-daemon
2013-11-27 4:16 ` bugzilla-daemon
2013-11-27 4:30 ` bugzilla-daemon
2013-11-27 5:01 ` bugzilla-daemon
2013-11-27 6:04 ` bugzilla-daemon
2013-11-27 14:14 ` bugzilla-daemon
2013-11-28 14:50 ` bugzilla-daemon
2013-11-29 1:21 ` bugzilla-daemon
2013-11-29 2:57 ` bugzilla-daemon
2013-11-29 15:46 ` bugzilla-daemon
2013-11-29 15:47 ` bugzilla-daemon
2013-11-29 19:31 ` bugzilla-daemon
2013-12-02 23:33 ` bugzilla-daemon
2013-12-08 17:37 ` bugzilla-daemon
2013-12-08 18:15 ` bugzilla-daemon
2013-12-08 18:31 ` bugzilla-daemon
2013-12-09 2:02 ` bugzilla-daemon
2013-12-09 7:42 ` bugzilla-daemon
2013-12-09 16:56 ` bugzilla-daemon
2013-12-09 20:01 ` bugzilla-daemon
2013-12-09 20:37 ` bugzilla-daemon
2013-12-09 20:43 ` bugzilla-daemon
2013-12-09 22:59 ` bugzilla-daemon
2013-12-10 0:01 ` bugzilla-daemon
2013-12-10 1:08 ` bugzilla-daemon
2013-12-10 2:14 ` bugzilla-daemon
2013-12-10 4:31 ` bugzilla-daemon
2013-12-10 9:09 ` bugzilla-daemon
2013-12-10 19:20 ` bugzilla-daemon
2013-12-11 3:33 ` bugzilla-daemon
2013-12-11 3:36 ` bugzilla-daemon
2013-12-11 19:26 ` bugzilla-daemon
2013-12-11 19:59 ` bugzilla-daemon
2013-12-12 14:07 ` bugzilla-daemon
2013-12-12 14:55 ` bugzilla-daemon
2013-12-13 2:48 ` bugzilla-daemon
2013-12-13 3:03 ` bugzilla-daemon
2013-12-13 5:39 ` bugzilla-daemon
2013-12-13 8:21 ` bugzilla-daemon
2013-12-13 17:12 ` bugzilla-daemon
2013-12-16 6:13 ` bugzilla-daemon
2013-12-16 20:11 ` bugzilla-daemon
2013-12-20 1:27 ` bugzilla-daemon
2013-12-20 13:42 ` bugzilla-daemon
2013-12-22 1:46 ` bugzilla-daemon
2014-01-12 21:19 ` bugzilla-daemon
2014-01-12 22:26 ` bugzilla-daemon
2014-01-12 23:30 ` bugzilla-daemon
2014-01-15 21:02 ` bugzilla-daemon
2014-01-15 21:15 ` bugzilla-daemon
2014-01-15 21:17 ` bugzilla-daemon
2014-01-15 21:33 ` bugzilla-daemon
2014-01-16 8:12 ` bugzilla-daemon
2014-01-16 20:39 ` bugzilla-daemon
2014-01-17 15:43 ` bugzilla-daemon
2014-01-17 15:53 ` bugzilla-daemon
2014-01-17 16:36 ` bugzilla-daemon
2014-01-18 3:08 ` bugzilla-daemon
2014-01-18 12:48 ` bugzilla-daemon
2014-01-18 17:01 ` bugzilla-daemon
2014-01-20 13:58 ` bugzilla-daemon
2014-01-23 2:28 ` bugzilla-daemon
2014-01-30 17:37 ` bugzilla-daemon
2014-01-30 18:30 ` bugzilla-daemon
2014-02-02 19:47 ` bugzilla-daemon
2014-03-07 4:32 ` bugzilla-daemon
2014-03-07 14:12 ` bugzilla-daemon
2014-03-11 19:12 ` bugzilla-daemon
2014-04-11 22:19 ` bugzilla-daemon
2014-04-11 22:23 ` bugzilla-daemon
2014-04-21 16:28 ` bugzilla-daemon
2014-07-01 16:19 ` bugzilla-daemon
2014-07-01 18:32 ` bugzilla-daemon
2014-07-01 20:15 ` bugzilla-daemon
2014-07-02 22:27 ` bugzilla-daemon
2014-07-03 2:52 ` bugzilla-daemon
2014-07-03 7:30 ` bugzilla-daemon
2014-07-04 21:28 ` bugzilla-daemon
2014-07-06 16:42 ` bugzilla-daemon
2014-07-06 20:27 ` bugzilla-daemon
2014-07-06 20:33 ` bugzilla-daemon
2014-07-07 17:13 ` bugzilla-daemon
2014-07-11 18:22 ` bugzilla-daemon
2014-07-11 20:12 ` 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-69723-502-veQAl3eTK8@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).