From: Jean Delvare <khali@linux-fr.org>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Sensors shows only 8 of 10 cores on 4-Socket Intel(R) Xeon(R) CPU E7- 4850 machine
Date: Tue, 14 Jan 2014 13:54:51 +0000 [thread overview]
Message-ID: <20140114145451.256bcc4c@endymion.delvare> (raw)
In-Reply-To: <CAGz0_-0VUOd_-SAncqUY99CBPLmRVuMV98aiedpqwd9jGqOv1Q@mail.gmail.com>
Hi Andreas,
On Tue, 14 Jan 2014 14:34:15 +0100, Andreas Hollmann wrote:
> 2014/1/14 Jean Delvare <khali@linux-fr.org>:
> > Please also provide the output of:
> > $ strace sensors "coretemp-isa-0000"
>
> (...)
> openat(AT_FDCWD, "/sys/class/hwmon/hwmon0/device", O_RDONLY|O_NONBLOCK|O_DIRECTORY|O_CLOEXEC) = 4
> brk(0x652000) = 0x652000
> getdents(4, /* 59 entries */, 32768) = 1944
> stat("/sys/class/hwmon/hwmon0/device/temp2_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp2_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp2_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp2_crit_alarm", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
I'm reordering the entries to make it easier to read... This is Core 0.
> stat("/sys/class/hwmon/hwmon0/device/temp3_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp3_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp3_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp3_crit_alarm", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
This is Core 1.
> stat("/sys/class/hwmon/hwmon0/device/temp4_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp4_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp4_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp4_crit_alarm", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
This is Core 2.
> stat("/sys/class/hwmon/hwmon0/device/temp10_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp10_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp10_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
This is Core 8, alarm flag is missing.
> stat("/sys/class/hwmon/hwmon0/device/temp11_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp11_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp11_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
This is Core 9, alarm flag is missing.
> stat("/sys/class/hwmon/hwmon0/device/temp18_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp18_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp18_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
This is Core 16, alarm flag is missing.
> stat("/sys/class/hwmon/hwmon0/device/temp19_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp19_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp19_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
This is Core 17, alarm flag is missing.
> stat("/sys/class/hwmon/hwmon0/device/temp20_input", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp20_max", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> stat("/sys/class/hwmon/hwmon0/device/temp20_crit", {st_mode=S_IFREG|0444, st_size@96, ...}) = 0
> getdents(4, /* 0 entries */, 32768) = 0
> close(4) = 0
This is Core 18, alarm flag is missing.
This matches the output of sensors, but raises two questions:
1* Why are the alarm flags missing for 5 inputs?
2* getdents says 59 entries, but the above are only 27. Even adding 2
for . and .. and 8 for the label files, we're only at 37. So there must
be more files to read than libsensors is actually reading - presumably
your two missing cores are there.
So please provide the output of:
$ ls -l /sys/devices/platform/coretemp.0
I suspect this constant in libsensors is causing the problem:
#define MAX_SENSORS_PER_TYPE 24
The library assumes linear numbering, so anything beyond temp23 would
be ignored, which I suspect is the problem here.
This however doesn't explain the missing alarm files. I'm curious if
the "ls" command above will show them.
I would also like to see the output of:
$ grep '^\(processor\|core id\)' /proc/cpuinfo
--
Jean Delvare
http://jdelvare.nerim.net/wishlist.html
_______________________________________________
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-01-14 13:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-14 13:01 [lm-sensors] Sensors shows only 8 of 10 cores on 4-Socket Intel(R) Xeon(R) CPU E7- 4850 machine Andreas Hollmann
2014-01-14 13:24 ` Jean Delvare
2014-01-14 13:26 ` Andreas Hollmann
2014-01-14 13:26 ` Jean Delvare
2014-01-14 13:54 ` Jean Delvare [this message]
2014-01-14 14:09 ` Andreas Hollmann
2014-01-14 14:26 ` Guenter Roeck
2014-01-14 14:44 ` Jean Delvare
2014-01-14 15:07 ` Andreas Hollmann
2014-01-14 15:16 ` Jean Delvare
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=20140114145451.256bcc4c@endymion.delvare \
--to=khali@linux-fr.org \
--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.