From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 29842] Radeon runs very hot
Date: Mon, 19 Mar 2012 16:35:13 GMT
Message-ID: <201203191635.q2JGZDEE023389@bugzilla.kernel.org>
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path:
Received: from bugzilla.kernel.org (bugzilla.kernel.org [198.145.19.204])
by gabe.freedesktop.org (Postfix) with ESMTP id 5E1A19E7D2
for ;
Mon, 19 Mar 2012 09:35:13 -0700 (PDT)
Received: from bugzilla.kernel.org (localhost [127.0.0.1])
by bugzilla.kernel.org (8.14.5/8.14.5) with ESMTP id q2JGZDna023390
for ; Mon, 19 Mar 2012 16:35:13 GMT
In-Reply-To:
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org
To: dri-devel@lists.freedesktop.org
List-Id: dri-devel@lists.freedesktop.org
https://bugzilla.kernel.org/show_bug.cgi?id=29842
--- Comment #17 from Igor Rudchenko 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.