| Summary: | Possible missing driver in kernel, Kernel driver NCT6775. | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Sébastien B. <sb.cw> |
| Component: | RPM Packages | Assignee: | Kernel and Drivers maintainers <kernel> |
| Status: | ASSIGNED --- | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | chb0, doktor5000, fri, ouaurelien |
| Version: | 8 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel-5.10.16-1.mga8.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Sébastien B.
2021-02-23 09:20:56 CET
both modules are available. $ /sbin/modinfo nct6775 filename: /lib/modules/5.10.16-desktop-1.mga8/kernel/drivers/hwmon/nct6775.ko.xz license: GPL description: Driver for NCT6775F and compatible chips author: Guenter Roeck <linux@roeck-us.net> depends: hwmon-vid retpoline: Y intree: Y name: nct6775 vermagic: 5.10.16-desktop-1.mga8 SMP mod_unload parm: force_id:Override the detected device ID (ushort) parm: fan_debounce:Enable debouncing for fan RPM signal (ushort) $ /sbin/modinfo coretemp filename: /lib/modules/5.10.16-desktop-1.mga8/kernel/drivers/hwmon/coretemp.ko.xz license: GPL description: Intel Core temperature monitor author: Rudolf Marek <r.marek@assembler.cz> alias: cpu:type:x86,ven0000fam*mod*:feature:*01C0* depends: retpoline: Y intree: Y name: coretemp vermagic: 5.10.16-desktop-1.mga8 SMP mod_unload parm: tjmax:TjMax value in degrees Celsius (int) Thank you for your quick reply. However do you know where the problem may be? does it help if you boot with: iommu=relaxed on kernel command line ? I try that now, and I get back to you, thank you. Hello,
After following your instructions (reboot edition adding the option iommu = relaxed) I get the following output from the sensors command:
"sensors
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +23.0°C (high = +80.0°C, crit = +100.0°C)
Core 0: +22.0°C (high = +80.0°C, crit = +100.0°C)
Core 1: +19.0°C (high = +80.0°C, crit = +100.0°C)
Core 2: +20.0°C (high = +80.0°C, crit = +100.0°C)
Core 3: +23.0°C (high = +80.0°C, crit = +100.0°C)
nct6776-isa-0290
Adapter: ISA adapter
Vcore: 880.00 mV (min = +0.00 V, max = +1.74 V)
in1: 1.85 V (min = +0.00 V, max = +0.00 V) ALARM
AVCC: 3.36 V (min = +2.98 V, max = +3.63 V)
+3.3V: 3.34 V (min = +2.98 V, max = +3.63 V)
in4: 656.00 mV (min = +0.00 V, max = +0.00 V) ALARM
in5: 1.72 V (min = +0.00 V, max = +0.00 V) ALARM
in6: 808.00 mV (min = +0.00 V, max = +0.00 V) ALARM
3VSB: 3.44 V (min = +2.98 V, max = +3.63 V)
Vbat: 3.25 V (min = +2.70 V, max = +3.63 V)
fan1: 457 RPM (min = 0 RPM)
fan2: 812 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
fan5: 0 RPM (min = 0 RPM)
SYSTIN: +27.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor
CPUTIN: +25.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
AUXTIN: +44.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor
PECI Agent 0: +24.0°C (high = +80.0°C, hyst = +75.0°C)
(crit = +100.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
"
However, dmesg errors are still present:
ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20200925/utaddress-204)
[ 2.809520] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.809522] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR2) (20200925/utaddress-204)
[ 2.809526] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200925/utaddress-204)
[ 2.809530] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.809530] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR2) (20200925/utaddress-204)
[ 2.809534] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200925/utaddress-204)
[ 2.809537] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200925/utaddress-204)
[ 2.809540] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.809541] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR2) (20200925/utaddress-204)
[ 2.809544] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20200925/utaddress-204)
[ 2.809548] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20200925/utaddress-204)
[ 2.809551] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver"
output of the journalctl -r -p err command: - Logs begin at Tue 2021-02-23 07:05:39 CET, end at Tue 2021-02-23 10:10:49 CET. -- févr. 23 10:10:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: SYSTIN: 27.0 C (limit = 0.0 C, hysteresis = 0.0 C) [ALARM] févr. 23 10:10:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in6: +0.81 V (min = +0.00 V, max = +0.00 V) [ALARM] févr. 23 10:10:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in5: +1.72 V (min = +0.00 V, max = +0.00 V) [ALARM] févr. 23 10:10:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in4: +0.70 V (min = +0.00 V, max = +0.00 V) [ALARM] févr. 23 10:10:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in1: +1.85 V (min = +0.00 V, max = +0.00 V) [ALARM] févr. 23 10:09:57 localhost.localdomain pipewire[4534]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name févr. 23 10:09:53 localhost.localdomain pipewire[4484]: Failed to receive portal pid: org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name 'org.freedesktop.portal.Desktop': no such name févr. 23 10:09:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: SYSTIN: 27.0 C (limit = 0.0 C, hysteresis = 0.0 C) [ALARM] févr. 23 10:09:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in6: +0.81 V (min = +0.00 V, max = +0.00 V) [ALARM] févr. 23 10:09:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in5: +1.72 V (min = +0.00 V, max = +0.00 V) [ALARM] févr. 23 10:09:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in4: +0.76 V (min = +0.00 V, max = +0.00 V) [ALARM] févr. 23 10:09:48 localhost.localdomain sensord[1052]: Sensor alarm: Chip nct6776-isa-0290: in1: +1.84 V (min = +0.00 V, max = +0.00 V) [ALARM] However, it should be noted that the proposed command removes the line: févr. 23 10:13:53 localhost.localdomain kernel: watchdog: watchdog0: watchdog did not stop! it may not have an impact, but I wanted to point it out. what do you think is missing? your system is using nct6776, not nct6775 those ACPI errors comes from buggy bios coding, nothing we can fix. Good evening, If it comes from my bios code, how can I explain that with Debian Bullseye kernel 5.10.xx, I don't have any of these errors? probably differences in kernel configs or they have patched out some of the ACPI warnings... I have thought of doing that for Mageia as people cant really do anything about them anyway... Can you attach debian kernel config so I can compare if something stands out Hi, thanks for reporting this. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it) Assignee:
bugsquad =>
kernel (In reply to Thomas Backlund from comment #10) > probably differences in kernel configs or they have patched out some of the > ACPI warnings... > > I have thought of doing that for Mageia as people cant really do anything > about them anyway... > > > Can you attach debian kernel config so I can compare if something stands out Thank you for these clarifications and for your time. (In reply to Thomas Backlund from comment #10) > probably differences in kernel configs or they have patched out some of the > ACPI warnings... > > I have thought of doing that for Mageia as people cant really do anything > about them anyway... > > > Can you attach debian kernel config so I can compare if something stands out Hello, "Can you attach debian kernel config so I can compare if something stands out" Unfortunately I will not be able to respond positively. I deleted my Debian images, and I only have Mageia 8 systems left. Thank you very much for your investment. Can we move the bug to resolved? Hi it looks like I have a similar issue with the support for nct6795 : ____________________________________________________________________________ $ journalctl -b --no-pager --no-hostname | grep -i sensor avril 06 17:28:42 systemd[1]: Starting Initialize hardware monitoring sensors... avril 06 17:28:42 systemd[1]: Finished Initialize hardware monitoring sensors. avril 06 17:28:42 systemd[1]: Starting Sensor Information Logging... avril 06 17:28:42 sensord[1014]: sensord started avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in1: +1.03 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 systemd[1]: Started Sensor Information Logging. avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in4: +1.02 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in5: +0.15 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in6: +0.70 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in9: +1.83 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in11: +0.78 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in12: +1.10 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in13: +0.68 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: in14: +1.55 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: Sensor alarm: Chip nct6795-isa-0a20: SYSTIN: 35.0 C (limit = 0.0 C, hysteresis = 0.0 C) [ALARM] avril 06 17:28:42 sensord[1014]: Chip: nct6795-isa-0a20 avril 06 17:28:42 sensord[1014]: Adapter: ISA adapter avril 06 17:28:42 sensord[1014]: Vcore: +1.42 V (min = +0.00 V, max = +1.74 V) avril 06 17:28:42 sensord[1014]: in1: +1.03 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: AVCC: +3.39 V (min = +2.98 V, max = +3.63 V) avril 06 17:28:42 sensord[1014]: +3.3V: +3.39 V (min = +2.98 V, max = +3.63 V) avril 06 17:28:42 sensord[1014]: in4: +1.02 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: in5: +0.15 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: in6: +0.70 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: 3VSB: +3.38 V (min = +2.98 V, max = +3.63 V) avril 06 17:28:42 sensord[1014]: Vbat: +3.33 V (min = +2.70 V, max = +3.63 V) avril 06 17:28:42 sensord[1014]: in9: +1.83 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: in10: +0.00 V (min = +0.00 V, max = +0.00 V) avril 06 17:28:42 sensord[1014]: in11: +0.78 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: in12: +1.10 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: in13: +0.68 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: in14: +1.55 V (min = +0.00 V, max = +0.00 V) [ALARM] avril 06 17:28:42 sensord[1014]: fan1: 0 RPM (min = 0 RPM) avril 06 17:28:42 sensord[1014]: fan2: 830 RPM (min = 0 RPM) avril 06 17:28:42 sensord[1014]: fan3: 930 RPM (min = 0 RPM) avril 06 17:28:42 sensord[1014]: fan4: 1004 RPM (min = 0 RPM) avril 06 17:28:42 sensord[1014]: fan5: 0 RPM (min = 0 RPM) avril 06 17:28:42 sensord[1014]: SYSTIN: 35.0 C (limit = 0.0 C, hysteresis = 0.0 C) [ALARM] avril 06 17:28:42 sensord[1014]: CPUTIN: 36.0 C (limit = 115.0 C, hysteresis = 90.0 C) avril 06 17:28:42 sensord[1014]: AUXTIN0: 42.5 C (limit = 115.0 C, hysteresis = 90.0 C) avril 06 17:28:42 sensord[1014]: AUXTIN1: -128.0 C avril 06 17:28:42 sensord[1014]: AUXTIN2: 38.0 C avril 06 17:28:42 sensord[1014]: AUXTIN3: -3.0 C avril 06 17:28:42 sensord[1014]: SMBUSMASTER 0: 46.0 C avril 06 17:28:42 sensord[1014]: PCH_CHIP_CPU_MAX_TEMP: 0.0 C avril 06 17:28:42 sensord[1014]: PCH_CHIP_TEMP: 0.0 C avril 06 17:28:42 sensord[1014]: PCH_CPU_TEMP: 0.0 C avril 06 17:28:42 sensord[1014]: beep_enable: Sound alarm disabled avril 06 17:28:42 sensord[1014]: Chip: amdgpu-pci-2900 avril 06 17:28:42 sensord[1014]: Adapter: PCI adapter avril 06 17:28:42 sensord[1014]: vddgfx: +0.72 V avril 06 17:28:42 sensord[1014]: fan1: 940 RPM (min = 0 RPM) avril 06 17:28:42 sensord[1014]: edge: 30.0 C avril 06 17:28:42 sensord[1014]: Chip: k10temp-pci-00c3 avril 06 17:28:42 sensord[1014]: Adapter: PCI adapter avril 06 17:28:42 sensord[1014]: Tctl: 46.9 C avril 06 17:28:42 sensord[1014]: Tdie: 46.9 C avril 06 17:28:42 sensord[1014]: Tccd1: 41.8 C ___________________________________________________________________________ CC:
(none) =>
chb0
Florian Hubold
2024-02-25 20:22:12 CET
CC:
(none) =>
doktor5000 Mga8 is EOL What is the status for this driver on mga9? CC:
(none) =>
fri |