kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[PGNet Dev]

I'm running linux kernel 5.4.6-24.ge5f8301-default on an AMD Ryzen 3700X cpu.

I'm seeing very limited lm_sensors output.

I've posted my recent detail to an existing, but closed (?), lm_sensors issue,

	Can't display frequency and others of Ryzen7 3700X. #187
	https://github.com/lm-sensors/lm-sensors/issues/187#issuecomment-568630737

I note some recent work in kernel logs,

	https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4

particularly by Marcel Bocu.

b4 (re)opening any new tickets, etc, checking-in here first.

*IS* the kernel support for Zen2 Ryzen 3700X incomplete, as yet?

And, *should* sensors output for Zen arch be full/complete?

Or is there something lm_sensors-specific going on here, preventing the sensors output?

Thanks for any comments/hints!

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[Guenter Roeck]

On 12/23/19 6:46 PM, PGNet Dev wrote:
> I'm running linux kernel 5.4.6-24.ge5f8301-default on an AMD Ryzen 3700X cpu.
> 
> I'm seeing very limited lm_sensors output.
> 
> I've posted my recent detail to an existing, but closed (?), lm_sensors issue,
> 
> 	Can't display frequency and others of Ryzen7 3700X. #187
> 	https://github.com/lm-sensors/lm-sensors/issues/187#issuecomment-568630737
> 

The "sensors" command, or libsensors, or hardware monitoring in the Linux kernel
in general, does not support, did never support, and will never support displaying
CPU frequencies.

Displaying fan speeds, supply voltages, and system temperatures other than
the CPU temperature has nothing to do with the CPU installed in a system.
It depends on support for the Super IO chip used on the motherboard, which
may or may not be supported by the Linux kernel. If it is not supported,
it is quite likely that the motherboard vendor does not support Linux and
refuses to make the necessary information available for Linux kernel developers.

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.

> I note some recent work in kernel logs,
> 
> 	https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4
> 
> particularly by Marcel Bocu.
> 
> b4 (re)opening any new tickets, etc, checking-in here first.
> 
> *IS* the kernel support for Zen2 Ryzen 3700X incomplete, as yet?
> 
> And, *should* sensors output for Zen arch be full/complete?
> 

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).

Thanks,
Guenter

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[PGNet Dev]

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

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?

> 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)

		atk0110-acpi-0
		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)

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[Guenter Roeck]

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)
> 

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[PGNet Dev]

On 12/24/19 6:25 AM, Guenter Roeck wrote:
> 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.

this certainly looks like it might be the source of the problem,

...
[33002.934396] nct6775: Found NCT6793D or compatible chip at 0x2e:0x290
[33002.934401] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33002.934406] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33017.944153] nct6775: Found NCT6795D or compatible chip at 0x2e:0x290
[33017.944158] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33017.944164] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33033.152135] nct6775: Found NCT6793D or compatible chip at 0x2e:0x290
[33033.152140] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33033.152146] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33085.807200] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[33085.807205] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[33085.807209] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[33519.421923] usb 4-1.4.3: reset SuperSpeed Gen 1 USB device number 4 using xhci_hcd
[34160.099747] it87: Found IT8728F chip at 0xfff8, revision 15
[34160.099769] it87: Beeping is supported
[34160.099844] it87: Found IT8728F chip at 0xfff8, revision 15
[34160.099865] it87: Beeping is supported
[34212.426003] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[34212.426008] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[34212.426014] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[35066.143893] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
[35066.143900] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
[35066.143907] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
...


if it is, iiuc your earlier comments, sounds like a BIOS issue.

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[Guenter Roeck]

