From: Guenter Roeck <linux@roeck-us.net>
To: James Cloos <cloos@jhcloos.com>
Cc: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
dri-devel@lists.freedesktop.org, lm-sensors@lm-sensors.org
Subject: Re: Kaveri [and Radeon] temps
Date: Wed, 5 Nov 2014 15:50:22 -0800 [thread overview]
Message-ID: <20141105235022.GA26085@roeck-us.net> (raw)
In-Reply-To: <m3ppd18bnn.fsf@carbon.jhcloos.org>
On Wed, Nov 05, 2014 at 06:34:20PM -0500, James Cloos wrote:
> >>>>> "GR" == Guenter Roeck <linux@roeck-us.net> writes:
>
> ...
> GR> AMD CPUs are known report wildly off temperatures especially at
> GR> low temperatures.
>
> Thanks. After some further digging, I wonder whether Aravind's recent
> patch might help? The apu does have both PCI_DEVICE_ID_AMD_16H_M30H_NB_F3
> and PCI_DEVICE_ID_AMD_16H_M30H_NB_F4 and lspci reports no driver for the
> F4 device.
>
Aravind would have to comment; my understanding is that the F4 device
reports the power, not the temperature. You could try to apply the patch
and see if it makes a difference. Worst case there will be no change ;-).
> GR> Does the temperature increase with load ?
>
> It seems to max out w/in a kelvin or two of the room's ambient temp.
>
Even under load ? Sounds weird. Question of course is if the chip really
reports a useful temperature in the first place; this is something I can
not answer, since I have neither a datasheet nor a system with that CPU.
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2014-11-05 23:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m31tph9wmt.fsf@carbon.jhcloos.org>
2014-11-05 23:21 ` Kaveri [and Radeon] temps Guenter Roeck
2014-11-05 23:34 ` James Cloos
2014-11-05 23:50 ` Guenter Roeck [this message]
2014-11-06 15:17 ` Aravind Gopalakrishnan
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=20141105235022.GA26085@roeck-us.net \
--to=linux@roeck-us.net \
--cc=aravind.gopalakrishnan@amd.com \
--cc=cloos@jhcloos.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=lm-sensors@lm-sensors.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