From: Phil Pokorny <ppokorny@penguincomputing.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] k10temp
Date: Mon, 13 May 2013 15:36:43 +0000 [thread overview]
Message-ID: <9203240578498506740@unknownmsgid> (raw)
In-Reply-To: <20130512194229.tceeg6ht8xokc884@webmail.dommel.be>
No. It's not always a crappy sensor.
The temperature reported is not absolute temperature. It's a control
temperature normalized to 70 degrees meaning max temp.
And the accuracy is such that its most accurate near "70" degrees and
may be less accurate further away. But given the intended use of this
sensor (to monitor and keep the "temperature" below "70" degrees) that
in-accuracy away from that target is not an issue.
It should be used to verify your cooling solution is working as
intended. It is much more accurate for this purpose than the
motherboard sensors which may not be on the CPU die and are not
calibrated by the CPU manufacturer to help you. If you want to
minimize fan speeds, you can dial them down as long as the k10
"temperature" is below 70
The datasheets are very clear on this.
Phil P.
--
Philip Pokorny, RHCE
Chief Technical Officer
PENGUIN COMPUTING, Inc
www.penguincomputing.com
On May 12, 2013, at 1:11 PM, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Dirk,
>
> On Sun, 12 May 2013 19:42:29 +0200, dirk.p@dommel.be wrote:
>> This is not dramatic, but I think the temperature returned by k10temp can not be
>> correct. The temperature is lower than the room temperature of 14°C and lower
>> than the more realistic values reported by it8728.
>> (...)
>> k10temp-pci-00c3
>> Adapter: PCI adapter
>> temp1: +8.0°C (high = +70.0°C)
>> (crit = +90.0°C, hyst = +87.0°C)
>
> We have received countless reports of crappy temperature reports from
> k10temp. Some CPU models we even had to blacklist because they were
> hopeless. This is believed to be a hardware issue that can't be fixed.
> Just use the it8728 values if you trust them more (I would.)
>
>> (...)
>> Every time I load module i2c-piix4 I get something like
>>
>> [ 2952.162696] ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO
>> conflicts with Region \SOR1 1 (20120913/utaddress-251)
>> [ 2952.162708] ACPI: If an ACPI driver is available for this device, you should
>> use it instead of the native driver
>> in dmesg.
>>
>> The wrong module or something not implemented by the OEM?
>
> ACPI stealing I/O ports for its own use; unrelated with k10temp.
>
> --
> Jean Delvare
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2013-05-13 15:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 17:42 [lm-sensors] k10temp dirk.p
2013-05-12 20:08 ` Jean Delvare
2013-05-13 15:36 ` Phil Pokorny [this message]
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=9203240578498506740@unknownmsgid \
--to=ppokorny@penguincomputing.com \
--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.