Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve

From	Ian Jackson <ijackson@chiark.greenend.org.uk>
Newsgroups	linux.debian.bugs.dist, linux.debian.kernel
Subject	Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve
Date	2025-07-16 17:20 +0200
Message-ID	<L9c5j-rL6-1@gated-at.bofh.it> (permalink)
References	<L8O2Z-ck3-3@gated-at.bofh.it> <L94Kt-n4y-3@gated-at.bofh.it> <L8O2Z-ck3-3@gated-at.bofh.it> <L94Kt-n4y-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

Salvatore Bonaccorso writes ("Re: Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve"):
> Control: tags -1 + moreinfo
...
> I suspect this is a deliberate change maybe e8cd4a8d5b88 ("ACPI:
> battery: negate current when discharging"), can you try with that
> commit reverted?

That sounds very likely.

I'm at Debconf and building kernels and rebooting my machine is quite
disruptive.  When I'm back home I'll have a spare laptop I could try
this out on; that would be over a week from now at the earliest.

(Also please would you point me at the right instructions for trying
such a thing?  I can get the kernel source package and patch it but it
wants to build a lot of flavours so the build is very slow, and
nowadays I suspect I may have some kind of restricted boot problem?)

> If that is sucessfull we would appreciate if you can take it to
> upstream involved people to ask if the side effect you are seeing is
> considered a regression bug or to be kept deliberately.
> 
> Can you please do that?

My experience with Linux upstream hasn't always been great but I can
give it a go.  Am I just to post to lmkl, or what ?

Ian.

-- 
Ian Jackson <ijackson@chiark.greenend.org.uk>   These opinions are my own.  

Pronouns: they/he.  If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.

Thread

Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-07-15 15:40 +0200
  Processed: Re: Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64:  uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-07-16 09:30 +0200
  Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Salvatore Bonaccorso <carnil@debian.org> - 2025-07-16 09:30 +0200
    Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-07-16 17:20 +0200
      Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Salvatore Bonaccorso <carnil@debian.org> - 2025-07-17 14:40 +0200
        Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-07-17 15:00 +0200
    Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Bastian Blank <waldi@debian.org> - 2025-07-17 21:50 +0200
  Processed: Re: Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64:  uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve "Debian Bug Tracking System" <owner@bugs.debian.org> - 2025-07-17 22:40 +0200
  Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Bastian Blank <waldi@debian.org> - 2025-07-17 22:40 +0200
    Bug#1109344: /boot/vmlinuz-6.12.35+deb13-amd64: uevent field power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW now -ve Salvatore Bonaccorso <carnil@debian.org> - 2025-07-18 15:30 +0200

csiph-web