dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38488] New: AMD Radeon HD 6950 (Cayman): Clocks not restored after resume from hibernation
Date: Mon, 20 Jun 2011 01:32:26 -0700 (PDT)	[thread overview]
Message-ID: <bug-38488-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: AMD Radeon HD 6950 (Cayman): Clocks not restored after
                    resume from hibernation
           Product: DRI
           Version: XOrg CVS
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: h.judt@gmx.at


Power profile does not work after resuming.

Steps to reproduce:

1) Boot system, set power profile to low.

$ cat /sys/kernel/debug/dri/64/radeon_pm_info:
default engine clock: 800000 kHz
current engine clock: 249990 kHz
default memory clock: 1250000 kHz
current memory clock: 150000 kHz
voltage: 900 mV

2) Hibernate system and resume.

Expected results:

* Power profile still set to low, clocks stay at low level.

* Power profile can be changed, and changes have desired effects.

Actual results:

* Power profile still shows "low", but according to debugfs clocks are at
default levels:

    default engine clock: 800000 kHz
    current engine clock: 799940 kHz
    default memory clock: 1250000 kHz
    current memory clock: 1250000 kHz
    voltage: 65281 mV

Voltage does seem strange too, when regarding the 900 mV above.

* Power profile can be changed, but clocks will not change.

* Fan is spinning louder due to the higher (default instead of low level) clock
speeds.

I have to admit that I modified and applied tuxonice patch to linux-3.0-rc3,
but on a laptop at work I use exactly the same and everything works correctly
there (ATI Mobility Radeon HD 3400), so I don't believe I messed up. Cayman
support is still quite new...

Is there another way to change the clock speeds?

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2011-06-20  8:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-20  8:32 bugzilla-daemon [this message]
2011-06-22 16:24 ` [Bug 38488] AMD Radeon HD 6950 (Cayman): Clocks not restored after resume from hibernation bugzilla-daemon
2011-06-22 22:19 ` bugzilla-daemon
2011-06-22 22:26 ` bugzilla-daemon
2011-06-23  9:36 ` bugzilla-daemon
2011-06-23 15:00 ` bugzilla-daemon
2011-06-23 18:18 ` bugzilla-daemon
2011-06-23 18:21 ` bugzilla-daemon
2011-06-23 19:03 ` bugzilla-daemon
2011-06-23 19:55 ` bugzilla-daemon
2011-06-28 18:24 ` bugzilla-daemon
2011-07-30 11:27 ` [Bug 38488] AMD Radeon HD 6950 (Cayman): Power profile has no effect " bugzilla-daemon
2011-09-18 13:02 ` bugzilla-daemon
2011-11-11 21:53 ` 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-38488-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox