From: Clemens Ladisch <clemens@ladisch.de>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] k10temp is detected but not shown
Date: Tue, 26 Oct 2010 13:53:29 +0000 [thread overview]
Message-ID: <4CC6DD59.30903@ladisch.de> (raw)
In-Reply-To: <578838.74607.qm@web111714.mail.gq1.yahoo.com>
Jean Delvare wrote:
> > > Doh. You are aware that Core i7 CPUs are made by Intel and Family 10h
> > > (aka K10) CPUs are made by AMD, aren't you? They are different CPU
> > > models, they don't have to be designed the same way.
> >
> > I know that :)
> > I thought maybe that is a standard and each cpu temperature must be show
> > separetly.
>
> There is no such standard.
And on the newest CPUs, Intel has switched to one temperature sensor per
package.
> On Tue, 26 Oct 2010 06:06:53 -0700 (PDT), Mahmood Naderan wrote:
> > One more question, Is it possible to find out which two modules are tied to one
> > processor?
>
> Modules?
>
> > Currently there are:
> > k10temp-pci-00c3
> > temp1: +27.0°C (high = +70.0°C, crit = +70.0°C)
> > k10temp-pci-00cb
> > temp1: +27.0°C (high = +70.0°C)
> > k10temp-pci-00d3
> > temp1: +26.0°C (high = +70.0°C)
> > k10temp-pci-00db
> > temp1: +26.0°C (high = +70.0°C, crit = +70.0°C)
> >
> > Is it true that [00c3 and 00cb] are for one physical cpu and [00d3 and 00db] are
> > for the other cpu?
I conclude from this question that you have two CPUs, and that each CPU
has two temperature sensors.
The temperature sensor is part of the PCI device that associated with
the CPU's internal northbridge. IIRC the six-core CPUs have two
northbridges, for whatever technical reason, so they present two
temparature sensors to the OS.
It looks as if the two sensors in each CPU have the same value. Is this
always the case?
(I don't know where the c3/cb/d3/db names come from.)
> All entries in cpuinfo look the same, so I can't explain why some have
> the critical limit and some don't.
The limit is set by the BIOS. I'd guess the BIOS knows that two sensors
are actually the same, an so doesn't bother to set the limit on the
superfluous ones.
I'll look into the datasheet to see if this situation (two northbridges
per CPU) is documented and can be detected so that the driver can ignore
these superfluous sensors.
Regards,
Clemens
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2010-10-26 13:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 8:14 [lm-sensors] k10temp is detected but not shown Mahmood Naderan
2010-10-25 14:45 ` Mahmood Naderan
2010-10-25 14:53 ` Jean Delvare
2010-10-25 15:00 ` Mahmood Naderan
2010-10-25 15:07 ` Jean Delvare
2010-10-25 15:30 ` Mahmood Naderan
2010-10-26 10:38 ` Mahmood Naderan
2010-10-26 10:59 ` Jean Delvare
2010-10-26 11:09 ` Mahmood Naderan
2010-10-26 11:21 ` Jean Delvare
2010-10-26 11:57 ` Mahmood Naderan
2010-10-26 12:38 ` Jean Delvare
2010-10-26 13:06 ` Mahmood Naderan
2010-10-26 13:21 ` Jean Delvare
2010-10-26 13:25 ` Mahmood Naderan
2010-10-26 13:53 ` Clemens Ladisch [this message]
2010-10-26 14:00 ` Mahmood Naderan
2010-10-26 14:15 ` Jean Delvare
2010-10-26 14:52 ` Clemens Ladisch
2010-10-26 14:53 ` Jean Delvare
2010-10-26 15:02 ` Guenter Roeck
2010-10-26 15:04 ` Philip Pokorny
2010-10-26 15:05 ` Clemens Ladisch
2010-10-26 15:33 ` Mahmood Naderan
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=4CC6DD59.30903@ladisch.de \
--to=clemens@ladisch.de \
--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.