From: paul@astropaul.com (Paul Reilly)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Tyan S2877 CPU Temp Erratic
Date: Sat, 25 Nov 2006 13:21:33 +0000 [thread overview]
Message-ID: <1164460893.4568435d2695a@mail.third-rock.net> (raw)
In-Reply-To: <1163375222.4557b2764fc69@mail.third-rock.net>
Hi Rudolf,
> Theoretically there could be 4 temps for one physical CPU. Two for each core
> * 2 = 4. And because your CPU is dualcore, and your CPU supports only 1
> temperature/core so you see two of them ;) I hope I clarified that.
Yes, I see from the k8temp.c
static SENSOR_DEVICE_ATTR_2(temp1_input, S_IRUGO, show_temp, NULL, 0, 0);
static SENSOR_DEVICE_ATTR_2(temp2_input, S_IRUGO, show_temp, NULL, 0, 1);
static SENSOR_DEVICE_ATTR_2(temp3_input, S_IRUGO, show_temp, NULL, 1, 0);
static SENSOR_DEVICE_ATTR_2(temp4_input, S_IRUGO, show_temp, NULL, 1, 1);
So,
temp1 = CPU#0 Core#0 Temp #0
temp2 = CPU#0 Core#0 Temp #1
temp3 = CPU#0 Core#1 Temp #0
temp4 = CPU#0 Core#1 Temp #1
My Dual Core Opteron (265) only reports temp1, and temp3.
That is OK. One temperature per core.
What would it look like if I add a second physical processor in
the second socket? Would I get the same lmsensor names repeated?
> So all in all, this works fine. Lets check the i2c bus related problem. And
> wait for some logs from you ;)
Here are the logs.
It looks like a timeout problem....
syslog:Nov 25 08:31:58 discover kernel: i2c /dev entries driver
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-9191: ISA main adapter
registered
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-0: nForce2 SMBus adapter
at 0xa000
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-1: nForce2 SMBus adapter
at 0xa040
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-0: SMBus Timeout! (0x10)
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-1: SMBus Timeout! (0x10)
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-9191: Driver w83627hf
registered
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-0: SMBus Timeout! (0x10)
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-1: SMBus Timeout! (0x10)
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-9191: Driver w83781d-isa
registered
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-0: SMBus Timeout! (0x10)
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-1: SMBus Timeout! (0x10)
syslog:Nov 25 08:31:58 discover kernel: i2c_adapter i2c-1: SMBus Timeout! (0x10)
next prev parent reply other threads:[~2006-11-25 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-12 23:47 [lm-sensors] Tyan S2877 CPU Temp Erratic Paul Reilly
2006-11-24 13:07 ` Rudolf Marek
2006-11-25 10:02 ` Paul Reilly
2006-11-25 10:04 ` Rudolf Marek
2006-11-25 10:07 ` Rudolf Marek
2006-11-25 12:48 ` Rudolf Marek
2006-11-25 13:21 ` Paul Reilly [this message]
2006-11-25 21:10 ` Rudolf Marek
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=1164460893.4568435d2695a@mail.third-rock.net \
--to=paul@astropaul.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.