Bug ID 1187874
Summary Kernel hwmon modules nct6775 no longer fully recognioses chip
Classification openSUSE
Product openSUSE Distribution
Version Leap 15.3
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Kernel
Assignee kernel-bugs@opensuse.org
Reporter opensuse@1.opensuse.bgcomp.co.uk
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

With opensuse 15.2, the nct6775 chip was recognise and the sensor command would
print details of its sensors.

This no longer happens with 15.3.

Running sensors-detect, the chip is not recognised, but is when the the module
is loaded, although it's sensors are still not listed.

The output 15.2 when the module is loaded is:
2021-03-01T19:22:02.900605+00:00 ns2 kernel: [    7.237799] nct6775: Enabling
hardware monitor logical device mappings.
2021-03-01T19:22:02.900605+00:00 ns2 kernel: [    7.237809] nct6775: Found
NCT6791D or compatible chip at 0x2e:0x290
2021-03-01T19:22:02.900605+00:00 ns2 kernel: [    7.237814] ACPI Warning:
SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion
0x0000000000000290-0x0000000000000299 (\_GPE.HWM) (20190703/utaddress-213)
2021-03-01T19:22:02.900605+00:00 ns2 kernel: [    7.237818] ACPI: This conflict
may cause random problems and system instability
2021-03-01T19:22:02.900605+00:00 ns2 kernel: [    7.237819] ACPI: If an ACPI
driver is available for this device, you should use it instead of the native
driver

while the output from 15.3 is:
2021-06-02T11:53:24.172296+01:00 ns2 kernel: nct6775: Enabling hardware monitor
logical device mappings.
2021-06-02T11:53:24.172369+01:00 ns2 kernel: nct6775: Found NCT6791D or
compatible chip at 0x2e:0x290
2021-06-02T11:53:24.172408+01:00 ns2 kernel: ACPI Warning: SystemIO range
0x0000000000000295-0x0000000000000296 conflicts with OpRegion
0x0000000000000290-0x0000000000000299 (\_GPE.HWM) (20200925/utaddress-213)
2021-06-02T11:53:24.172447+01:00 ns2 kernel: ACPI: This conflict may cause
random problems and system instability
2021-06-02T11:53:24.172480+01:00 ns2 kernel: ACPI: If an ACPI driver is
available for this device, you should use it instead of the native driver


The only difference between the 2 outputs are with the ACPI systemIO range, but
that seems to be date related, 20200925 vs 20190703.

This is on an Asus Z97I-Plus with the output of lscpu:
localhost:/usr/local # lscpu
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   39 bits physical, 48 bits virtual
CPU(s):                          4
On-line CPU(s) list:             0-3
Thread(s) per core:              2
Core(s) per socket:              2
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           60
Model name:                      Intel(R) Core(TM) i3-4160 CPU @ 3.60GHz
Stepping:                        3
CPU MHz:                         3401.785
CPU max MHz:                     3600.0000
CPU min MHz:                     800.0000
BogoMIPS:                        7195.92
Virtualization:                  VT-x
L1d cache:                       64 KiB
L1i cache:                       64 KiB
L2 cache:                        512 KiB
L3 cache:                        3 MiB
NUMA node0 CPU(s):               0-3
Vulnerability Itlb multihit:     KVM: Mitigation: VMX disabled
Vulnerability L1tf:              Mitigation; PTE Inversion; VMX conditional
cache flushes, SMT vulnerable
Vulnerability Mds:               Mitigation; Clear CPU buffers; SMT vulnerable
Vulnerability Meltdown:          Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled
via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and
__user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Full generic retpoline, IBPB
conditional, IBRS_FW, STIBP conditional, RSB filling
Vulnerability Srbds:             Mitigation; Microcode
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep
mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe
syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl
xtopology nonstop_tsc cpuid aperfmperf pni pclmulq
                                 dq dtes64 monitor ds_cpl vmx est tm2 ssse3
sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes
xsave avx f16c rdrand lahf_lm abm cpuid_fault epb invpcid_single pti ssbd ibrs
ibpb stibp tpr_shadow vnmi flexpriority ept vpi
                                 d ept_ad fsgsbase tsc_adjust bmi1 avx2 smep
bmi2 erms invpcid xsaveopt dtherm arat pln pts md_clear flush_l1d


uname:
Linux localhost 5.3.18-59.5-default #1 SMP Wed Jun 2 08:21:36 UTC 2021
(eaf040d) x86_64 x86_64 x86_64 GNU/Linux


You are receiving this mail because: