linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Eric Biggers <ebiggers@kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Linux PM <linux-pm@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Lukasz Luba <lukasz.luba@arm.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Zhang Rui <rui.zhang@intel.com>,
	Neil Armstrong <neil.armstrong@linaro.org>
Subject: Re: [PATCH v3] thermal: core: Call monitor_thermal_zone() if zone temperature is invalid
Date: Tue, 16 Jul 2024 13:15:00 +0200	[thread overview]
Message-ID: <20240716131500.35cf4f00@mir> (raw)
In-Reply-To: <20240716125538.09f716d1@mir>

Hi

On 2024-07-16, Stefan Lippers-Hollmann wrote:
> On 2024-07-16, Rafael J. Wysocki wrote:
> > On Tue, Jul 16, 2024 at 1:48 AM Stefan Lippers-Hollmann <s.l-h@gmx.de> wrote:
> > > On 2024-07-15, Rafael J. Wysocki wrote:
> > > > On Mon, Jul 15, 2024 at 2:54 PM Stefan Lippers-Hollmann <s.l-h@gmx.de> wrote:
> > > > > On 2024-07-15, Rafael J. Wysocki wrote:
> > > > > > On Mon, Jul 15, 2024 at 11:09 AM Daniel Lezcano
> > > > > > <daniel.lezcano@linaro.org> wrote:
> > > > > > > On 15/07/2024 06:45, Eric Biggers wrote:
> > > > > > > > On Thu, Jul 04, 2024 at 01:46:26PM +0200, Rafael J. Wysocki wrote:
> > > > > > > >> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> > > [...]
> > > > > Silencing the warnings is already a big improvement - and that patch
> > > > > works to this extent for me with an ax200, thanks.
> > > >
> > > > So attached is a patch that should avoid enabling the thermal zone
> > > > when it is not ready for use in the first place, so it should address
> > > > both the message and the useless polling.
> > > >
> > > > I would appreciate giving it a go (please note that it hasn't received
> > > > much testing so far, though).
> > >
> > > Sadly this patch doesn't seem to help:
> >
> > This is likely because it is missing checks for firmware image type.
> > I've added them to the attached new version.  Please try it.
> >
> > I've also added two pr_info() messages to get a better idea of what's
> > going on, so please grep dmesg for "Thermal zone not ready" and
> > "Enabling thermal zone".
>
> This is the output with the patch applied:

The ax200 wlan interface is currently not up/ configured (system
using its wired ethernet cards instead), the thermal_zone1 stops
if I manually enable the interface (ip link set dev wlp4s0 up)
after booting up:

$ dmesg | grep -i -e iwlwifi -e thermal
[    0.080899] CPU0: Thermal monitoring enabled (TM1)
[    0.113768] thermal_sys: Registered thermal governor 'fair_share'
[    0.113770] thermal_sys: Registered thermal governor 'bang_bang'
[    0.113771] thermal_sys: Registered thermal governor 'step_wise'
[    0.113772] thermal_sys: Registered thermal governor 'user_space'
[    0.113773] thermal_sys: Registered thermal governor 'power_allocator'
[    3.759673] iwlwifi 0000:04:00.0: enabling device (0140 -> 0142)
[    3.764918] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
[    3.764974] iwlwifi 0000:04:00.0: PCI dev 2723/0084, rev=0x340, rfid=0x10a100
[    3.769432] iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
[    3.873466] iwlwifi 0000:04:00.0: loaded firmware version 77.a20fb07d.0 cc-a0-77.ucode op_mode iwlmvm
[    3.907122] iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    3.907886] iwl_mvm_thermal_zone_register: Thermal zone not ready
[    4.032380] iwlwifi 0000:04:00.0: Detected RF HR B3, rfid=0x10a100
[    4.032392] thermal thermal_zone1: Enabling thermal zone
[    4.098308] iwlwifi 0000:04:00.0: base HW address: 94:e6:f7:XX:XX:XX
[    4.112535] thermal thermal_zone1: failed to read out thermal zone (-61)
[    4.128306] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[    4.369396] thermal thermal_zone1: failed to read out thermal zone (-61)
[    4.625385] thermal thermal_zone1: failed to read out thermal zone (-61)
[    4.881416] thermal thermal_zone1: failed to read out thermal zone (-61)
[    5.137377] thermal thermal_zone1: failed to read out thermal zone (-61)
[    5.394377] thermal thermal_zone1: failed to read out thermal zone (-61)
[    5.649412] thermal thermal_zone1: failed to read out thermal zone (-61)
[    5.905379] thermal thermal_zone1: failed to read out thermal zone (-61)
[    6.161380] thermal thermal_zone1: failed to read out thermal zone (-61)
[    6.418381] thermal thermal_zone1: failed to read out thermal zone (-61)
[    6.673381] thermal thermal_zone1: failed to read out thermal zone (-61)
[    6.929377] thermal thermal_zone1: failed to read out thermal zone (-61)
               [...]