On 12/24/19 7:59 AM, PGNet Dev wrote:
> On 12/24/19 6:25 AM, Guenter Roeck wrote:
>> 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.
> 
> this certainly looks like it might be the source of the problem,
> 
> ...
> [33002.934396] nct6775: Found NCT6793D or compatible chip at 0x2e:0x290
> [33002.934401] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
> [33002.934406] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [33017.944153] nct6775: Found NCT6795D or compatible chip at 0x2e:0x290
> [33017.944158] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
> [33017.944164] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [33033.152135] nct6775: Found NCT6793D or compatible chip at 0x2e:0x290
> [33033.152140] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
> [33033.152146] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [33085.807200] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
> [33085.807205] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
> [33085.807209] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [33519.421923] usb 4-1.4.3: reset SuperSpeed Gen 1 USB device number 4 using xhci_hcd
> [34160.099747] it87: Found IT8728F chip at 0xfff8, revision 15
> [34160.099769] it87: Beeping is supported
> [34160.099844] it87: Found IT8728F chip at 0xfff8, revision 15
> [34160.099865] it87: Beeping is supported
> [34212.426003] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
> [34212.426008] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
> [34212.426014] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> [35066.143893] nct6775: Found NCT6798D or compatible chip at 0x2e:0x290
> [35066.143900] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
> [35066.143907] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> ...
> 
> 
> if it is, iiuc your earlier comments, sounds like a BIOS issue.
> 
The problem is - most likely - that the BIOS (or, rather, ACPI) accesses the
same memory range, and there is no synchronization. You could try to boot with
"acpi_enforce_resources=lax" command line option, but that would be on your
own risk, and some recent boards don't even boot if that command line option
is present.

You should not try to load the it87 driver on ASUS boards.

Did you try to load "asus_atk0110" ?

Guenter

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[PGNet Dev]

On 12/24/19 8:29 AM, Guenter Roeck wrote:
> The problem is - most likely - that the BIOS (or, rather, ACPI) accesses the
> same memory range, and there is no synchronization. You could try to boot with
> "acpi_enforce_resources=lax" command line option, but that would be on your
> own risk, and some recent boards don't even boot if that command line option
> is present.
> 
> You should not try to load the it87 driver on ASUS boards.
> 
> Did you try to load "asus_atk0110" ?

Had earlier come upon this,

	Nuvoton nct6798d not detected #197
	 https://github.com/lm-sensors/lm-sensors/issues/197

re: the add'n of

	acpi_enforce_resources=lax

and was just adding that to my grub kernel config.

just in case also added,

	cat /etc/modules-load.d/sensors.conf
		msr
		k10temp
		nct6775
+		asus_atk0110

now on reboot, I no longer see those^^ earlier conflict warnings; I _do_ see now,

	...
	[    0.233419] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
	[    2.484532] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
	[    2.489504] ACPI: This conflict may cause random problems and system instability
	[    2.492038] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
	[    2.513650] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
	[    2.540469] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9421164 (first instance was on PNP0C14:01)
	[    2.543119] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9421164 (first instance was on PNP0C14:01)
	[    2.559449] ACPI: bus type USB registered
	[   13.553990] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
	[   14.609097] acpi_cpufreq: overriding BIOS provided _PSD data
	[   14.610845] ACPI: Power Button [PWRB]
	[   14.611600] ACPI: Power Button [PWRF]
	[   14.633620] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
	[   15.451860] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
	...

Seems `acpi_enforce_resources` and `asus_atk0110` don't play nicely?

AND, `sensors` certainly appears a bit more informative/useful!

	sensors
		k10temp-pci-00c3
		Adapter: PCI adapter
		Tdie:         +55.2°C  (high = +70.0°C)
		Tctl:         +55.2°C

		nct6798-isa-0290
		Adapter: ISA adapter
		in0:                   504.00 mV (min =  +0.00 V, max =  +1.74 V)
		in1:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
		in2:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
		in3:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
		in4:                   1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
		in5:                   816.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
		in6:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
		in7:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
		in8:                     3.25 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
		in9:                   896.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
		in10:                  408.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
		in11:                  544.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
		in12:                    1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
		in13:                  1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
		in14:                  1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
		fan1:                  1218 RPM  (min =    0 RPM)
		fan2:                  1917 RPM  (min =    0 RPM)
		fan3:                   905 RPM  (min =    0 RPM)
		fan4:                  1190 RPM  (min =    0 RPM)
		fan5:                     0 RPM  (min =    0 RPM)
		fan6:                     0 RPM  (min =    0 RPM)
		fan7:                     0 RPM  (min =    0 RPM)
		SYSTIN:                 +36.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
		CPUTIN:                 +32.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
		AUXTIN0:                +25.0°C    sensor = thermistor
		AUXTIN1:                +36.0°C    sensor = thermistor
		AUXTIN2:                +21.0°C    sensor = thermistor
		AUXTIN3:                +26.0°C    sensor = thermistor
		PCH_CHIP_CPU_MAX_TEMP:   +0.0°C
		PCH_CHIP_TEMP:           +0.0°C
		PCH_CPU_TEMP:            +0.0°C
		PCH_MCH_TEMP:            +0.0°C
		intrusion0:            ALARM
		intrusion1:            ALARM
		beep_enable:           disabled

, with ALL of those now available to desktop utils such as KDE's (slightly broken) ThermalMonitor plasma widget ... (need to figure out which of those are the CPU, vs Mobo, fan/temp sensors)

I don't know what, if any, issues are introducted by the use of `acpi_enforce_resources=lax` ...
This _is_ just a workaround, yes?  I.e., BIOS still should have a fix?

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[PGNet Dev]

On 12/24/19 9:14 AM, PGNet Dev wrote:
> , with ALL of those now available to desktop utils such as KDE's (slightly broken) ThermalMonitor plasma widget ... (need to figure out which of those are the CPU, vs Mobo, fan/temp sensors)
> 
> I don't know what, if any, issues are introducted by the use of `acpi_enforce_resources=lax` ...
> This _is_ just a workaround, yes?  I.e., BIOS still should have a fix?

and, fwiw, `pwmconfig` now executes correctly, generating /etc/fancontrol data/config.

given BIOS's foibles, is it generally recommended to USE thermal/fan control via `fancontrol` on linux/OS?  or leave it to BIOS?

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[Guenter Roeck]

On 12/24/19 9:14 AM, PGNet Dev wrote:
> On 12/24/19 8:29 AM, Guenter Roeck wrote:
>> The problem is - most likely - that the BIOS (or, rather, ACPI) accesses the
>> same memory range, and there is no synchronization. You could try to boot with
>> "acpi_enforce_resources=lax" command line option, but that would be on your
>> own risk, and some recent boards don't even boot if that command line option
>> is present.
>>
>> You should not try to load the it87 driver on ASUS boards.
>>
>> Did you try to load "asus_atk0110" ?
> 
> Had earlier come upon this,
> 
> 	Nuvoton nct6798d not detected #197
> 	 https://github.com/lm-sensors/lm-sensors/issues/197
> 
> re: the add'n of
> 
> 	acpi_enforce_resources=lax
> 
> and was just adding that to my grub kernel config.
> 
> just in case also added,
> 
> 	cat /etc/modules-load.d/sensors.conf
> 		msr
> 		k10temp
> 		nct6775
> +		asus_atk0110
> 
> now on reboot, I no longer see those^^ earlier conflict warnings; I _do_ see now,
> 
> 	...
> 	[    0.233419] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
> 	[    2.484532] ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20190816/utaddress-204)
> 	[    2.489504] ACPI: This conflict may cause random problems and system instability
> 	[    2.492038] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
> 	[    2.513650] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
> 	[    2.540469] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9421164 (first instance was on PNP0C14:01)
> 	[    2.543119] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9421164 (first instance was on PNP0C14:01)
> 	[    2.559449] ACPI: bus type USB registered
> 	[   13.553990] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
> 	[   14.609097] acpi_cpufreq: overriding BIOS provided _PSD data
> 	[   14.610845] ACPI: Power Button [PWRB]
> 	[   14.611600] ACPI: Power Button [PWRF]
> 	[   14.633620] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
> 	[   15.451860] asus_atk0110: Resources not safely usable due to acpi_enforce_resources kernel parameter
> 	...
> 
> Seems `acpi_enforce_resources` and `asus_atk0110` don't play nicely?
> 
> AND, `sensors` certainly appears a bit more informative/useful!
> 
> 	sensors
> 		k10temp-pci-00c3
> 		Adapter: PCI adapter
> 		Tdie:         +55.2°C  (high = +70.0°C)
> 		Tctl:         +55.2°C
> 
> 		nct6798-isa-0290
> 		Adapter: ISA adapter
> 		in0:                   504.00 mV (min =  +0.00 V, max =  +1.74 V)
> 		in1:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in2:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in3:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in4:                   1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in5:                   816.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in6:                     1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in7:                     3.34 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in8:                     3.25 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in9:                   896.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in10:                  408.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in11:                  544.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in12:                    1.02 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in13:                  1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		in14:                  1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
> 		fan1:                  1218 RPM  (min =    0 RPM)
> 		fan2:                  1917 RPM  (min =    0 RPM)
> 		fan3:                   905 RPM  (min =    0 RPM)
> 		fan4:                  1190 RPM  (min =    0 RPM)
> 		fan5:                     0 RPM  (min =    0 RPM)
> 		fan6:                     0 RPM  (min =    0 RPM)
> 		fan7:                     0 RPM  (min =    0 RPM)
> 		SYSTIN:                 +36.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> 		CPUTIN:                 +32.0°C  (high = +80.0°C, hyst = +75.0°C)  sensor = thermistor
> 		AUXTIN0:                +25.0°C    sensor = thermistor
> 		AUXTIN1:                +36.0°C    sensor = thermistor
> 		AUXTIN2:                +21.0°C    sensor = thermistor
> 		AUXTIN3:                +26.0°C    sensor = thermistor
> 		PCH_CHIP_CPU_MAX_TEMP:   +0.0°C
> 		PCH_CHIP_TEMP:           +0.0°C
> 		PCH_CPU_TEMP:            +0.0°C
> 		PCH_MCH_TEMP:            +0.0°C
> 		intrusion0:            ALARM
> 		intrusion1:            ALARM
> 		beep_enable:           disabled
> 
> , with ALL of those now available to desktop utils such as KDE's (slightly broken) ThermalMonitor plasma widget ... (need to figure out which of those are the CPU, vs Mobo, fan/temp sensors)
> 
> I don't know what, if any, issues are introducted by the use of `acpi_enforce_resources=lax` ...
> This _is_ just a workaround, yes?  I.e., BIOS still should have a fix?
> 

The BIOS does exactly what the board vendor wants it to do: Reject direct access
to the Super-IO chip. The board vendor wants you to access the chip through ACPI,
ie with asus_atk0110. Unfortunately, it looks like the board vendor also
changed the ACPI data sufficiently enough to make that driver not work for
your board (assuming you tried loading it without acpi_enforce_resources=lax).

There is nothing we can do about that unless the board vendor provides the information
necessary to interpret the DSDT, or someone spends the time to reverse engineer it.

Guenter

Re: kernel 5.4.6 + Ryzen 3700X: "Can't display frequency and others of Ryzen7 3700X"

[PGNet Dev]

On 12/24/19 11:57 AM, Guenter Roeck wrote:
> The BIOS does exactly what the board vendor wants it to do: Reject direct access
> to the Super-IO chip. The board vendor wants you to access the chip through ACPI,
> ie with asus_atk0110. Unfortunately, it looks like the board vendor also
> changed the ACPI data sufficiently enough to make that driver not work for
> your board (assuming you tried loading it without acpi_enforce_resources=lax).


WITH module

	lsmod | grep asus_atk
		asus_atk0110           24576  0

but WITHOUT cmd line

	... acpi_enforce_resources=lax ...


`sensors` returns ONLY the limited

	sensors
		k10temp-pci-00c3
		Adapter: PCI adapter
		Tdie:         +34.4°C  (high = +70.0°C)
		Tctl:         +34.4°C

OTOH, switching, WITHOUT module

	lsmod | grep asus_atk
		(empty)

and WITH cmd line

	... acpi_enforce_resources=lax ...


`sensors` returns the full(er) output, as posted.

note again, in this case, even ATTEMPTING to load asus_atk0110 FAILs due to the apparent conflict with the =lax spec'n.

> There is nothing we can do about that unless the board vendor provides the information
> necessary to interpret the DSDT, or someone spends the time to reverse engineer it.

got it.  i'll poke at ASUS support.

thx 4 the education re: this^^ !