From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 68235] Display freezes after login with kernel 3.11.0-rc5 on Cayman with dpm=1
Date: Wed, 18 Sep 2013 21:44:15 +0000 [thread overview]
Message-ID: <bug-68235-502-DETHJF2fO7@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-68235-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 561 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=68235
--- Comment #33 from Alex Deucher <agd5f@yahoo.com> ---
Created attachment 86111
--> https://bugs.freedesktop.org/attachment.cgi?id=86111&action=edit
testing patch - force mclk to high
Try this patch by itself. This patch will force the mclk to the highest for
all performance levels. If it works, the issue is probably related to the
changing of mclks, if not, then we are probably programming one of the mclk
parameters wrong.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1618 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-09-18 21:44 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-18 1:33 [Bug 68235] New: Display freezes after login with kernel 3.11.0-rc5 on Cayman with dpm=1 bugzilla-daemon
2013-08-18 1:35 ` [Bug 68235] " bugzilla-daemon
2013-08-22 4:42 ` bugzilla-daemon
2013-08-23 2:33 ` bugzilla-daemon
2013-08-25 3:50 ` bugzilla-daemon
2013-08-26 15:13 ` bugzilla-daemon
2013-08-26 15:53 ` bugzilla-daemon
2013-08-27 5:10 ` bugzilla-daemon
2013-08-27 6:32 ` bugzilla-daemon
2013-09-03 3:57 ` bugzilla-daemon
2013-09-03 4:47 ` bugzilla-daemon
2013-09-03 23:42 ` bugzilla-daemon
2013-09-03 23:43 ` bugzilla-daemon
2013-09-07 0:12 ` bugzilla-daemon
2013-09-10 17:31 ` bugzilla-daemon
2013-09-10 18:15 ` bugzilla-daemon
2013-09-10 19:55 ` bugzilla-daemon
2013-09-10 19:55 ` bugzilla-daemon
2013-09-10 20:40 ` bugzilla-daemon
2013-09-11 1:46 ` bugzilla-daemon
2013-09-12 4:00 ` bugzilla-daemon
2013-09-12 5:36 ` bugzilla-daemon
2013-09-12 13:26 ` bugzilla-daemon
2013-09-12 13:31 ` bugzilla-daemon
2013-09-12 14:53 ` bugzilla-daemon
2013-09-13 6:04 ` bugzilla-daemon
2013-09-13 19:13 ` bugzilla-daemon
2013-09-13 22:25 ` bugzilla-daemon
2013-09-13 22:32 ` bugzilla-daemon
2013-09-14 1:19 ` bugzilla-daemon
2013-09-17 14:19 ` bugzilla-daemon
2013-09-17 14:34 ` bugzilla-daemon
2013-09-17 22:54 ` bugzilla-daemon
2013-09-18 21:44 ` bugzilla-daemon [this message]
2013-09-18 21:46 ` bugzilla-daemon
2013-09-19 0:37 ` bugzilla-daemon
2013-09-19 5:32 ` bugzilla-daemon
2013-09-19 5:44 ` bugzilla-daemon
2013-09-19 6:15 ` bugzilla-daemon
2013-09-19 6:30 ` bugzilla-daemon
2013-09-19 13:38 ` bugzilla-daemon
2013-09-19 14:46 ` bugzilla-daemon
2013-09-19 15:34 ` bugzilla-daemon
2013-09-19 21:49 ` bugzilla-daemon
2013-09-21 19:45 ` bugzilla-daemon
2013-09-21 19:45 ` bugzilla-daemon
2013-09-22 16:51 ` bugzilla-daemon
2013-09-22 16:55 ` bugzilla-daemon
2013-09-23 2:50 ` bugzilla-daemon
2013-09-23 3:04 ` bugzilla-daemon
2013-09-23 14:07 ` bugzilla-daemon
2013-09-23 16:15 ` bugzilla-daemon
2013-09-25 1:47 ` 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-68235-502-DETHJF2fO7@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).