All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: platform-driver-x86@vger.kernel.org
Subject: [Bug 221065] New: ideapad_acpi: unexpected charge_types spam on Yoga Pro 7 14ASP9
Date: Mon, 09 Feb 2026 07:50:47 +0000	[thread overview]
Message-ID: <bug-221065-215701@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=221065

            Bug ID: 221065
           Summary: ideapad_acpi: unexpected charge_types spam on Yoga Pro
                    7 14ASP9
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: low
          Priority: P3
         Component: Platform_x86
          Assignee: drivers_platform_x86@kernel-bugs.osdl.org
          Reporter: rbitton@linux.com
        Regression: No

Hi,

I'm experiencing constant dmesg spam from ideapad_acpi on my Lenovo Yoga Pro 7
14ASP9:

[  733.997072] ideapad_acpi VPC2004:00: unexpected charge_types: both [Fast]
and [Long_Life] are enabled

This started on 6.19.0 on both my distro's mainline kernel and the vanilla
mainline kernel I compiled. The issue is not present in 6.18. It happens about
every minute starting about a minute after boot regardless of if I'm charging
or not.

Model: Lenovo Yoga Pro 7 14ASP9 (83HN)
CPU: AMD Ryzen AI 9 365
BIOS: PSCN17WW (up to date)

The laptop appears to be reporting both Fast and Long_Life charge modes
simultaneously, which the driver considers unexpected. Functionally everything
works fine, including fast charging, but the log spam is excessive.

Of note:
zsh rbitton@rbitton-linux3 01:46 /sys/class/power_supply/BAT0 > cat
/sys/class/power_supply/BAT*/charge_types    
[Fast] Standard Long_Life

All attempts to fix it on my end have failed.Let me know if you need any
additional information; I would be more than willing to test any fixes.

Thanks,
Raphael Bitton

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2026-02-09  7:50 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-09  7:50 bugzilla-daemon [this message]
2026-02-09  9:10 ` [Bug 221065] ideapad_acpi: unexpected charge_types spam on Yoga Pro 7 14ASP9 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

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@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.