X86 platform drivers
 help / color / mirror / Atom feed
From: "Zhang, Rui" <rui.zhang@intel.com>
To: "benjamin@benis.se" <benjamin@benis.se>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"rafael@kernel.org" <rafael@kernel.org>,
	"W_Armin@gmx.de" <W_Armin@gmx.de>,
	"platform-driver-x86@vger.kernel.org"
	<platform-driver-x86@vger.kernel.org>,
	"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>
Subject: Re: HP Omnibook Ultra Flip 14 - power profiles
Date: Tue, 1 Jul 2025 07:01:59 +0000	[thread overview]
Message-ID: <65f3a229f70279ab0da7efa878b863c7798d4427.camel@intel.com> (raw)
In-Reply-To: <c6Eep72y6E7gc-wUMdcIS9JfNN1_OBjlwGUrd4yGvp2R-PW2-OOoQngQt5H5kiZIccxFAPswaN9G6wVpHuewtoEvUkT52UCzHPibVJh7iYY=@benis.se>

> > > 
> > > how do you suspend the system? and can you attach the dmesg output
> > > after
> > > system "suspended" and resumed?
> > 
> > 
> > Will test later!
> 
> https://drive.benis.se/s/sBZSFGAskp7YZy8
> 
> I hope this is correct.
> 
> 
Yeah, the log shows the system indeed ran a s2idle cycle.
But there is nothing suspicious in the log. The ACPI errors should always
be there no matter if thermald is activated or not.

can you please do the following test?
1. make sure thermald is not activated
2. do a s2idle cycle and make sure that there is no fan spinning
3. launch thermald with --loglevel=debug
4. do a s2idle cycle and make sure that the fan is indeed spinning
5. attach the dmesg output and the output of "journalctl --since=-1h |
grep thermal" and let's see what changes thermald has made.

thanks,
rui


  reply	other threads:[~2025-07-01  7:02 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 13:52 HP Omnibook Ultra Flip 14 - power profiles Benjamin Hasselgren-Hallén
2025-06-23 18:52 ` Armin Wolf
2025-06-25  8:06   ` Benjamin Hasselgren-Hallén
2025-06-25 13:44     ` Armin Wolf
2025-06-25 21:22       ` Benjamin Hasselgren-Hallén
2025-06-25 21:43         ` Armin Wolf
2025-06-26 13:20           ` Benjamin Hasselgren-Hallén
2025-06-27 17:10             ` Armin Wolf
2025-06-27 19:15               ` Kurt Borja
2025-06-27 20:49                 ` Benjamin Hasselgren-Hallén
2025-06-27 21:56                   ` Benjamin Hasselgren-Hallén
2025-06-28  0:40                     ` Armin Wolf
2025-06-30 12:31                       ` Benjamin Hasselgren-Hallén
2025-06-28  0:45                   ` Kurt Borja
2025-06-30 12:32                     ` Benjamin Hasselgren-Hallén
2025-06-30 12:39                       ` Armin Wolf
2025-06-30 12:46                         ` Benjamin Hasselgren-Hallén
2025-06-30 14:49                           ` Armin Wolf
2025-06-30 22:29                             ` Benjamin Hasselgren-Hallén
2025-06-27 20:45               ` Benjamin Hasselgren-Hallén
2025-06-30  1:18               ` Zhang, Rui
2025-06-30 12:48                 ` Benjamin Hasselgren-Hallén
2025-06-30 13:23                   ` Benjamin Hasselgren-Hallén
2025-07-01  7:01                     ` Zhang, Rui [this message]
2025-07-01  7:44                       ` Benjamin Hasselgren-Hallén
     [not found]                         ` <1e02c8f28200d8e3f27589e0ba75a67f2e99d1a4.camel@intel.com>
     [not found]                           ` <Hsi54U41U6V6LB65SJ9b8D_q4OsW-xsvWJSQmvmxo7EfsebwJKc6NnNHLO20CerbcNGL-Q8huoeWtzNuGsCVNrQvJW8ndwTdnIKZJIDbTjg=@benis.se>
2025-07-15 21:21                             ` Benjamin Hasselgren-Hallén
     [not found]                             ` <4d0e07edfa83653fa8330e08fb4520f07bb38448.camel@intel.com>
2025-07-19 20:19                               ` Benjamin Hasselgren-Hallén
2025-07-19 20:38                                 ` Benjamin Hasselgren-Hallén
2025-07-23 21:18                                   ` Benjamin Hasselgren-Hallén
2025-07-01  6:54                   ` Zhang, Rui
2025-07-01  7:04                     ` Benjamin Hasselgren-Hallén
2025-07-02  1:13                       ` Zhang, Rui
2025-07-07 19:53                         ` Benjamin Hasselgren-Hallén

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=65f3a229f70279ab0da7efa878b863c7798d4427.camel@intel.com \
    --to=rui.zhang@intel.com \
    --cc=W_Armin@gmx.de \
    --cc=benjamin@benis.se \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael@kernel.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