All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor
Date: Wed, 14 Aug 2013 05:30:26 +0000	[thread overview]
Message-ID: <520B15F2.7090100@roeck-us.net> (raw)
In-Reply-To: <CAFSPGzQyxOOhjawcQj=wH+k1b=OC1gGf6CKWoU89TWVTykNcOQ@mail.gmail.com>

On 08/13/2013 10:17 PM, Kapil Dev wrote:
>
> On Aug 14, 2013, at 12:56 AM, Guenter Roeck <linux@roeck-us.net> wrote:
>
>> On 08/13/2013 08:09 PM, Dev, Kapil wrote:
>>>
>>>
>>> On Tue, Aug 13, 2013 at 11:02 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net>> wrote:
>>>
>>>     On 08/13/2013 07:41 PM, Dev, Kapil wrote:
>>>
>>>         Thanks again Guenter!
>>>
>>>
>>>
>>>
>>>         On Tue, Aug 13, 2013 at 5:51 PM, Guenter Roeck <linux@roeck-us.net <mailto:linux@roeck-us.net> <mailto:linux@roeck-us.net <mailto:linux@roeck-us.net>>> wrote:
>>>
>>>              On Tue, Aug 13, 2013 at 05:11:31PM -0400, Dev, Kapil wrote:
>>>               > Thanks for the response Guenter!
>>>               >
>>>               > I put the system on load and I noticed their value hardly changes. To my
>>>               > surprise, I ran a benchmark for 3 minutes and none of temp*  values changed
>>>               > during execution. The highest reported temperature is always 48C.
>>>               >
>>>               > I was expecting that the internal temperature would have "sensor = thermal
>>>               > diode" or "sensor = core" as a keyword. I thought "sensor=thermistor" means
>>>               > the corresponding sensor is on the motherboard and not the internal
>>>               > die-sensor.
>>>               >
>>>              Sure, but who knows if they put a sensor below the CPU for some reason ...
>>>
>>>              I am not familiar with the A10 CPUs. Are those similar to K10 ?
>>>              If so, maybe the k10temp driver works or could be extended to support it.
>>>              Can you give it a try ?
>>>
>>>              If it does not work out of the box, can you send me the output of "lspci -nn" ?
>>>
>>>
>>>         Kapil: I believe K10 corresponds to A8 seried, and A10 has Bulldozer architecture (http://www.cpu-world.com/__CPUs/Bulldozer/TYPE-A10-__Series.html <http://www.cpu-world.com/CPUs/Bulldozer/TYPE-A10-Series.html>). I am not sure how different they are though. I tried K10, but it did not work out of the box. I am looking into k10temp.c driver now. Also,I am attaching the output of "lspci -nn" command herewith; you might have to open it using wordpad for proper formatting..
>>>
>>>
>>>     Your lspci output includes
>>>
>>>     00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Device [1022:1403]
>>>
>>>     which is supported by the latest k10temp driver. Support was added early last year.
>>>     What is your kernel version, and can you switch to a more recent version ?
>>>
>>>
>>> Kapil: I have 2.6.39-020639-generic kernel. Is it too old kernel for k10temp driver to work? Which stable kernel should I upgrade to?
>>>
>>
>> You need 3.4 or later.
>
> Kapil: I was trying to avoid updating the kernel because my current kernel is setup for running different type of benchmarks etc. Seems like I can't avoid updating the kernel; I will do it..
>
Alternative would be to back-port the k10temp driver from a later kernel. Then you can keep running the old one.

> Just for my understanding: Currently, when I run "sensors" command, I am getting three values (apparently wrong), temp1-3. So, what do you think is happening that is causing these values wrong? And, how is it going to be fixed by updating the  kernel? Although we don't know yet, but, I am hoping that by updating the kernel and loading the k10temp kernel, I would be able to see readings from thermal-diode (core-temperature) along with the current readings from thermal-resistors.
>
Not wrong; those are probably different chassis and/or board temperatures. Does the BIOS report
any matching temperatures ?

Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2013-08-14  5:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-13 19:05 [lm-sensors] reading on-die temperature sensor of AMD A10 5700 processor Dev, Kapil
2013-08-13 20:27 ` Guenter Roeck
2013-08-13 21:11 ` Dev, Kapil
2013-08-13 21:51 ` Guenter Roeck
2013-08-14  2:41 ` Dev, Kapil
2013-08-14  3:02 ` Guenter Roeck
2013-08-14  3:09 ` Dev, Kapil
2013-08-14  4:56 ` Guenter Roeck
2013-08-14  5:17 ` Kapil Dev
2013-08-14  5:30 ` Guenter Roeck [this message]
2013-08-14  5:32 ` Phil Pokorny
2013-08-14 17:20 ` Dev, Kapil
2013-08-14 18:29 ` Guenter Roeck
2013-08-14 18:33 ` Guenter Roeck
2013-08-14 19:06 ` Dev, Kapil
2013-08-14 20:03 ` Guenter Roeck
2013-08-14 20:45 ` Dev, Kapil
2013-08-14 22:39 ` Guenter Roeck
2013-08-15  4:16 ` Dev, Kapil
2013-08-15  4:29 ` Guenter Roeck
2013-08-15  4:32 ` Dev, Kapil
2013-08-15  5:30 ` Guenter Roeck
2013-08-15  7:55 ` Clemens Ladisch
2013-08-16  3:48 ` Dev, Kapil
2013-08-16  7:03 ` Clemens Ladisch
2013-08-16  8:57 ` Kapil Dev
2013-08-16  9:27 ` Clemens Ladisch

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=520B15F2.7090100@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@vger.kernel.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.