Hrev51033 x86_gcc2 and later revisions - problem with the increased power consumption of the laptop battery

51033 revision and later have a problem with the increased power consumption of the laptop battery.
The increase in power consumption by 25 percent or more.
Compare with revision 51032 and earlier.

1 Like

Welcome to the Haiku shell.

~> listdev

device Serial bus controller (SMBus) [c|5|0]
vendor 8086: Intel Corporation
device 1e22: 7 Series/C216 Chipset Family SMBus Controller

device Mass storage controller (SATA controller, AHCI 1.0) [1|6|1]
vendor 8086: Intel Corporation
device 1e03: 7 Series Chipset Family 6-port SATA Controller [AHCI mode]

device Bridge (ISA bridge) [6|1|0]
vendor 8086: Intel Corporation
device 1e5d: HM75 Express Chipset LPC Controller

device Serial bus controller (USB controller, EHCI) [c|3|20]
vendor 8086: Intel Corporation
device 1e26: 7 Series/C216 Chipset Family USB Enhanced Host Controller #1

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 1e16: 7 Series/C216 Chipset Family PCI Express Root Port 4

device Network controller (Ethernet controller) [2|0|0]
vendor 10ec: Realtek Semiconductor Co., Ltd.
device 8168: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 1e14: 7 Series/C210 Series Chipset Family PCI Express Root Port 3

device Network controller [2|80|0]
vendor 8086: Intel Corporation
device 088e: Centrino Advanced-N 6235

device Bridge (PCI bridge, Normal decode) [6|4|0]
vendor 8086: Intel Corporation
device 1e10: 7 Series/C216 Chipset Family PCI Express Root Port 1

device Multimedia controller (Audio device) [4|3|0]
vendor 8086: Intel Corporation
device 1e20: 7 Series/C216 Chipset Family High Definition Audio Controller

device Serial bus controller (USB controller, EHCI) [c|3|20]
vendor 8086: Intel Corporation
device 1e2d: 7 Series/C216 Chipset Family USB Enhanced Host Controller #2

device Communication controller [7|80|0]
vendor 8086: Intel Corporation
device 1e3a: 7 Series/C216 Chipset Family MEI Controller #1

device Display controller (VGA compatible controller, VGA controller) [3|0|0]
vendor 8086: Intel Corporation
device 0166: 3rd Gen Core processor Graphics Controller

device Bridge (Host bridge) [6|0|0]
vendor 8086: Intel Corporation
device 0154: 3rd Gen Core processor DRAM Controller
~>

1 Like

https://cgit.haiku-os.org/haiku/commit/?id=19d8e4f73cff0862a80d4d7954a3e0c4da9e40b8

ipv4/6: fixed crossing link fields from different hash tables. hrev51033

Revert ?

https://dev.haiku-os.org/ticket/13433

It is very unlikely that this specific commit is related to power usage.

I did notice that my battery life seemed quite short this week-end, too, but I think the problem is more likely to be elsewhere. Maybe a problem with the build bot used to build each image, leading to different results? (we had this happen in the past already).

Is it possible to check to revert commit 51033?

Can you build locally with or without this commit? This would be the easiest way.

Maybe a problem with the build bot used to build each image, leading to different results?

Impossible, sorry …

Nothing is impossible!

Setup build environment:

git clone https://git.haiku-os.org/haiku
git clone https://git.haiku-os.org/buildtools
cd buildtools/jam
make; sudo make install
cd -

Build cross compiler

mkdir haiku/generated.x86_gcc2; cd haiku/generated.x86_gcc2
../configure -j2 --build-cross-tools x86_gcc2 ../../buildtools

Build os with hrev51033 reverted:

git revert 19d8e4f73cff0862a80d4d7954a3e0c4da9e40b8
jam -j2 -q @nightly-anyboot

boot haiku-anyboot.iso on your test machine and repeat the build above as needed for more testing.

(EDIT: The point to all of this is sometimes the best way to get a problem solved is to do some advanced troubleshooting to help the developers out. It’s also a great way to get experience.)

Build with 51033 revert on a third-party computer may not produce the desired result.

hrev51200 - work fine !

I am new to the community but you could try using a new Battery to see if the battery is self is the problem or not.