All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 38657] New: Redwood: power state #4 not used
Date: Fri, 24 Jun 2011 15:45:28 -0700 (PDT)	[thread overview]
Message-ID: <bug-38657-502@http.bugs.freedesktop.org/> (raw)

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

           Summary: Redwood: power state #4 not used
           Product: DRI
           Version: unspecified
          Platform: All
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: DRM/Radeon
        AssignedTo: dri-devel@lists.freedesktop.org
        ReportedBy: mkgmafbt@gmail.com


Created an attachment (id=48390)
 --> (https://bugs.freedesktop.org/attachment.cgi?id=48390)
Part of dmesg with power states

It's a Sapphire Radeon HD5670 512MB GDDR5. DRM reports 5 power states, but low
profile won't use #4, wich is the 2D profile, nor does dynpm. All kernels with
Evergreen pm support are affected by this (possible) bug, including 3.0-rc4.

cat /sys/class/drm/card0/device/power_profile 
low

cat /sys/kernel/debug/dri/0/radeon_pm_info
default engine clock: 775000 kHz
current engine clock: 399990 kHz
default memory clock: 950000 kHz
current memory clock: 950000 kHz
voltage: 1100 mV
PCIE lanes: 16

(should be 150/300 MHz 0.9V)

lspci -nn | grep  VGA
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc Redwood [Radeon
HD 5670] [1002:68d8]

-- 
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-24 22:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 22:45 bugzilla-daemon [this message]
2011-06-28 15:53 ` [Bug 38657] Redwood: power state #4 not used bugzilla-daemon
2011-06-28 16:00 ` bugzilla-daemon
2011-06-28 16:40 ` bugzilla-daemon
2019-11-19  8:20 ` 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-38657-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.