linux-kernel - Re: module nct6775 reporting wrong values after resume from suspend

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <193d6c42-7e0b-49c9-9e95-db458d4baaa7@roeck-us.net>
Date: Wed, 30 Oct 2024 09:08:54 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: M3 <mys3lf@...tonmail.com>, "jdelvare@...e.com" <jdelvare@...e.com>,
 "linux-hwmon@...r.kernel.org" <linux-hwmon@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Cc: "christian@...sel.eu" <christian@...sel.eu>
Subject: Re: module nct6775 reporting wrong values after resume from suspend

On 10/30/24 08:36, M3 wrote:
[ ... ]

> sensors reporting before systemctl suspend
> 
> 
> $ sensors nct6798-isa-02a0
> 
> 
> nct6798-isa-02a0
> Adapter: ISA adapter
> CPU Fan:            1162 RPM  (min =    0 RPM)
> Chassis Front Fan1:  495 RPM  (min =    0 RPM)
> Chassis Rear Fan:    491 RPM  (min =    0 RPM)
> Chassis Front Fan2:  742 RPM  (min =    0 RPM)
> Motherboard: *+30.0°C*  (high = +80.0°C, hyst = +75.0°C)
>                                (crit = +100.0°C)  sensor = thermistor
> 
> ----------
> sensors reporting after resume from suspend (fan rpm's are now similar)
> 
> $ sensors nct6798-isa-02a0
> 
> 
> nct6798-isa-02a0
> Adapter: ISA adapter
> CPU Fan:            1165 RPM  (min =    0 RPM)
> Chassis Front Fan1:  494 RPM  (min =    0 RPM)
> Chassis Rear Fan:    510 RPM  (min =    0 RPM)
> Chassis Front Fan2:  716 RPM  (min =    0 RPM)
> Motherboard: *+21.0°C*  (high = +80.0°C, hyst = +75.0°C)
>                                (crit = +100.0°C)  sensor = thermistor
> 

It is impossible to say what might be wrong from this information. Any chance to provide
output from hwmon device attributes (from sys/class/hwmon/hwmonX/) from before and after
re-loading the module ?

Guenter