You are not logged in.
- Topics: Active | Unanswered
#1 2020-01-19 18:51:25
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Annoying "Timers" Causing Huge Battery Drain
Hey Arch,
I'll get right to the important info -
- I am dealing with extremely bad battery drain on my laptop which was made better by installing TLP and following ALL of the wiki on battery management and such so nothing to worry about their.
- My battery life on my Predator Helios 300 2019 gets about 5 hours when on Windows 10 and I should be able to get about 4 hours in Arch. However my battery is draining severely when no processes are opening and Powertop is showing that these two timers are taking a significant chunk of that. My battery drain is really bad to the point where I only have 1 hour and 51 minutes on full charge when idle. This powertop was taken at 28% battery. Can I get any help with this please as I am deseperate to do anything to continue using arch and move away from windows. Thanks a ton guys 
I will be happy to post any logs requested
The battery reports a discharge rate of 40.4 W
The power consumed was 0.00 J
The estimated remaining time is 0 hours, 25 minutes
Summary: 1858.4 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 11.0% CPU use
Power est. Usage Events/s Category Description
4.77 W 11.6 ms/s 1203.4 Timer hrtimer_wakeup
1.35 W 2.2 ms/s 340.2 Timer tick_sched_timer
443 mW 14.4 ms/s 106.5 Process [PID 19925] powertop
106 mW 2.0 ms/s 23.6 Process [PID 19880] kitty
79.3 mW 19.8 ms/s 12.3 Interrupt [9] acpi
76.5 mW 3.7 ms/s 17.9 kWork handle_update
69.6 mW 1.7 ms/s 17.0 Interrupt [7] sched(softirq)
59.8 mW 2.5 ms/s 14.1 Process [PID 988] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{596af6c5-c859-4042-91ed-21147dd7df41} -background none -noreset -dis
55.9 mW 61.1 µs/s 14.1 Interrupt [0] HI_SOFTIRQ
52.5 mW 246.3 µs/s 13.2 Process [PID 766] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid -m:NbfcService /opt/nbfc/NbfcService.exe
49.4 mW 22.1 ms/s 3.8 Process [PID 15558] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid -m:NbfcService /opt/nbfc/NbfcService.exe
48.6 mW 143.0 µs/s 12.3 Process [PID 11] [rcu_preempt]
43.1 mW 6.2 ms/s 8.5 Process [PID 18272] /usr/lib/firefox/firefox -contentproc -childID 53 -isForBrowser -prefsLen 7756 -prefMapSize 210026 -parentBuildID 2
37.9 mW 411.4 µs/s 9.4 Process [PID 18287] /usr/lib/firefox/firefox -contentproc -childID 53 -isForBrowser -prefsLen 7756 -prefMapSize 210026 -parentBuildID 2
37.5 mW 197.3 µs/s 9.4 Process [PID 19158] /usr/lib/firefox/firefox
36.9 mW 392.0 µs/s 8.5 Process [PID 1082] xcompmgr
29.9 mW 64.2 µs/s 7.5 kWork psi_avgs_work
26.8 mW 17.2 ms/s 0.00 Process [PID 99] [kworker/4:1]
24.0 mW 1.0 ms/s 5.7 Process [PID 17993] /usr/lib/firefox/firefox -contentproc -childID 51 -isForBrowser -prefsLen 7756 -prefMapSize 210026 -parentBuildID 2The battery reports a discharge rate of 42.8 W
The power consumed was 0.00 J
System baseline power is estimated at 7.30 W
Power est. Usage Device name
5.04 W 7.4% CPU misc
1.38 W 7.4% CPU core
875 mW 7.4% DRAM
0 mW 100.0% Radio device: iwlwifi
0 mW 40.0% Display backlight
0 mW 0.0% USB device: xHCI Host Controller
0 mW 0.0% USB device: HD User Facing (Chicony Electronics Co.,Ltd.)
0 mW 0.0% USB device: xHCI Host Controller
0 mW 0.0% USB device: xHCI Host Controller
0 mW 0.0% USB device: xHCI Host Controller
0 mW 0.0% Audio codec hwC0D0: Realtek
0 mW 0.0 pkts/s Network interface: wlp0s20f3 (iwlwifi)
0 mW 0.0% Radio device: acer-wmi
100.0% PCI Device: NVIDIA Corporation Device 1aec
100.0% PCI Device: Intel Corporation Cannon Lake PCH SPI Controller
100.0% PCI Device: Intel Corporation Wireless-AC 9560 [Jefferson Peak]
100.0% PCI Device: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem
100.0% PCI Device: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16)
100.0% PCI Device: Intel Corporation Device a30d
100.0% PCI Device: Intel Corporation Cannon Lake PCH Serial IO I2C Controller #1Last edited by NotKudo (2020-01-20 03:29:19)
Offline
#2 2020-01-20 02:16:01
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
Bump - Just making sure this doesn't get lost in the void
Offline
#3 2020-01-20 03:09:11
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: Annoying "Timers" Causing Huge Battery Drain
READ the Rules you agreed to when you signed up.
Don't bump: https://wiki.archlinux.org/index.php/Co … ct#Bumping
Don't put redundant cruft in your thread title like "Help Loved": https://wiki.archlinux.org/index.php/Co … ow_to_post
And don't crosspost: https://wiki.archlinux.org/index.php/Co … ss-posting
Offline
#4 2020-01-20 03:29:43
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
READ the Rules you agreed to when you signed up.
Don't bump: https://wiki.archlinux.org/index.php/Co … ct#Bumping
Don't put redundant cruft in your thread title like "Help Loved": https://wiki.archlinux.org/index.php/Co … ow_to_post
And don't crosspost: https://wiki.archlinux.org/index.php/Co … ss-posting
Sorry - I edited out my mistakes. Thanks for your help
Offline
#5 2020-01-20 03:51:37
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: Annoying "Timers" Causing Huge Battery Drain
Is this a hybrid graphics machine, and have you configured it accordingly?
Offline
#6 2020-01-20 04:24:39
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
Is this a hybrid graphics machine, and have you configured it accordingly?
Yes BBSwitch and Bumblebee are set up to the best of my ability after following the wiki and my dedicated GPU is not being used to save power
Last edited by NotKudo (2020-01-20 04:29:48)
Offline
#7 2020-01-20 04:28:59
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: Annoying "Timers" Causing Huge Battery Drain
jasonwryan wrote:Is this a hybrid graphics machine, and have you configured it accordingly?
Yes BBSwitch and Bumblebee are setup to the best of my ability after following the wiki
#Using Bumblebee - provides Windows-like functionality by allowing to run selected applications with NVIDIA graphics while using Intel graphics for everything else. Has significant performance issues.
Offline
#8 2020-01-20 04:31:40
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
NotKudo wrote:jasonwryan wrote:Is this a hybrid graphics machine, and have you configured it accordingly?
Yes BBSwitch and Bumblebee are setup to the best of my ability after following the wiki
wiki wrote:#Using Bumblebee - provides Windows-like functionality by allowing to run selected applications with NVIDIA graphics while using Intel graphics for everything else. Has significant performance issues.
Although I'm sure Bumblebee isn't causing any issues - I will head over and remove it from my system and report back on PowerTop. Thank you for your further help - You don't understand how much I appreciate it
I will also go through the Hybrid Graphics page again just to make sure nothing was missed
Last edited by NotKudo (2020-01-20 04:34:54)
Offline
#9 2020-01-20 04:39:01
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
NotKudo wrote:jasonwryan wrote:Is this a hybrid graphics machine, and have you configured it accordingly?
Yes BBSwitch and Bumblebee are setup to the best of my ability after following the wiki
wiki wrote:#Using Bumblebee - provides Windows-like functionality by allowing to run selected applications with NVIDIA graphics while using Intel graphics for everything else. Has significant performance issues.
So I believe this was the reason I installed Bbswitch in the first place, I was attempting to use only my intel integrated graphics when using linux to save battery - here in the arch wiki it says bbswitch is safer to use to accomplish this.
Fully Power Down Discrete GPU
You may want to turn off the high-performance graphics processor to save battery power.
Using bbswitchWith a NVidia GPU, this can be more safely done using bbswitch, which consists of a kernel package that automatically issues the correct ACPI calls to disable the discrete GPU when not needed, or automatically at boot. "
(Fully Power Down Discrete GPU Section)
Should I instead use the other method of powering off the GPU using ascpi calls?
Offline
#10 2020-01-20 04:43:59
- jasonwryan
- Anarchist
- From: .nz
- Registered: 2009-05-09
- Posts: 30,424
- Website
Re: Annoying "Timers" Causing Huge Battery Drain
To establish a baseline with powertop, I would disable the nvidia card completely: https://wiki.archlinux.org/index.php/NV … phics_only
Offline
#11 2020-01-20 04:47:25
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
To establish a baseline with powertop, I would disable the nvidia card completely: https://wiki.archlinux.org/index.php/NV … phics_only
Understood - I can't disable the card completely as I need to use it with other OS's, however I will disable it completely using the acpi call method.
Offline
#12 2020-01-20 05:10:26
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
To establish a baseline with powertop, I would disable the nvidia card completely: https://wiki.archlinux.org/index.php/NV … phics_only
just a quick update - I ran into some issues while using acpi_call in the wiki tutorial tutorial. After running the command to power off the GPU my system just freezes and I have to restart to use it again - I suspect this is because my display is now using my discrete GPU to power it. Their is a tip at the bottom stating this and I think it might concern me but I need to be sure as it may cause my system to be unbootable.
After X server initialization
On some systems, turning off the discrete GPU before the X server is initialized may hang the system. In such cases, it may be better to disable the GPU after X server initialization, which is possible with some display managers. In LightDM, for instance, the display-setup-script seat configuration parameter could be used to execute a script as root that disables the GPU.
EDIT: ADDIOTINALLY I have major information that my help out in solving this - I just opened my powertop just to check everything out (Have not done any tweaks yet that I mentioned) My battery life at 65% reported 3 hours which is about what I should be getting.
The battery reports a discharge rate of 13.6 W
The power consumed was 0.00 J
The estimated remaining time is 2 hours, 46 minutes
Summary: 4696.2 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 44.3% CPU use
Power est. Usage Events/s Category Description
6.69 W 84.3 ms/s 1510.4 Process [PID 1182] /usr/lib/firefox/firefox
5.10 W 11.9 ms/s 1285.5 Interrupt [17] idma64.1
1.79 W 3.8 ms/s 452.5 Timer tick_sched_timer
1.05 W 17.6 ms/s 259.0 Process [PID 1194] /usr/lib/firefox/firefox
922 mW 62.1 ms/s 208.7 Process [PID 2296] /usr/lib/firefox/firefox -contentproc -childID 12 -isForBrowser -
794 mW 11.5 ms/s 181.2 Process [PID 471] [irq/127-SYNA7DB]
613 mW 10.9 ms/s 150.8 Process [PID 1243] /usr/lib/firefox/firefox -contentproc -parentBuildID 202001081319
375 mW 31.2 ms/s 82.5 Process [PID 3292] powertop
304 mW 18.9 ms/s 68.3 Process [PID 1235] /usr/lib/firefox/firefox -contentproc -parentBuildID 202001081319
281 mW 59.8 ms/s 47.4 Process [PID 869] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{110b076a-d447-48f
252 mW 32.1 ms/s 51.2 Interrupt [14] INT3450:00
228 mW 3.5 ms/s 56.0 Process [PID 1048] unclutter
175 mW 4.1 ms/s 42.7 Interrupt [7] sched(softirq)
149 mW 4.3 ms/s 36.1 Process [PID 1268] /usr/lib/firefox/firefox
113 mW 156.2 µs/s 28.5 Interrupt [0] HI_SOFTIRQ
107 mW 1.8 ms/s 23.7 Process [PID 3281] kitty
105 mW 348.2 µs/s 26.6 Process [PID 11] [rcu_preempt]
83.9 mW 0.9 ms/s 20.9 Process [PID 1457] /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -p
79.8 mW 1.3 ms/s 19.0 Process [PID 1043] xcompmgr
71.9 mW 2.8 ms/s 17.1 kWork handle_update
62.0 mW 1.3 ms/s 15.2 Interrupt [143] i915
43.8 mW 1.7 ms/s 10.4 Process [PID 1441] /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -p
41.1 mW 26.4 ms/s 0.00 Interrupt [17] i2c_designware.1
30.1 mW 2.5 ms/s 6.6 Process [PID 2311] /usr/lib/firefox/firefox -contentproc -childID 12 -isForBrowser -
30.0 mW 41.4 µs/s 7.6 kWork psi_avgs_work
24.3 mW 1.2 ms/s 5.7 Process [PID 1573] /usr/lib/firefox/firefox -contentproc -childID 6 -isForBrowser -p
24.3 mW 1.2 ms/s 5.7 Process [PID 1374] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
22.5 mW 11.3 µs/s 5.7 kWork free_work
16.1 mW 7.9 ms/s 0.9 Process [PID 3297] i3blocks
15.9 mW 7.8 ms/s 0.9 Process [PID 3298] i3blocks
15.3 mW 169.0 µs/s 3.8 Process [PID 1389] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
15.2 mW 135.4 µs/s 3.8 Process [PID 1588] /usr/lib/firefox/firefox -contentproc -childID 6 -isForBrowser -p
14.2 mW 1.9 ms/s 2.8 Process [PID 3307] sh
14.1 mW 1.8 ms/s 2.8 Process [PID 3313] sh
13.9 mW 1.7 ms/s 2.8 Process [PID 3310] sh
11.7 mW 5.1 ms/s 0.9 kWork delayed_fput
8.66 mW 0.7 ms/s 1.9 Process [PID 3299] sh
8.40 mW 3.0 ms/s 0.9 Process [PID 3304] sh
8.38 mW 568.5 µs/s 1.9 Process [PID 3300] sh
8.26 mW 489.0 µs/s 1.9 Process [PID 3312] sh
8.07 mW 370.0 µs/s 1.9 Process [PID 3305] sh
8.07 mW 366.5 µs/s 1.9 Process [PID 3301] sh
8.03 mW 344.2 µs/s 1.9 Process [PID 3308] sh
7.99 mW 317.9 µs/s 1.9 Process [PID 3311] sh
7.89 mW 251.3 µs/s 1.9 Process [PID 1771] /usr/lib/firefox/firefox -contentproc -childID 10 -isForBrowser -
7.78 mW 183.7 µs/s 1.9 Process [PID 3309] sh
7.73 mW 2.6 ms/s 0.9 Process [PID 3303] sh
7.71 mW 136.5 µs/s 1.9 Process [PID 3303] grep
7.70 mW 130.5 µs/s 1.9 Process [PID 3304] awk
7.63 mW 87.1 µs/s 1.9 Process [PID 3214] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid
7.60 mW 67.0 µs/s 1.9 Process [PID 1785] /usr/lib/firefox/firefox -contentproc -childID 10 -isForBrowser -hwever this appears to be only temporary until the process (tick_sched_timer) comes up and decreases it again to about 1 hour which is the normal amount from before and my fans start spinning fast. below is the results after the process comes back. For some reason when the tick sched process pops up my fans start spinning and the battery drops down - however when it dissapears my battery increases and my fans quite down.
The battery reports a discharge rate of 41.1 W
The power consumed was 438 J
The estimated remaining time is 0 hours, 51 minutes
Summary: 2244.4 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 79.7% CPU use
Power est. Usage Events/s Category Description
2.04 W 5.3 ms/s 515.3 Timer tick_sched_timer
1.14 W 5.2 ms/s 277.8 Process [PID 1194] /usr/lib/firefox/firefox
1.09 W 360.6 ms/s 127.2 Process [PID 2296] /usr/lib/firefox/firefox -contentproc -childID 12 -isForBrowser -
650 mW 2.2 ms/s 154.6 Process [PID 1236] /usr/lib/firefox/firefox
549 mW 279.7 ms/s 28.4 Process [PID 2314] /usr/lib/firefox/firefox -contentproc -childID 12 -isForBrowser -
526 mW 621.5 µs/s 132.9 Interrupt [17] idma64.1
481 mW 3.3 ms/s 120.4 Process [PID 1243] /usr/lib/firefox/firefox -contentproc -parentBuildID 202001081319
453 mW 4.9 ms/s 104.1 Process [PID 471] [irq/127-SYNA7DB]
404 mW 5.2 ms/s 100.4 Process [PID 2299] /usr/lib/firefox/firefox -contentproc -childID 12 -isForBrowser -
374 mW 5.1 ms/s 80.3 Process [PID 1182] /usr/lib/firefox/firefox
355 mW 515.7 µs/s 89.6 Interrupt [0] HI_SOFTIRQ
285 mW 7.3 ms/s 67.1 Process [PID 869] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{110b076a-d447-48f
276 mW 36.7 ms/s 50.0 Process [PID 1244] /usr/lib/firefox/firefox -contentproc -parentBuildID 202001081319
208 mW 46.9 ms/s 34.2 Interrupt [14] INT3450:00
179 mW 2.1 ms/s 44.5 Process [PID 1268] /usr/lib/firefox/firefox
175 mW 1.0 ms/s 40.7 Process [PID 1043] xcompmgr
149 mW 1.3 ms/s 37.3 Process [PID 1232] /usr/lib/firefox/firefox
145 mW 4.0 ms/s 35.1 Interrupt [7] sched(softirq)
145 mW 1.1 ms/s 32.3 Process [PID 3281] kitty
144 mW 3.0 ms/s 35.2 Interrupt [143] i915
120 mW 156.1 µs/s 30.2 Process [PID 11] [rcu_preempt]
69.4 mW 466.0 µs/s 17.4 Timer hrtimer_wakeup
68.2 mW 1.7 ms/s 16.6 Process [PID 1441] /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -p
46.1 mW 0.8 ms/s 11.4 Interrupt [9] RCU(softirq)
44.1 mW 356.2 µs/s 11.0 Process [PID 1446] /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -p
40.0 mW 290.5 µs/s 10.0 Process [PID 1048] unclutter
28.3 mW 382.2 µs/s 7.0 Process [PID 1374] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
16.6 mW 200.1 µs/s 4.0 Process [PID 3578] /usr/lib/firefox/firefox -contentproc -childID 14 -isForBrowser -
16.2 mW 14.8 µs/s 4.1 kWork console_callback
14.1 mW 58.4 µs/s 3.5 Process [PID 1195] /usr/lib/firefox/firefox
12.0 mW 20.6 µs/s 3.0 kWork psi_avgs_work
11.6 mW 6.4 ms/s 0.4 Interrupt [9] acpi
9.67 mW 1.0 ms/s 2.0 Process [PID 3292] powertop
6.86 mW 104.9 µs/s 1.7 Process [PID 1235] /usr/lib/firefox/firefox -contentproc -parentBuildID 202001081319
5.56 mW 31.4 µs/s 1.4 Process [PID 1389] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
4.74 mW 8.6 µs/s 1.2 Timer watchdog_timer_fn
4.11 mW 114.2 µs/s 1.0 Process [PID 9] [ksoftirqd/0]
3.76 mW 12.4 µs/s 0.9 Process [PID 3593] /usr/lib/firefox/firefox -contentproc -childID 14 -isForBrowser -
3.24 mW 2.1 ms/s 0.00 Interrupt [17] i2c_designware.1
3.16 mW 132.2 µs/s 0.7 kWork __i915_gem_free_work
2.87 mW 1.2 ms/s 0.25 Interrupt [1] timer(softirq)
2.81 mW 412.1 µs/s 0.5 kWork delayed_fput
2.70 mW 26.2 µs/s 0.6 Process [PID 1021] i3 -a --restart /run/user/1000/i3/restart-state.1021
2.58 mW 12.6 µs/s 0.6 Interrupt [4] block(softirq)
2.31 mW 1.1 ms/s 0.15 Process [PID 3314] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid
2.23 mW 1.1 ms/s 0.15 Process [PID 800] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid
1.97 mW 0.5 µs/s 0.5 kWork flush_backlog
1.66 mW 53.3 µs/s 0.4 kWork handle_update
1.62 mW 27.4 µs/s 0.4 kWork pci_pme_list_scan
1.59 mW 12.4 µs/s 0.4 kWork vmstat_shepherd
1.59 mW 7.2 µs/s 0.4 kWork hangcheck_elapse Last edited by NotKudo (2020-01-20 05:19:46)
Offline
#13 2020-01-20 08:47:52
- V1del
- Forum Moderator
- Registered: 2012-10-16
- Posts: 21,659
Re: Annoying "Timers" Causing Huge Battery Drain
@Jason If bbswitch is correctly configured and bumblebee/the discrete GPU not actively used the card will be properly disabled.
@NotKudo
I remember reading something about unstable/broken HPET timers on Coffee Lakes and that they got disabled in recent kernels, make sure you are using an up to date kernel. You also might want to post a complete dmesg during the issue.
Last edited by V1del (2020-01-20 08:48:06)
Online
#14 2020-01-20 11:56:50
- Lone_Wolf
- Member
- From: Netherlands, Europe
- Registered: 2005-10-04
- Posts: 11,911
Re: Annoying "Timers" Causing Huge Battery Drain
52.5 mW 246.3 µs/s 13.2 Process [PID 766] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid -m:NbfcService /opt/nbfc/NbfcService.exeYou appear to be using https://wiki.archlinux.org/index.php/Fa … ntrol#NBFC
Which profile are you using for it and does disabling it make a difference ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
#15 2020-01-20 15:41:59
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
52.5 mW 246.3 µs/s 13.2 Process [PID 766] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid -m:NbfcService /opt/nbfc/NbfcService.exeYou appear to be using https://wiki.archlinux.org/index.php/Fa … ntrol#NBFC
Which profile are you using for it and does disabling it make a difference ?
Yes I am using that, I am using a profile that was recommended similar to my laptop model (Predator 2018) as my 2019 model was not their as a fan control profile and they we're both simmilar. Disabling Fan Speed Control didn't really do anything but here is the updated powertop at 20% battery showing about 4 hours of battery at max . tick_sched_timer is popping up at random times and lowering it by a couple minutes but I think I managed to attain my battery up to 4 hours. However I still would love to do something about those three pesky proceses (idma64 - I think is caused by something CPU related)
The battery reports a discharge rate of 14.4 W
The power consumed was 270 J
The estimated remaining time is 0 hours, 46 minutes
Summary: 2070.5 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 46.3% CPU use
Power est. Usage Events/s Category Description
1.61 W 5.9 ms/s 404.4 Timer tick_sched_timer
4.96 W 11.5 ms/s 1250.9 Timer hrtimer_wakeup
4.67 W 9.0 ms/s 1177.7 Interrupt [17] idma64.1
1.80 W 2.7 ms/s 454.3 Timer tick_sched_timer
618 mW 130.3 ms/s 105.1 Process [PID 7039] /usr/lib/firefox/firefox -contentproc -childID 7 -isForBrowser -p
481 mW 1.1 ms/s 121.4 Interrupt [17] idma64.1
466 mW 55.9 ms/s 95.9 Process [PID 4048] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
338 mW 5.2 ms/s 83.4 Process [PID 3704] /usr/lib/firefox/firefox -contentproc -parentBuildID 202001081319
311 mW 20.9 ms/s 53.6 Process [PID 3689] /usr/lib/firefox/firefox -contentproc -parentBuildID 202001081319
262 mW 4.3 ms/s 54.2 Process [PID 7042] /usr/lib/firefox/firefox -contentproc -childID 7 -isForBrowser -p
256 mW 17.5 ms/s 57.8 Process [PID 1022] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{d0151d9a-c2cd-44
215 mW 2.9 ms/s 49.0 Process [PID 468] [irq/127-SYNA7DB]
204 mW 532.7 µs/s 51.4 Interrupt [0] HI_SOFTIRQ
197 mW 42.8 ms/s 33.0 Interrupt [14] INT3450:00
191 mW 4.4 ms/s 46.6 Process [PID 3764] /usr/lib/firefox/firefox
189 mW 5.7 ms/s 45.7 Interrupt [7] sched(softirq)
135 mW 3.9 ms/s 32.7 Interrupt [143] i915
121 mW 1.6 ms/s 28.6 Process [PID 2319] xcompmgr
87.9 mW 5.4 ms/s 20.1 Process [PID 6967] /usr/lib/firefox/firefox -contentproc -childID 6 -isForBrowser -p
71.8 mW 10.1 ms/s 13.2 Process [PID 7368] /usr/lib/firefox/firefox -contentproc -childID 8 -isForBrowser -p
60.6 mW 607.6 µs/s 15.1 Timer hrtimer_wakeup
49.1 mW 169.1 µs/s 12.4 Process [PID 11] [rcu_preempt]
38.0 mW 232.8 µs/s 9.5 Process [PID 489] [irq/131-iwlwifi]
34.4 mW 694.5 µs/s 8.4 Process [PID 3573] /usr/lib/firefox/firefox
34.2 mW 481.7 µs/s 8.3 Process [PID 2288] i3
30.5 mW 415.1 µs/s 7.0 Process [PID 7228] kitty
27.8 mW 616.3 µs/s 6.8 Process [PID 2324] unclutter
25.3 mW 2.9 ms/s 5.3 Process [PID 3575] /usr/lib/firefox/firefox
25.2 mW 215.2 µs/s 6.3 Process [PID 486] [irq/128-iwlwifi]
17.5 mW 310.3 µs/s 4.3 Process [PID 4072] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
13.8 mW 1.7 ms/s 2.8 Process [PID 7273] powertop
13.2 mW 42.1 µs/s 3.3 kWork psi_avgs_work
13.0 mW 0.8 ms/s 3.0 Interrupt [9] RCU(softirq)
11.4 mW 2.7 ms/s 1.8 Process [PID 7361] FontLoader
8.66 mW 144.8 µs/s 2.1 Interrupt [4] block(softirq)
7.55 mW 186.4 µs/s 1.8 Process [PID 3856] /usr/lib/firefox/firefox -contentproc -childID 1 -isForBrowser -p
6.87 mW 382.9 µs/s 1.6 Process [PID 4762] /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -p
6.36 mW 180.2 µs/s 1.5 Process [PID 4775] /usr/lib/firefox/firefox -contentproc -childID 4 -isForBrowser -p
6.30 mW 18.6 µs/s 1.6 Timer watchdog_timer_fn
6.30 mW 13.8 µs/s 1.6 kWork blk_mq_requeue_work
5.19 mW 58.5 µs/s 1.3 Process [PID 488] [irq/130-iwlwifi]
5.03 mW 82.1 µs/s 1.2 Process [PID 490] [irq/132-iwlwifi]
4.91 mW 132.4 µs/s 1.2 Process [PID 7362] StreamTrans #20
4.82 mW 71.6 µs/s 1.2 Process [PID 2373] xcape -e Super_L Escape
4.75 mW 1.8 ms/s 0.5 kWork delayed_fput
4.67 mW 68.7 µs/s 1.1 Process [PID 2321] dunst
4.44 mW 2.8 ms/s 0.00 Interrupt [17] i2c_designware.1
4.44 mW 330.9 µs/s 1.0 Process [PID 3845] /usr/lib/firefox/firefox -contentproc -childID 1 -isForBrowser -p
4.36 mW 28.7 µs/s 1.1 Process [PID 763] /usr/lib/systemd/systemd-logind
4.32 mW 5.6 µs/s 1.1 kWork console_callback
4.26 mW 89.5 µs/s 1.0 Process [PID 7364] StreamTrans #22
<ESC> Exit | <TAB> / <Shift + TAB> Navigate | Last edited by NotKudo (2020-01-20 15:46:22)
Offline
#16 2020-01-20 15:45:02
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
@Jason If bbswitch is correctly configured and bumblebee/the discrete GPU not actively used the card will be properly disabled.
@NotKudo
I remember reading something about unstable/broken HPET timers on Coffee Lakes and that they got disabled in recent kernels, make sure you are using an up to date kernel. You also might want to post a complete dmesg during the issue.
Thanks so much for your help and I remember reading that as well which makes me assume that tick sched timer is related to the CPU. However, I am using kernel (Kernel: 5.4.13-arch1-1 ) which I believe is the newest one. Also I was able to compeltely disable the GPU using acpi so that is all fine.
Last edited by NotKudo (2020-01-20 15:45:28)
Offline
#17 2020-01-20 18:48:03
- Head_on_a_Stick
- Member
- From: London
- Registered: 2014-02-20
- Posts: 7,732
- Website
Re: Annoying "Timers" Causing Huge Battery Drain
Does powertop's --auto-tune option help at all? And have you tried the LTS kernel?
This (very old, marked solved) bug report suggests that disabling SMT might work. Bit of a stab in the dark though.
Offline
#18 2020-01-20 20:33:18
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
Does powertop's --auto-tune option help at all? And have you tried the LTS kernel?
This (very old, marked solved) bug report suggests that disabling SMT might work. Bit of a stab in the dark though.
I always have the auto tune option run at start up although it is finicky sometimes but it does usually work - I have not tried the LTS kernel ye, although I think that might be a good option to try. Should I do it?
Also how would go upon disabling SMT?
Also the battery drain comes back for a few minutes when booting my computer but then dissapears normally although I still have these processes but for the most part I do believe the battery drain is mostly fixed to the point where I'm fine with getting about 4 hours - however I think the extra hour is gone due to the processes that are still their and I would like to know what causes them and how to get rid of them
The battery reports a discharge rate of 14.4 W
The power consumed was 0.00 J
The estimated remaining time is 4 hours, 2 minutes
Summary: 408.1 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 3.4% CPU use
Power est. Usage Events/s Category Description
412 mW 12.6 ms/s 99.4 Process [PID 2568] powertop
345 mW 0.7 ms/s 87.1 Interrupt [17] idma64.1
184 mW 320.0 µs/s 46.4 Timer tick_sched_timer
125 mW 1.5 ms/s 27.5 Process [PID 2538] kitty
77.0 mW 3.8 ms/s 18.0 kWork handle_update
67.4 mW 43.0 µs/s 17.0 Interrupt [0] HI_SOFTIRQ
58.5 mW 0.9 ms/s 13.3 Process [PID 473] [irq/127-SYNA7DB]
52.2 mW 2.3 ms/s 12.3 Process [PID 994] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{d70c142e-e8ab-4fcf-821b-4795e9cd6991} -background none -noreset -dis
45.0 mW 78.5 µs/s 11.4 kWork psi_avgs_workHowever the battery drain comes back for most of the time when these three processes come up so I really can't say anything is fixed
The battery reports a discharge rate of 38.3 W
The power consumed was 0.00 J
The estimated remaining time is 1 hours, 2 minutes
Summary: 4176.1 wakeups/second, 0.0 GPU ops/seconds, 0.0 VFS ops/sec and 17.7% CPU use
Power est. Usage Events/s Category Description
7.17 W 19.4 ms/s 1808.6 Interrupt [17] idma64.1
5.42 W 10.8 ms/s 1366.9 Timer hrtimer_wakeup
1.47 W 2.3 ms/s 370.0 Timer tick_sched_timer
928 mW 10.1 ms/s 213.1 Process [PID 451] [irq/126-SYNA7DB]
530 mW 6.6 ms/s 121.1 Process [PID 3284] kitty
314 mW 14.6 ms/s 73.6 Process [PID 3458] powertop
313 mW 36.5 ms/s 64.9 Interrupt [14] INT3450:00
94.0 mW 1.4 ms/s 23.2 Process [PID 1021] unclutter
53.9 mW 34.5 ms/s 0.00 Interrupt [17] i2c_designware.1
53.6 mW 45.5 µs/s 13.6 Interrupt [0] HI_SOFTIRQ
52.0 mW 1.5 ms/s 12.6 kWork handle_update
51.8 mW 11.1 ms/s 8.7 Process [PID 941] /usr/lib/Xorg -nolisten tcp -auth /var/run/sddm/{39ac5622-1eee-4bf
40.1 mW 1.2 ms/s 9.7 Interrupt [7] sched(softirq)
38.8 mW 328.8 µs/s 9.7 Process [PID 2018] /usr/lib/firefox/firefox
37.8 mW 315.5 µs/s 8.7 Process [PID 1016] xcompmgr
34.6 mW 82.6 µs/s 8.7 Process [PID 11] [rcu_preempt]
30.7 mW 58.4 µs/s 7.7 kWork psi_avgs_work
26.6 mW 17.1 ms/s 0.00 Process [PID 391] [kworker/5:2]
23.3 mW 239.7 µs/s 5.8 Interrupt [137] i915
23.3 mW 236.8 µs/s 5.8 Process [PID 2782] /usr/lib/firefox/firefox -contentproc -childID 7 -isForBrowser -p
23.3 mW 187.2 µs/s 5.8 Process [PID 3233] /usr/lib/firefox/firefox -contentproc -childID 13 -isForBrowser -
15.5 mW 130.9 µs/s 3.9 Process [PID 2208] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
15.1 mW 2.3 ms/s 2.9 Process [PID 2005] /usr/lib/firefox/firefox
12.6 mW 699.6 µs/s 2.9 Process [PID 2767] /usr/lib/firefox/firefox -contentproc -childID 7 -isForBrowser -p
11.7 mW 129.0 µs/s 2.9 Process [PID 457] [irq/132-iwlwifi]
8.33 mW 433.4 µs/s 1.9 Process [PID 2110] /usr/lib/firefox/firefox -contentproc -childID 1 -isForBrowser -p
7.82 mW 105.9 µs/s 1.9 Process [PID 2126] /usr/lib/firefox/firefox -contentproc -childID 1 -isForBrowser -p
7.81 mW 102.4 µs/s 1.9 Process [PID 452] [irq/127-iwlwifi]
7.78 mW 79.4 µs/s 1.9 Process [PID 3342] /usr/bin/mono /usr/lib/mono/4.5/mono-service.exe -l:/run/nbfc.pid
7.69 mW 24.6 µs/s 1.9 Timer timerfd_tmrproc
7.68 mW 17.1 µs/s 1.9 Process [PID 3308] kitty
4.53 mW 452.5 µs/s 1.0 Process [PID 2193] /usr/lib/firefox/firefox -contentproc -childID 3 -isForBrowser -p
4.06 mW 150.6 µs/s 1.0 Process [PID 347] /usr/lib/systemd/systemd-journald
3.97 mW 93.0 µs/s 1.0 Process [PID 28] [ksoftirqd/2]
3.90 mW 50.2 µs/s 1.0 Process [PID 579] /usr/bin/NetworkManager --no-daemon
3.90 mW 45.2 µs/s 1.0 Process [PID 458] [irq/133-iwlwifi]
3.88 mW 34.1 µs/s 1.0 Process [PID 2043] /usr/lib/firefox/firefox
3.87 mW 28.1 µs/s 1.0 kWork pci_pme_list_scan
3.86 mW 22.4 µs/s 1.0 Process [PID 3224] /usr/lib/firefox/firefox -contentproc -childID 13 -isForBrowser -
3.85 mW 12.7 µs/s 1.0 Process [PID 3421] /usr/lib/firefox/firefox -contentproc -childID 14 -isForBrowser -
3.85 mW 12.7 µs/s 1.0 kWork vmstat_shepherd
3.84 mW 11.5 µs/s 1.0 Process [PID 2773] /usr/lib/firefox/firefox -contentproc -childID 7 -isForBrowser -p
3.84 mW 6.4 µs/s 1.0 kWork iwl_mvm_tcm_work
3.83 mW 4.4 µs/s 1.0 kWork flush_to_ldisc
3.83 mW 3.1 µs/s 1.0 Timer sched_rt_period_timer
3.06 mW 2.0 ms/s 0.00 Interrupt [17] snd_hda_intel:card1
1.17 mW 0.8 ms/s 0.00 Interrupt [1] timer(softirq)
601 µW 385.2 µs/s 0.00 Process [PID 3219] /usr/lib/firefox/firefox -contentproc -childID 13 -isForBrowser -
307 µW 196.7 µs/s 0.00 Process [PID 462] [kworker/2:3]
223 µW 142.7 µs/s 0.00 Interrupt [9] RCU(softirq)
144 µW 92.6 µs/s 0.00 Timer delayed_work_timer_fnLast edited by NotKudo (2020-01-20 21:14:46)
Offline
#19 2020-01-20 20:48:38
- Head_on_a_Stick
- Member
- From: London
- Registered: 2014-02-20
- Posts: 7,732
- Website
Re: Annoying "Timers" Causing Huge Battery Drain
I have not tried the LTS kernel ye, although I think that might be a good option to try. Should I do it?
Well, yes. It won't hurt to try.
Also how would go upon disabling SMT?
Either use the option in your firmware ("BIOS"), if there is such a thing, or add the nosmt kernel command line parameter.
Or if you don't like rebooting I use this script to disable SMT at runtime:
empty@E485:~ $ cat `which nosmt`
#!/bin/sh
echo on > /sys/devices/system/cpu/smt/control
for n in 1 3 5 7
do echo 0 > /sys/devices/system/cpu/cpu${n}/online
done
echo off > /sys/devices/system/cpu/smt/control
empty@E485:~ $My processor has 8 threads, mutatis mutandis.
Offline
#20 2020-01-20 21:22:51
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
NotKudo wrote:I have not tried the LTS kernel ye, although I think that might be a good option to try. Should I do it?
Well, yes. It won't hurt to try.
NotKudo wrote:Also how would go upon disabling SMT?
Either use the option in your firmware ("BIOS"), if there is such a thing, or add the nosmt kernel command line parameter.
Or if you don't like rebooting I use this script to disable SMT at runtime:
empty@E485:~ $ cat `which nosmt` #!/bin/sh echo on > /sys/devices/system/cpu/smt/control for n in 1 3 5 7 do echo 0 > /sys/devices/system/cpu/cpu${n}/online done echo off > /sys/devices/system/cpu/smt/control empty@E485:~ $My processor has 8 threads, mutatis mutandis.
Just disabled hyper threading with the command line parameter and it appears to have no effect - timer and interrupt processes still draining battery life. I will try switching to the LTS kernel now
EDIT: LTS kernel has no effect as well 
Last edited by NotKudo (2020-01-20 21:26:54)
Offline
#21 2020-01-21 18:15:20
- NotKudo
- Member
- Registered: 2020-01-19
- Posts: 14
Re: Annoying "Timers" Causing Huge Battery Drain
I'm thinking of buying a cheap Thinkpad to exclusively use Arch on, is that a bad idea? I think thinkpads have much better compatibility for simply typing that gaming hybrid laptops.
Offline