Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1252950

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

Cross-posted to 2 groups.

Show all headers | View raw

Control: tags -1 + moreinfo

Hi Ian,

On Tue, Jul 15, 2025 at 02:36:57PM +0100, Ian Jackson wrote:
> Package: src:linux
> Version: 6.12.35-1
> Severity: normal
> File: /boot/vmlinuz-6.12.35+deb13-amd64
> X-Debbugs-Cc: debian-amd64@lists.debian.org
> User: debian-amd64@lists.debian.org
> Usertags: amd64
> 
> Control: affects chiark-utils-bin 8.0.0
> 
> My battery monitor applet broke because:
> 
> $ uname -av
> Linux zealot 6.12.35+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.35-1 (2025-07-03) x86_64 GNU/Linux
> $ egrep . /sys/class/power_supply/*/uevent
> ...
> /sys/class/power_supply/BAT1/uevent:POWER_SUPPLY_STATUS=Discharging
> ...
> /sys/class/power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW=-484000
> ...
> 
> Full event output here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109342#15
> 
> 
> Whereas previously:
> 
> $ uname -av
> Linux zealot 6.12.33+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.33-1 (2025-06-19) x86_64 GNU/Linux
> $ egrep . /sys/class/power_supply/*/uevent
> ...
> /sys/class/power_supply/BAT1/uevent:POWER_SUPPLY_STATUS=Discharging
> ...
> /sys/class/power_supply/BAT1/uevent:POWER_SUPPLY_CURRENT_NOW=504000
> ...
> 
> Full event output here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1109342#10
> 
> Note that the previous value was positive, and the new value is
> negative.  In both cases the laptop was not charging.
> 
> The negative value makes semantic sense, but I wonder if this change
> was deliberate.  It seems like precisely the kind of bug-for-bug
> compatibility thing that Linux normally tries to retain.
> 
> In the meantime I will adjust my code to take abs(), since STATUS can
> be used to find out the sense of current flow.
> 
> Thanks for your attention.

I suspect this is a deliberate change maybe e8cd4a8d5b88 ("ACPI:
battery: negate current when discharging"), can you try with that
commit reverted?

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?

Regards,
Salvatore

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

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