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: Tue, 10 Feb 2026 18:57:06 +0000 [thread overview]
Message-ID: <bug-221065-215701-AjOs5V9mkK@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 #7 from Avraham Hollander (anhollander516@gmail.com) ---
(In reply to Rong Zhang from comment #6)
> Hi Avraham,
>
> On Tue, 2026-02-10 at 17:56 +0000, bugzilla-daemon@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=221065
> >
> > Avraham Hollander (anhollander516@gmail.com) changed:
> >
> > What |Removed |Added
> >
> ----------------------------------------------------------------------------
> > CC| |anhollander516@gmail.com
> >
> > --- Comment #3 from Avraham Hollander (anhollander516@gmail.com) ---
> > I'm also seeing this on an IdeaPad 5 2-in-1 14AHP9 (83DR), after upgrading
> > to
> > Linux 6.19.
> >
> > I'll attached dmesg and acpidump, but this is not a vanilla kernel, so take
> > it
> > with a grain of salt. This kernel doesn't have debugfs, so I can't provide
> > that.
>
> Thanks for your dmesg and acpidump. I will find some time looking into
> them.
>
> As for debugfs, every major distribution have it enabled [1] and so do
> any sane downstream kernel. debugfs can only be accessed by the root
> user by default. Did you try with the root user (e.g., `sudo -i')?
>
> [1]: https://oracle.github.io/kconfigs/?config=UTS_RELEASE&config=DEBUG_FS
>
> And since you are using a downstream kernel, could you provide a link
> to its website or so? So that I can check if it's the root cause
> (though unlikely).
>
> > /sys/class/power_supply/BAT0/charge_types is [Fast] Standard Long_Life.
> >
> > /sys/bus/platform/drivers/ideapad_acpi/VPC2004:00/conservation_mode is 0.
> >
> > I'm using the BIOS default charging configuration and haven't set up any
> > weird
> > ACPI stuff, afaik.
>
> Thanks,
> Rong
I build my own kernel with a selection of out-of-tree patches
(https://github.com/Frogging-Family/linux-tkg) and a heavily tuned
configuration, which indeed doesn't have debugfs. I don't mind building a
vanilla kernel with debugfs; I have just been using my laptop and haven't had
the time too. Probably later today.
--
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-02-10 18:57 UTC|newest]
Thread overview: 63+ 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 [this message]
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
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-AjOs5V9mkK@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox