From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 91268] R6xx freezes with kernel 3.17 and up
Date: Thu, 16 Jul 2015 14:37:26 +0000 [thread overview]
Message-ID: <bug-91268-502-vqsKLCIcbj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91268-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 970 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91268
--- Comment #13 from Kajzer <kap3tan@gmail.com> ---
(In reply to Alex Deucher from comment #12)
> Just to be clear, does this bug only happen when you force dpm on or all the
> time?
If I don't set performance to high then it hangs all the time (not just in
gaming) and I can provoke it within minutes, regardless of kernel version.
This bug (CPU mappings) happens only while playing games and with kernels above
3.16
So, will this bug happen if I don't force performance to high ?
To be honest I don't know, been a while since I was on anything else other than
high, because for sure the other bug would happen, and they behave the same
when the hang happens.
So I guess it would hang if I don't force it.
Except maybe if there were some kind of mappings in the kernel before 3.17 and
that somehow both bugs are related.
That I don't know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1776 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:[~2015-07-16 14:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 12:15 [Bug 91268] R6xx freezes with kernel 3.17 and up bugzilla-daemon
2015-07-11 19:20 ` bugzilla-daemon
2015-07-12 2:20 ` bugzilla-daemon
2015-07-12 12:37 ` bugzilla-daemon
2015-07-13 14:19 ` bugzilla-daemon
2015-07-13 15:30 ` bugzilla-daemon
2015-07-15 3:30 ` bugzilla-daemon
2015-07-15 12:27 ` bugzilla-daemon
2015-07-15 12:29 ` bugzilla-daemon
2015-07-16 3:52 ` bugzilla-daemon
2015-07-16 13:12 ` bugzilla-daemon
2015-07-16 13:56 ` bugzilla-daemon
2015-07-16 13:58 ` bugzilla-daemon
2015-07-16 14:37 ` bugzilla-daemon [this message]
2015-07-16 14:43 ` bugzilla-daemon
2015-07-16 14:49 ` bugzilla-daemon
2015-07-16 15:03 ` bugzilla-daemon
2015-07-16 16:15 ` bugzilla-daemon
2015-07-17 3:06 ` bugzilla-daemon
2015-07-17 3:30 ` bugzilla-daemon
2015-07-24 19:38 ` bugzilla-daemon
2015-07-24 19:42 ` bugzilla-daemon
2015-08-04 10:00 ` bugzilla-daemon
2015-08-04 14:33 ` bugzilla-daemon
2015-10-29 20:34 ` bugzilla-daemon
2015-11-26 8:17 ` bugzilla-daemon
2016-01-29 2:42 ` bugzilla-daemon
2016-03-22 15:54 ` 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-91268-502-vqsKLCIcbj@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).