[   21.009413] thermal thermal_zone1: failed to read out thermal zone (-61)
[   21.265496] thermal thermal_zone1: failed to read out thermal zone (-61)
[   21.521462] thermal thermal_zone1: failed to read out thermal zone (-61)
[   21.777481] thermal thermal_zone1: failed to read out thermal zone (-61)
[   22.033468] thermal thermal_zone1: failed to read out thermal zone (-61)
[   22.213120] thermal thermal_zone1: Enabling thermal zone
[   22.283954] iwlwifi 0000:04:00.0: Registered PHC clock: iwlwifi-PTP, with index: 0

Regards
	Stefan Lippers-Hollmann


  reply	other threads:[~2024-07-16 11:15 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 11:46 [PATCH v3] thermal: core: Call monitor_thermal_zone() if zone temperature is invalid Rafael J. Wysocki
2024-07-04 12:49 ` Daniel Lezcano
2024-07-04 12:52   ` Neil Armstrong
2024-07-04 14:23     ` Rafael J. Wysocki
2024-07-04 14:21   ` Rafael J. Wysocki
2024-07-04 16:53     ` Daniel Lezcano
2024-07-04 16:58       ` Rafael J. Wysocki
2024-07-15  4:45 ` Eric Biggers
2024-07-15  9:06   ` Stefan Lippers-Hollmann
2024-07-15 10:52     ` Rafael J. Wysocki
2024-07-15  9:09   ` Daniel Lezcano
2024-07-15 11:21     ` Rafael J. Wysocki
2024-07-15 12:54       ` Stefan Lippers-Hollmann
2024-07-15 14:48         ` Rafael J. Wysocki
2024-07-15 21:12           ` Eric Biggers
2024-07-15 23:48           ` Stefan Lippers-Hollmann
2024-07-16 10:05             ` Rafael J. Wysocki
2024-07-16 10:55               ` Stefan Lippers-Hollmann
2024-07-16 11:15                 ` Stefan Lippers-Hollmann [this message]
2024-07-16 11:36                   ` Rafael J. Wysocki
2024-07-16 12:10                     ` Daniel Lezcano
2024-07-16 12:18                       ` Rafael J. Wysocki
2024-07-16 12:30                     ` Rafael J. Wysocki
2024-07-16 13:20                       ` Stefan Lippers-Hollmann
2024-07-16 14:04                         ` Rafael J. Wysocki
2024-07-16 16:37                           ` Oleksandr Natalenko
2024-07-16 17:03                             ` Rafael J. Wysocki
2024-07-16 23:30                           ` Stefan Lippers-Hollmann
2024-07-16 11:19                 ` Rafael J. Wysocki
2024-07-15 10:49   ` Rafael J. Wysocki

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=20240716131500.35cf4f00@mir \
    --to=s.l-h@gmx.de \
    --cc=daniel.lezcano@linaro.org \
    --cc=ebiggers@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).