From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221065] ideapad_acpi: unexpected charge_types spam on Yoga Pro 7 14ASP9
Date: Sun, 17 May 2026 21:48:44 +0000 [thread overview]
Message-ID: <bug-221065-215701-q6hVECEFYg@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221065-215701@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221065
--- Comment #89 from Rick (rickk1166@gmail.com) ---
(In reply to Rong Zhang from comment #85)
> Please execute
>
> echo 'file drivers/acpi/ec.c +p' | sudo tee /proc/dynamic_debug/control
>
> beforehand, so that I can see which EC queries arrive before the pause event.
>
> Please also spam magic sysrq until the pause finishes, so that I can see
> more samples during the pause. In detail, you can press Alt (keep it
> pressed), press Fn+S once (no need to keep them pressed), and quickly spam l
> and w alternately. You can do some practice beforehand.
>
> With these changes, your dmesg dump will be extremely long, so please upload
> it as an attachment.
>
> Thanks for being willing to investigate the issue together!
I appreciate that you have been keeping things relatively simple and breaking
the information gathering into reasonable chunks.
It took me embarrassingly long to figure out how to attach the files - but at
least they appear to be there now!
Before starting I opened one terminal with
dmesg -w
And in another terminal I did
sudo sysctl kernel.sysrq=1
echo 'file drivers/acpi/ec.c +p' | sudo tee /proc/dynamic_debug/control
As there is now more output into the dmesg window I decided to capture just the
system sitting alone through two pause events and captured that in my first
upload #310145
Next I did the spamming requested (both l and w alternating until the pause
ended)
This is contained in attachment #310146
I noticed with the first spamming attempt that the new output ACPI messages
happen in the dmesg window before the system actually pauses. So I did another
spamming attempt but this time I tried to start spamming as soon as I saw the
dmesg window start displaying the new ACPI messages. It is likely this file
has data that starts earlier and personally I would start looking at this one
first.
This is contained in attachment #310147
As always - let me know if you want more.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2026-05-17 21:48 UTC|newest]
Thread overview: 99+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 7:50 [Bug 221065] New: ideapad_acpi: unexpected charge_types spam on Yoga Pro 7 14ASP9 bugzilla-daemon
2026-02-09 9:10 ` [Bug 221065] " bugzilla-daemon
2026-02-09 11:47 ` bugzilla-daemon
2026-02-09 12:06 ` [Bug 221065] New: " Rong Zhang
2026-02-09 12:11 ` [Bug 221065] " bugzilla-daemon
2026-02-10 17:56 ` bugzilla-daemon
2026-02-10 18:44 ` Rong Zhang
2026-02-10 17:56 ` bugzilla-daemon
2026-02-10 17:57 ` bugzilla-daemon
2026-02-10 18:49 ` bugzilla-daemon
2026-02-10 18:57 ` bugzilla-daemon
2026-02-10 18:58 ` bugzilla-daemon
2026-02-10 19:01 ` bugzilla-daemon
2026-02-10 19:17 ` bugzilla-daemon
2026-02-10 19:23 ` bugzilla-daemon
2026-02-10 19:25 ` bugzilla-daemon
2026-02-10 19:28 ` bugzilla-daemon
2026-02-10 21:20 ` bugzilla-daemon
2026-02-10 21:28 ` bugzilla-daemon
2026-02-10 21:30 ` bugzilla-daemon
2026-02-10 21:32 ` bugzilla-daemon
2026-02-10 21:39 ` bugzilla-daemon
2026-02-10 21:42 ` bugzilla-daemon
2026-02-10 21:43 ` bugzilla-daemon
2026-02-10 21:53 ` bugzilla-daemon
2026-02-11 14:13 ` bugzilla-daemon
2026-02-11 15:02 ` bugzilla-daemon
2026-02-11 15:03 ` bugzilla-daemon
2026-02-11 15:17 ` bugzilla-daemon
2026-02-11 15:17 ` bugzilla-daemon
2026-02-11 15:35 ` bugzilla-daemon
2026-02-11 15:41 ` bugzilla-daemon
2026-02-11 16:58 ` bugzilla-daemon
2026-02-11 17:32 ` bugzilla-daemon
2026-02-11 17:59 ` bugzilla-daemon
2026-02-11 18:04 ` bugzilla-daemon
2026-02-13 13:20 ` bugzilla-daemon
2026-02-13 13:22 ` bugzilla-daemon
2026-02-17 1:37 ` bugzilla-daemon
2026-02-17 1:59 ` bugzilla-daemon
2026-02-17 2:06 ` bugzilla-daemon
2026-02-17 2:32 ` bugzilla-daemon
2026-02-17 2:44 ` bugzilla-daemon
2026-02-17 2:44 ` bugzilla-daemon
2026-02-17 16:28 ` bugzilla-daemon
2026-03-02 10:56 ` bugzilla-daemon
2026-03-02 11:06 ` bugzilla-daemon
2026-03-02 13:45 ` bugzilla-daemon
2026-03-02 14:41 ` bugzilla-daemon
2026-03-02 16:24 ` bugzilla-daemon
2026-03-02 16:35 ` bugzilla-daemon
2026-03-04 18:25 ` bugzilla-daemon
2026-03-04 18:29 ` bugzilla-daemon
2026-03-09 9:19 ` bugzilla-daemon
2026-03-10 18:01 ` bugzilla-daemon
2026-03-24 10:41 ` bugzilla-daemon
2026-03-24 18:40 ` bugzilla-daemon
2026-03-24 18:48 ` bugzilla-daemon
2026-04-01 12:58 ` bugzilla-daemon
2026-04-01 13:35 ` bugzilla-daemon
2026-04-07 19:02 ` bugzilla-daemon
2026-04-11 18:12 ` bugzilla-daemon
2026-04-11 18:57 ` bugzilla-daemon
2026-04-24 22:09 ` bugzilla-daemon
2026-04-26 18:39 ` bugzilla-daemon
2026-04-26 18:43 ` bugzilla-daemon
2026-04-26 18:44 ` bugzilla-daemon
2026-04-26 18:50 ` bugzilla-daemon
2026-04-26 19:08 ` bugzilla-daemon
2026-04-26 19:21 ` bugzilla-daemon
2026-04-27 5:42 ` bugzilla-daemon
2026-04-27 11:50 ` bugzilla-daemon
2026-04-27 12:21 ` bugzilla-daemon
2026-04-27 12:34 ` bugzilla-daemon
2026-04-27 23:58 ` bugzilla-daemon
2026-04-28 9:01 ` bugzilla-daemon
2026-04-28 12:22 ` bugzilla-daemon
2026-04-30 9:30 ` bugzilla-daemon
2026-04-30 17:20 ` bugzilla-daemon
2026-05-14 17:39 ` bugzilla-daemon
2026-05-15 19:58 ` bugzilla-daemon
2026-05-15 22:09 ` bugzilla-daemon
2026-05-15 22:30 ` bugzilla-daemon
2026-05-16 17:37 ` bugzilla-daemon
2026-05-16 17:47 ` bugzilla-daemon
2026-05-16 21:02 ` bugzilla-daemon
2026-05-16 22:21 ` bugzilla-daemon
2026-05-17 1:12 ` bugzilla-daemon
2026-05-17 16:45 ` bugzilla-daemon
2026-05-17 21:32 ` bugzilla-daemon
2026-05-17 21:33 ` bugzilla-daemon
2026-05-17 21:33 ` bugzilla-daemon
2026-05-17 21:48 ` bugzilla-daemon [this message]
2026-05-18 16:48 ` bugzilla-daemon
2026-05-20 15:43 ` bugzilla-daemon
2026-05-20 15:46 ` bugzilla-daemon
2026-05-25 12:14 ` bugzilla-daemon
2026-05-25 17:30 ` bugzilla-daemon
2026-05-26 12:33 ` bugzilla-daemon
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=bug-221065-215701-q6hVECEFYg@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=platform-driver-x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.