From: Steven J Abner <pheonix.sja@att.net>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: thermal driver patch
Date: Mon, 29 Aug 2022 08:20:09 -0400 [thread overview]
Message-ID: <L9MDHR.JVBXTJ2L6TPP2@att.net> (raw)
In-Reply-To: <0f961ea6-4948-0b7a-e01d-d62ca4065af8@infradead.org>
On Mon, Aug 29, 2022 at 05:47, Randy Dunlap <rdunlap@infradead.org>
wrote:
> a. the exact message(s) [copy-paste]
> c. what kernel version is causing the problem
[ 0.000000] Linux version 5.18.12-051812-generic (kernel@sita) (gcc
(Ubuntu 11.3.0-4ubuntu1) 11.3.0, GNU ld (GNU Binutils for Ubuntu)
2.38.50.20220629) #202207150942 SMP PREEMPT_DYNAMIC Fri Jul 15 10:10:55
UTC 2022
[ 5.244369] thermal thermal_zone0: failed to read out thermal zone
(-61)
[ 0.000000] Linux version 5.4.204-0504204-generic (kernel@kathleen)
(gcc version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.1)) #202207071639 SMP
Thu Jul 7 16:59:09 UTC 2022
[ 5.207243] thermal thermal_zone0: failed to read out thermal zone
(-61)
as to reproduce, can only think of saying: boot up kernel without
patched?
additional info that may? help:
I did not trace what calls 'update_temperature', just saw any call to it
will cause message due to it's call to 'thermal_zone_get_temp', which
states
no thermal_zone_device should provide or be requesting an update.
It may be that if 'thermal_zone_get_temp' where removed was actual
function's
intent, and all instances in this file and other function's use was a
case of designer debugging or signaling a deprecated API? That was my
intent on saying
'for you to do and review', because it looked like a lot of functions
could be
updated to take into account that no device should call functions that
start off
by calling 'thermal_zone_get_temp'.
It is more probable that my patch suggestion is wrong and calls to
'update_temperature' are suppose to fail with return -ENODEV always
allowing
other calls to 'update_temperature' to fail also. With proposed code,
I've not
seen adverse side effects. It just removed dmesg error, but was hoping
I would
get lucky and it was the reason for CPUTIN -62C without actually hard
work of
finding real reason.
additional dmesg info:
only other 'thermal' are 'thermal_sys' loading governors
smpboot: CPU0: AMD Ryzen 5 2400G with Radeon Vega Graphics (family:
0x17, model: 0x11, stepping: 0x0)
from lspci:
Kernel driver in use: k10temp
from lsmod:
nct6775
hwmon_vid
these 2 removed in personal configs, but used in the two ubuntu kernel
builds:
wmi
wmi_bmof
Steve
next prev parent reply other threads:[~2022-08-29 12:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DL9RGR.8W3XFSCFFYXI2.ref@att.net>
2022-08-17 10:39 ` thermal driver patch Steven J Abner
2022-08-29 5:47 ` Randy Dunlap
2022-08-29 12:20 ` Steven J Abner [this message]
2022-08-29 22:06 ` Randy Dunlap
2022-09-01 5:59 ` Daniel Lezcano
2022-09-01 12:14 ` Steven J Abner
2022-09-07 11:15 ` Steven J Abner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=L9MDHR.JVBXTJ2L6TPP2@att.net \
--to=pheonix.sja@att.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox