dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29842] Radeon runs very hot
Date: Mon, 19 Mar 2012 16:35:13 GMT	[thread overview]
Message-ID: <201203191635.q2JGZDEE023389@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-29842-2300@https.bugzilla.kernel.org/>

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





--- Comment #17 from Igor Rudchenko <igor@starrain.org>  2012-03-19 16:35:11 ---
To Matthew Garrett:

I agree about network cards, but current situation with video card worries me
much. Prior 3.0.20, 3.2.5 and 3.3 kernels, users of ThinkPads T60 can simply
add key "pcie_aspm=force" to kernel and get ASPM working for their radeon card.
But after your last patch to ASPM code we can't get ASPM working simply by keys
or sysfs. "pcie_aspm=force" does nothing, but the ability to change policy. But
changing policy also does nothing! I tried to change to powersave and then
watch into registers - I got the same 0x40 values. So now direct change
registers with setpci is our only choice to get ASPM working. And so it should
not be.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-03-19 16:35 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 19:24 [Bug 29842] New: Radeon runs very hot bugzilla-daemon
2011-02-25 14:54 ` [Bug 29842] " bugzilla-daemon
2011-02-25 17:11   ` Phillip Susi
2011-02-25 17:35     ` Matt Turner
2011-02-26  8:09     ` Michel Dänzer
2011-02-26 15:40       ` Phillip Susi
2011-02-26 17:35         ` Alex Deucher
2011-03-01  0:40 ` bugzilla-daemon
2011-03-01  3:19 ` bugzilla-daemon
2011-03-01  3:43 ` bugzilla-daemon
2011-03-01  3:49 ` bugzilla-daemon
2011-03-01 19:58 ` bugzilla-daemon
2011-03-01 21:06 ` bugzilla-daemon
2011-03-01 21:09 ` bugzilla-daemon
2011-04-12  1:22 ` bugzilla-daemon
2011-04-12  2:26 ` bugzilla-daemon
2011-04-12 16:35 ` bugzilla-daemon
2011-06-27 12:44 ` bugzilla-daemon
2011-06-27 19:12 ` bugzilla-daemon
2011-07-02 11:57 ` bugzilla-daemon
2012-02-22 16:56 ` bugzilla-daemon
2012-02-23  6:45   ` Pasi Kärkkäinen
2012-03-19 10:50 ` bugzilla-daemon
2012-03-19 14:01 ` bugzilla-daemon
2012-03-19 16:35 ` bugzilla-daemon [this message]
2012-05-12 15:13 ` bugzilla-daemon
2015-02-19 16:19 ` 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=201203191635.q2JGZDEE023389@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox