All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 75992] Display freezes & corruption with an r7 260x on 3.14-rc6
Date: Wed, 26 Mar 2014 17:33:18 +0000	[thread overview]
Message-ID: <bug-75992-502-NmSyPgxkUY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-75992-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 858 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=75992

--- Comment #7 from Ed Tomlinson <edt@aei.ca> ---
The only setting I cannot revert in the patch is:

pi->mclk_dpm_key_disabled = 1;

To avoid humdreds of: radeon 0000:01:00.0: GPU fault detected: 146 0x0aa20804
and 147 type errors I had to add: export R600_DEBUG=nohyperz in the X startup
as documented in: https://bugzilla.kernel.org/show_bug.cgi?id=66981

Also found some funny stuff to do with primary and secondary graphic cards.
booting with the primary as the builtin hd4600, with no radeon specific stuff
in the kernel command line does NOT enable the dpm on the secondary radeon card
and trying to use radeon.dpm=1 causes the X startup to stall.  Note in all
cases the a xorg.conf file selects the radeon card to be used.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1711 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

  parent reply	other threads:[~2014-03-26 17:33 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-10 17:25 [Bug 75992] New: Display freezes & corruption with an r7 260x on 3.14-rc6 bugzilla-daemon
2014-03-10 17:25 ` [Bug 75992] " bugzilla-daemon
2014-03-10 17:28 ` bugzilla-daemon
2014-03-10 20:33 ` bugzilla-daemon
2014-03-23 20:04 ` bugzilla-daemon
2014-03-24 14:55 ` bugzilla-daemon
2014-03-25 13:00 ` bugzilla-daemon
2014-03-25 14:55 ` bugzilla-daemon
2014-03-26 17:33 ` bugzilla-daemon [this message]
2014-03-27 14:36 ` bugzilla-daemon
2014-03-27 18:53 ` bugzilla-daemon
2014-03-27 22:08 ` bugzilla-daemon
2014-03-28 12:13 ` bugzilla-daemon
2014-03-28 12:19 ` bugzilla-daemon
2014-03-28 14:12 ` bugzilla-daemon
2014-03-28 17:28 ` bugzilla-daemon
2014-03-28 18:18 ` bugzilla-daemon
2014-03-28 20:09 ` bugzilla-daemon
2014-03-28 23:07 ` bugzilla-daemon
2014-04-02 16:49 ` bugzilla-daemon
2014-04-02 22:31 ` bugzilla-daemon
2014-04-07 17:18 ` bugzilla-daemon
2014-04-10 15:19 ` bugzilla-daemon
2014-04-10 17:30 ` bugzilla-daemon
2014-04-10 17:35 ` bugzilla-daemon
2014-04-10 18:37 ` bugzilla-daemon
2014-04-10 18:44 ` bugzilla-daemon
2014-04-10 19:05 ` bugzilla-daemon
2014-04-10 19:10 ` bugzilla-daemon
2014-04-10 20:26 ` bugzilla-daemon
2014-04-10 20:36 ` bugzilla-daemon
2014-04-10 21:03 ` bugzilla-daemon
2014-04-10 21:30 ` bugzilla-daemon
2014-04-10 21:45 ` bugzilla-daemon
2014-04-10 21:47 ` bugzilla-daemon
2014-04-10 21:50 ` bugzilla-daemon
2014-04-10 22:09 ` bugzilla-daemon
2014-04-10 23:40 ` bugzilla-daemon
2014-04-11  0:59 ` bugzilla-daemon
2014-04-11  3:02 ` bugzilla-daemon
2014-04-11  3:11 ` bugzilla-daemon
2014-04-11  7:45 ` bugzilla-daemon
2014-04-11  8:57 ` bugzilla-daemon
2014-04-11  9:25 ` bugzilla-daemon
2014-04-11 11:17 ` bugzilla-daemon
2014-04-11 11:18 ` bugzilla-daemon
2014-04-11 11:58 ` bugzilla-daemon
2014-04-11 12:15 ` bugzilla-daemon
2014-04-11 22:10 ` bugzilla-daemon
2014-04-11 22:17 ` bugzilla-daemon
2014-04-11 22:32 ` bugzilla-daemon
2014-04-13  5:07 ` bugzilla-daemon
2014-04-13 13:03 ` bugzilla-daemon
2014-04-14  0:32 ` bugzilla-daemon
2014-05-08 16:23 ` bugzilla-daemon
2014-05-08 16:25 ` bugzilla-daemon
2014-05-14 11:30 ` bugzilla-daemon
2014-05-14 11:52 ` bugzilla-daemon
2014-05-14 21:36 ` bugzilla-daemon
2014-05-14 21:39 ` bugzilla-daemon
2014-05-14 21:45 ` bugzilla-daemon
2019-11-20  7:58 ` 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-75992-502-NmSyPgxkUY@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 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.