All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 62721] GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec...
Date: Fri, 20 Feb 2015 10:14:03 +0000	[thread overview]
Message-ID: <bug-62721-2300-dRdh1omMh2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-62721-2300@https.bugzilla.kernel.org/>

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

--- Comment #18 from Maciej Gluszek <info@maciejgluszek.com> ---
UPDATE: Seems i found a solution. So far almost 48h uptime on my laptop and no
crash. What i did, is i added "radeon.hard_reset=1" to GRUB command line.

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.dpm=1 radeon.hard_reset=1"

-- 
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:[~2015-02-20 10:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 13:03 [Bug 62721] New: GPU lockup: radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec bugzilla-daemon
2013-10-08 13:03 ` [Bug 62721] " bugzilla-daemon
2013-10-08 17:54 ` bugzilla-daemon
2013-10-09  3:40 ` bugzilla-daemon
2013-10-09 13:15 ` bugzilla-daemon
2013-10-10 17:12 ` bugzilla-daemon
2013-10-10 17:13 ` bugzilla-daemon
2013-10-14 13:52 ` bugzilla-daemon
2014-01-16  4:14 ` bugzilla-daemon
2014-01-16  4:15 ` bugzilla-daemon
2014-01-16  4:15 ` bugzilla-daemon
2014-01-16  4:25 ` bugzilla-daemon
2014-01-18  4:28 ` bugzilla-daemon
2014-10-10 12:06 ` bugzilla-daemon
2014-10-10 12:09 ` bugzilla-daemon
2014-10-21 14:28 ` bugzilla-daemon
2014-10-21 14:32 ` bugzilla-daemon
2015-02-17 18:54 ` bugzilla-daemon
2015-02-20 10:14 ` bugzilla-daemon [this message]

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-62721-2300-dRdh1omMh2@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.