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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 06 Aug 2014 23:20:32 -0700
From:	Guenter Roeck <>
CC:	Benjamin Herrenschmidt <>,
	LKML <>,
	Jean Delvare <>
Subject: Re: [PATCH 5/5] Export the temperatures via hwmon

On 08/06/2014 11:03 PM, Goffredo Baroncelli wrote:
> On 08/07/2014 01:18 AM, Guenter Roeck wrote:
>> On Wed, Aug 06, 2014 at 09:05:03PM +0000, Goffredo Baroncelli wrote:
>>> From: Goffredo Baroncelli <>
>>> Export the temperature via the hwmon subsystem.
>>> See the list below for the sensors exported:
>>> $ cd /sys/devices/temperature/hwmon/hwmon0
>>> $ echo "name: $(cat name)"; for i in temp*; do echo "$i: $(cat $i)"; done
>>> name: therm_windtunnel
>>> temp1_input: 59312
>>> temp1_label: CPU
>>> temp2_input: 36750
>>> temp2_label: Case
>>> temp3_input: 37750
>>> temp3_label: Case2
>> Makes me wonder why you don't report the fan speed through hwmon.
> See the first email. Basically when I start to read the fan speed,
> it became irregular, so I stopped the test. I don't know
> if it is a my faulted hardware, or an hw design problem.
> The fan is a 2 wire fan.

Patch 4/5 is "Return the fan speed via sysfs: /sys/devices/temperature/fan_level".

So you are saying that returning the fan speed with a non-hwmon attribute works,
but returning it with a hwmon attribute doesn't ? Not really sure if I understand
your logic. Either fan_level doesn't return the fan speed (or an abstraction of it),
or something in your line of argument is inconsistent.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists