All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76130] New: Radeon HD 4570 set dpm state fails after suspend
Date: Thu, 13 Mar 2014 17:21:53 +0000	[thread overview]
Message-ID: <bug-76130-502@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 76130
          Assignee: dri-devel@lists.freedesktop.org
           Summary: Radeon HD 4570 set dpm state fails after suspend
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: crew4ok@gmail.com
          Hardware: x86 (IA32)
            Status: NEW
           Version: unspecified
         Component: DRM/Radeon
           Product: DRI

Created attachment 95731
  --> https://bugs.freedesktop.org/attachment.cgi?id=95731&action=edit
dmesg

Right before the system go to suspend, the following line appears in dmesg:

[drm:rv730_stop_dpm] *ERROR* Could not force DPM to low

After wakeup i see this in dmesg:

[drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed

Also i notice a degradation in performance in some games (e.g. in Teeworlds
before the suspend i have 60fps, after suspend - 30-40 fps).

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

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

             reply	other threads:[~2014-03-13 17:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-13 17:21 bugzilla-daemon [this message]
2014-03-13 17:26 ` [Bug 76130] Radeon HD 4570 set dpm state fails after suspend bugzilla-daemon
2014-03-13 18:49 ` bugzilla-daemon
2014-03-14 18:26 ` bugzilla-daemon
2014-06-13  6:37 ` bugzilla-daemon
2014-07-03 22:50 ` bugzilla-daemon
2014-11-05 16:40 ` bugzilla-daemon
2015-02-01 11:41 ` bugzilla-daemon
2015-04-28 23:25 ` bugzilla-daemon
2015-04-28 23:35 ` bugzilla-daemon
2015-04-29 16:04 ` bugzilla-daemon
2015-04-29 16:07 ` bugzilla-daemon
2015-04-29 18:38 ` bugzilla-daemon
2015-04-30 23:00 ` bugzilla-daemon
2015-05-02 10:22 ` bugzilla-daemon
2015-11-08 21:18 ` bugzilla-daemon
2015-11-09 19:26 ` bugzilla-daemon
2015-11-23 21:46 ` bugzilla-daemon
2015-11-24 16:08 ` bugzilla-daemon
2015-11-24 17:46 ` bugzilla-daemon
2015-11-24 17:47 ` bugzilla-daemon
2015-11-24 18:39 ` bugzilla-daemon
2015-11-30 22:45 ` bugzilla-daemon
2016-06-14  8:54 ` bugzilla-daemon
2017-08-07 18:50 ` bugzilla-daemon
2019-11-19  8:45 ` 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-76130-502@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.