From: Marc MERLIN <marc@merlins.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-acpi@vger.kernel.org
Subject: Re: s2idle on kdell xps 9730 does go to sleep but laptop is warm
Date: Sun, 1 Jun 2025 07:23:28 -0700 [thread overview]
Message-ID: <aDxiYDc-pOVY-p3t@merlins.org> (raw)
In-Reply-To: <20250531231626.GB179983@mit.edu>
On Sat, May 31, 2025 at 07:16:26PM -0400, Theodore Ts'o wrote:
> On Sat, May 31, 2025 at 02:26:32PM -0700, Marc MERLIN wrote:
> > This is still a problem. Is there more info I can provide? For now it's
> > bad enough that I can't have the battery be in S3 sleep for 24H without
> > the batteries running out :-/
>
> I believe what is going on is that on more modern systems, it relies
> on the OS's drivers to power done various peripherals (e.g., graphics,
> SSD's, etc.) and this is no longer being done by the low-level
> firmware. With Linux the CPU is put to sleep, but there's a lot more
> on a modern mainboard than just the CPU....
Hi Ted, nice to hear from you. Yes, I agree that what you wrote totally
matches my experience and the reason why the laptop was so warm, even in
sleep mode.
So, given that this is not a new problem, are there any new options in
linux drivers and/or kernel options to have linux do this (shut down
each subsystem)?
Thanks,
Marc
--
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Home page: http://marc.merlins.org/ | PGP 7F55D5F27AAF9D08
next prev parent reply other threads:[~2025-06-01 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 7:45 s2idle on kdell xps 9730 does go to sleep but laptop is warm Marc MERLIN
2025-05-31 21:26 ` Marc MERLIN
2025-05-31 23:16 ` Theodore Ts'o
2025-06-01 14:23 ` Marc MERLIN [this message]
2025-06-02 14:23 ` Rafael J. Wysocki
2025-06-02 20:56 ` Marc MERLIN
2025-06-27 22:51 ` Marc MERLIN
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=aDxiYDc-pOVY-p3t@merlins.org \
--to=marc@merlins.org \
--cc=linux-acpi@vger.kernel.org \
--cc=tytso@mit.edu \
/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