mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aaron Burton <aaron@infinitelytimeless.tech>
To: linux-kernel@vger.kernel.org
Cc: chrome-platform@lists.linux.dev
Subject: cros_ec_lpcs breaking sleep mode on HP Elite Dragonfly
Date: Tue, 3 Mar 2026 19:15:03 -0800	[thread overview]
Message-ID: <1015ded1-c3f2-4b0d-92b8-15f413d1242b@infinitelytimeless.tech> (raw)

Hello,

I'm reaching out in regards to an issue I've been trying to troubleshoot 
running Fedora (6.18.13-200.fc43.x86_64) on a HP Elite Dragonfly 
Chromebook. I'm aware this is not relevant to ChromeOS, but I was hoping 
maybe I could get some insight on this sleep mode issue I've been 
experiencing. This affects basically every Linux distro I've tested thus 
far, where if I put this Chromebook to sleep, it will immediately wake 
up. dmesg output when attempting sleep mode:


[ 1478.853982] PM: suspend entry (s2idle)
[ 1478.876379] Filesystems sync: 0.022 seconds
[ 1478.877848] Freezing user space processes
[ 1478.885201] Freezing user space processes completed (elapsed 0.007 
seconds)
[ 1478.885217] OOM killer disabled.
[ 1478.885220] Freezing remaining freezable tasks
[ 1478.886503] Freezing remaining freezable tasks completed (elapsed 
0.001 seconds)
[ 1478.933986] PM: Some devices failed to suspend, or early wake event 
detected
[ 1478.961519] PM: resume devices took 0.027 seconds
[ 1478.961978] OOM killer enabled.
[ 1478.961980] Restarting tasks: Starting
[ 1478.963295] Restarting tasks: Done
[ 1478.963339] random: crng reseeded on system resumption
[ 1478.965350] PM: suspend exit

I've tried troubleshooting via /proc/acpi/wakeup by disabling each 
device enabled one by one, then eventually everything listed, and 
putting it to sleep via systemctl suspend, the machine still wakes up 
instantly without any user input. I eventually stumbled across what was 
causing the issue and it's related to the cros_ec_lpcs kernel driver as 
unloading the driver allowed it to sleep properly, though this also has 
unwanted side effects like the power LED no longer working and some 
issues with USB-C ports. I'd like to find a proper fix for this 
Chromebook EC in the kernel driver, though I don't have much experience 
debugging low-level kernel drivers. I'd be more than happy to provide 
any debugging data to try to fix this issue if possible.


Thanks

Aaron


             reply	other threads:[~2026-03-04  3:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  3:15 Aaron Burton [this message]
2026-03-05 16:35 ` Tzung-Bi Shih
     [not found]   ` <97301467-d7c1-411a-8575-ec3fa303d91d@infinitelytimeless.tech>
2026-03-11  6:25     ` Tzung-Bi Shih

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=1015ded1-c3f2-4b0d-92b8-15f413d1242b@infinitelytimeless.tech \
    --to=aaron@infinitelytimeless.tech \
    --cc=chrome-platform@lists.linux.dev \
    --cc=linux-kernel@vger.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

all inboxes | Powered by JetHome®