All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 72701] Screen freeze when using radeon driver
Date: Wed, 12 Nov 2014 17:01:21 +0000	[thread overview]
Message-ID: <bug-72701-2300-JmAUZn4cb4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-72701-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=72701

--- Comment #22 from EmanueL Czirai <emanueLczirai@openmailbox.org> ---
In order to avoid any freezes, with the caveat that the DIScrete card won't
ever be turned off (even by # echo 'OFF' >
/sys/kernel/debug/vgaswitcheroo/switch  which would have no effect) I am using:
 radeon.dpm=1 radeon.runpm=1
with the above patch[originally made by  Alex Deucher above in Comment #14 ]
(which I also put here
https://github.com/emanueLczirai/coostomhuston/blob/a3c118ac44b616ebcc049419cc08c4d13ebb44bd/system/lenovo%20z575/OS/manjaro/filesystem%20now/home/emacs/build/kernel/linuxgit/2100_DIScrete_gfx_card_systemfreeze.patch
)

As per our irc conversation, it would seem that maybe the lenovo board requires
some quirk in order to avoid the system freeze and thus I accept the current
workaround. Besides, I always keep my DIS card off from BIOS anyway (the BIOS
Graphics: UDMA setting(instead of Dynamic), does this)

I am thus then giving up on this for now, but I'm always ready to test new
ideas, if any should arise.

Thank you.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-11-12 17:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22 16:22 [Bug 72701] New: Screen freeze when using radeon driver bugzilla-daemon
2014-03-22 16:24 ` [Bug 72701] " bugzilla-daemon
2014-03-22 16:50 ` bugzilla-daemon
2014-03-22 20:32 ` bugzilla-daemon
2014-03-24 14:39 ` bugzilla-daemon
2014-03-24 19:06 ` bugzilla-daemon
2014-03-24 19:12 ` bugzilla-daemon
2014-03-24 19:30 ` bugzilla-daemon
2014-04-01 19:42 ` bugzilla-daemon
2014-04-01 19:51 ` bugzilla-daemon
2014-04-01 21:53 ` bugzilla-daemon
2014-04-01 22:36 ` bugzilla-daemon
2014-04-07  2:13 ` bugzilla-daemon
2014-04-09  0:04 ` bugzilla-daemon
2014-04-09  2:07 ` bugzilla-daemon
2014-04-09  5:59 ` bugzilla-daemon
2014-07-14 10:08 ` bugzilla-daemon
2014-07-14 11:43 ` bugzilla-daemon
2014-07-14 11:46 ` bugzilla-daemon
2014-07-14 11:48 ` bugzilla-daemon
2014-07-14 12:05 ` bugzilla-daemon
2014-07-14 16:29 ` bugzilla-daemon
2014-11-12 15:53 ` bugzilla-daemon
2014-11-12 17:01 ` bugzilla-daemon [this message]
2016-03-27 21:49 ` 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-72701-2300-JmAUZn4cb4@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.