Linux-Hwmon Archive on lore.kernel.org
 help / color / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Jonathan McDowell <noodles@earth.li>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ken Moffat <zarniwhoop73@googlemail.com>
Subject: Re: [PATCH v2 0/5] hwmon: k10temp driver improvements
Date: Sun, 19 Jan 2020 07:46:11 -0800
Message-ID: <f9bb13a7-60ba-37f1-9e22-3237e35cf4e5@roeck-us.net> (raw)
In-Reply-To: <20200119101855.GA15446@earth.li>

On 1/19/20 2:18 AM, Jonathan McDowell wrote:
> 
> In article <20200118172615.26329-1-linux@roeck-us.net> (earth.lists.linux-kernel) you wrote:
>> This patch series implements various improvements for the k10temp driver.
> ...
>> The voltage and current information is limited to Ryzen CPUs. Voltage
>> and current reporting on Threadripper and EPYC CPUs is different, and the
>> reported information is either incomplete or wrong. Exclude it for the time
>> being; it can always be added if/when more information becomes available.
> 
>> Tested with the following Ryzen CPUs:
> 
> Tested-By: Jonathan McDowell <noodles@earth.li>
> 
Thanks!

> Tested on a Ryzen 7 2700 (patched on top of 5.4.13):
> 
> | k10temp-pci-00c3
> | Adapter: PCI adapter
> | Vcore:        +0.80 V
> | Vsoc:         +0.81 V
> | Tdie:         +37.0°C
> | Tctl:         +37.0°C
> | Icore:        +8.31 A
> | Isoc:         +6.86 A
> 
> Like the 1300X case I see a discrepancy compared to what the nct6779
> driver says Vcore is:
> 
> | nct6779-isa-0290
> | Adapter: ISA adapter
> | Vcore:                  +0.33 V  (min =  +0.00 V, max =  +1.74 V)

I see that on all of my boards as well (3900X, different boards and board vendors),
with temperatures reported by the Super-IO chip sometimes as low as 0.18V (!).
Yet, there is a clear correlation of that voltage with CPU load.
I suspect the measurement by the Super-IO chip is a different voltage.

I don't think there is anything we can do about that without access to more
information.

> | in1:                    +0.32 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | AVCC:                   +3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | +3.3V:                  +3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in4:                    +1.88 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in5:                    +0.82 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in6:                    +0.30 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | 3VSB:                   +3.42 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | Vbat:                   +3.25 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in9:                    +0.00 V  (min =  +0.00 V, max =  +0.00 V)
> | in10:                   +0.22 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in11:                   +1.06 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in12:                   +1.70 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in13:                   +1.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | in14:                   +1.79 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> | fan1:                     0 RPM  (min =    0 RPM)
> | fan2:                  1708 RPM  (min =    0 RPM)
> | fan3:                     0 RPM  (min =    0 RPM)
> | fan4:                     0 RPM  (min =    0 RPM)
> | fan5:                     0 RPM  (min =    0 RPM)
> | SYSTIN:                 +33.0°C  (high =  +0.0°C, hyst =  +0.0°C)  ALARM
> | sensor = thermistor
> | CPUTIN:                 -62.5°C  (high = +80.0°C, hyst = +75.0°C)
> | sensor = thermistor
> | AUXTIN0:                +79.0°C    sensor = thermistor
> | AUXTIN1:                +96.0°C    sensor = thermistor
> | AUXTIN2:                +23.0°C    sensor = thermistor
> | AUXTIN3:                -22.0°C    sensor = thermistor
> | SMBUSMASTER 0:          +39.0°C
> | PCH_CHIP_CPU_MAX_TEMP:   +0.0°C
> | PCH_CHIP_TEMP:           +0.0°C
> | PCH_CPU_TEMP:            +0.0°C
> | intrusion0:            ALARM
> | intrusion1:            ALARM
> | beep_enable:           disabled
> 
> I suspect the nct6779 is not reporting correctly (or needs some
> configuration) here, as I see that's what Ken is using with his 1300X as
> well.
> 
Initially I thought the voltage reported by the Super-IO chip would help
us understand what is going on, but that is not really the case.

The problem with Ken's board is that idle current and voltage are very high.
The idle voltage claims to be higher than the voltage under load, which
doesn't really make sense. This is only reflected in the voltage and current
reported by the CPU, but not by the voltage reported by the Super-IO chip.

Thanks,
Guenter

  reply index

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 17:26 Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 1/5] hwmon: (k10temp) Use bitops Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 2/5] hmon: (k10temp) Convert to use devm_hwmon_device_register_with_info Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 3/5] hwmon: (k10temp) Report temperatures per CPU die Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 4/5] hwmon: (k10temp) Show core and SoC current and voltages on Ryzen CPUs Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 5/5] hwmon: (k10temp) Don't show temperature limits on Ryzen (Zen) CPUs Guenter Roeck
2020-01-19  0:33 ` [PATCH v2 0/5] hwmon: k10temp driver improvements Ken Moffat
2020-01-19  0:48   ` Guenter Roeck
2020-01-19  1:08     ` Ken Moffat
2020-01-19  3:13     ` Brad Campbell
2020-01-19 10:18 ` Jonathan McDowell
2020-01-19 15:46   ` Guenter Roeck [this message]
2020-01-19 19:38     ` Jonathan McDowell
2020-01-19 13:38 ` Holger Kiehl
2020-01-19 15:49   ` Guenter Roeck

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=f9bb13a7-60ba-37f1-9e22-3237e35cf4e5@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=noodles@earth.li \
    --cc=zarniwhoop73@googlemail.com \
    /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

Linux-Hwmon Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-hwmon/0 linux-hwmon/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-hwmon linux-hwmon/ https://lore.kernel.org/linux-hwmon \
		linux-hwmon@vger.kernel.org
	public-inbox-index linux-hwmon

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-hwmon


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git