linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: pgnet.dev@gmail.com, linux-hwmon@vger.kernel.org
Cc: marcel.p.bocu@gmail.com
Subject: Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"
Date: Tue, 24 Dec 2019 06:25:44 -0800	[thread overview]
Message-ID: <121bee85-6369-4b32-2504-c1d104ea2bd6@roeck-us.net> (raw)
In-Reply-To: <2c858787-1e5e-77e4-30ef-f17036b205c2@gmail.com>

On 12/23/19 9:50 PM, PGNet Dev wrote:
> hi,
> 
> On 12/23/19 9:28 PM, Guenter Roeck wrote:
>> In the specific issue referenced above, it appears that a Nuvoton NCT6796D
>> was detected but not instantiated. Most likely the problem is that the IO address
>> range necessary to access the chip is reserved by the BIOS. Looking into the
>> kernel log would reveal that information. Again, that has nothing to do with
>> support for the CPU installed on the board, but with the board vendor and,
>> to a substantial degree, the lack of support for Linux by that board vendor.
> 
> not sure if this is of note,
> 
>   superiotool --dump
>    superiotool r
>    No Super I/O found
> 

superiotool only reports about chips it knows about. You might want to try
sensors-detect; it will at least tell you about unknown chips.

> I've contacted Asus tech re: BIOS 'gotchas' that might be interfering; I'll pass on your comments.  So far, on other issues, they've been very cooperative/helpful; we'll see how this goes.
> 
> As for the kernel log, anything specific to look for, share here?  Or just grab & post the whole thing somewhere?
> 
You'll probably see a note about an ACPI resource conflict. If the board
with NCT6796D wasn't yours, that may not be the case.

>> If you think something is missing that should be displayed by k10temp,
>> if you have documentation from AMD describing the necessary registers to
>> obtain this information, and if you have permission from AMD to publish
>> it, please feel free to submit a patch adding it to the k10temp driver.
>> Please make sure that the additional information follows the hardware
>> monitoring ABI (specifically, CPU frequencies are not part of that ABI).
> 
> Not entirely sure on the 'should' of it ... yet.
> 
> I _can_ say that, currently, for the 'new' setup, the limited info with 'k10temp' is
> 
> (1) ASUSTeK PRIME X570-PRO mobo + Ryzen7 3700X
> 
> 	sensors
> 		k10temp-pci-00c3
> 		Adapter: PCI adapter
> 		Tdie:         +59.9°C  (high = +70.0°C)
> 		Tctl:         +59.9°C
> 
> 
> and for an older board/cpu, also with 'k10temp', it's
> 
> (2) Asus M3A78-CM with a non-Ryzen, AMD Phenom II
> 
> 	sensors
> 		k10temp-pci-00c3
> 		Adapter: PCI adapter
> 		temp1:        +42.9°C  (high = +70.0°C)
> 		                       (crit = +99.5°C, hyst = +97.5°C)
> 

The register addresses for temperature limit information (if available) have
not been published by AMD for Ryzen CPUs. The same is true for other chip
specific information (voltages and power); my understanding is that AMD makes
that information only available under NDA, which is not suitable for a Linux
driver. Please feel free to contact AMD and convince them to publish the
necessary information.

> 		atk0110-acpi-0

This is very much _not_ k10temp. As the name says, it is the atk0110 ACPI driver
for ASUS boards. Support is very much board specific, and typically depends on
someone disassembling and analyzing the DSDT of a given board.

> 		Adapter: ACPI interface
> 		Vcore Voltage:       1.02 V  (min =  +0.85 V, max =  +1.60 V)
> 		 +3.3 Voltage:       3.23 V  (min =  +2.97 V, max =  +3.63 V)
> 		 +5 Voltage:         4.86 V  (min =  +4.50 V, max =  +5.50 V)
> 		 +12 Voltage:       12.04 V  (min = +10.20 V, max = +13.80 V)
> 		CPU FAN Speed:     2789 RPM  (min =  600 RPM, max = 7200 RPM)
> 		CHASSIS FAN Speed:    0 RPM  (min =  600 RPM, max = 7200 RPM)
> 		POWER FAN Speed:      0 RPM  (min =  600 RPM, max = 7200 RPM)
> 		CPU Temperature:    +44.0°C  (high = +60.0°C, crit = +95.0°C)
> 		MB Temperature:     +34.0°C  (high = +45.0°C, crit = +95.0°C)
> 


  reply	other threads:[~2019-12-24 14:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-24  2:46 kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X" PGNet Dev
2019-12-24  5:28 ` Guenter Roeck
2019-12-24  5:50   ` PGNet Dev
2019-12-24 14:25     ` Guenter Roeck [this message]
2019-12-24 15:59       ` PGNet Dev
2019-12-24 16:29         ` Guenter Roeck
2019-12-24 17:14           ` PGNet Dev
2019-12-24 17:38             ` PGNet Dev
2019-12-24 19:57             ` Guenter Roeck
2019-12-24 20:34               ` PGNet Dev

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=121bee85-6369-4b32-2504-c1d104ea2bd6@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=marcel.p.bocu@gmail.com \
    --cc=pgnet.dev@gmail.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).