Package id 0: +44.0°C (high = +100.0°C, crit = +100.0°C)
Core 0: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 4: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 8: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 12: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 16: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 17: +42.0°C (high = +100.0°C, crit = +100.0°C)
Core 18: +41.0°C (high = +100.0°C, crit = +100.0°C)
Core 19: +41.0°C (high = +100.0°C, crit = +100.0°C)
Core 20: +40.0°C (high = +100.0°C, crit = +100.0°C)
Core 21: +40.0°C (high = +100.0°C, crit = +100.0°C)
Core 22: +40.0°C (high = +100.0°C, crit = +100.0°C)
Core 23: +40.0°C (high = +100.0°C, crit = +100.0°C)
This was after approximately 45 minutes of hibernation
I’ve figured out the most reliable triggers are certain web video players and complex web graphics (e.g. flightradar24). These are much more problematic then games like Factorio (for example)
What confuses me most is that once I’ve closed every intense website my computer still refuses to get below 55 degress unless I turn it off
Maybe you can post your top command without cutting of the running commands?
Depending on what the system does in background it may not eat a lot of resources but keep the CPU warm.
1 Like
hi @Samuel_Dyck ,
can we also try to check sleep/suspend logs?
sudo journalctl -t systemd-sleep
1 Like
It’s currently behaving so I’ll post those once it acts up again
Mar 08 15:55:17 systemd-sleep[3733]: Entering sleep state 'suspend'...
Mar 08 15:57:25 systemd-sleep[3733]: System returned from sleep state.
Mar 08 16:53:45 systemd-sleep[8790]: Entering sleep state 'suspend'...
Mar 08 16:59:24 systemd-sleep[8790]: System returned from sleep state.
Mar 08 16:59:55 systemd-sleep[9044]: Entering sleep state 'suspend'...
-- Boot dd087ab4048e4acc9c55d1a202f3271b --
Mar 08 18:51:13 systemd-sleep[53119]: Entering sleep state 'suspend'...
Mar 08 19:44:43 systemd-sleep[53119]: System returned from sleep state.
Mar 08 21:26:47 systemd-sleep[54966]: Entering sleep state 'suspend'...
Mar 10 17:16:57 systemd-sleep[54966]: System returned from sleep state.
Mar 10 17:36:17 systemd-sleep[56200]: Entering sleep state 'suspend'...
Mar 10 17:57:37 systemd-sleep[56200]: System returned from sleep state.
Mar 10 18:32:16 systemd-sleep[56837]: Entering sleep state 'suspend'...
Mar 10 19:05:45 systemd-sleep[56837]: System returned from sleep state.
Mar 10 19:06:14 systemd-sleep[57021]: Entering sleep state 'suspend'...
Mar 10 19:19:39 systemd-sleep[57021]: System returned from sleep state.
Mar 10 19:59:53 systemd-sleep[57639]: Entering sleep state 'suspend'...
Mar 10 20:06:31 systemd-sleep[57639]: System returned from sleep state.
Mar 10 20:31:50 systemd-sleep[58835]: Entering sleep state 'suspend'...
Mar 10 20:36:08 systemd-sleep[58835]: System returned from sleep state.
Mar 10 20:44:27 systemd-sleep[59401]: Entering sleep state 'suspend'...
Mar 10 20:46:29 systemd-sleep[59401]: System returned from sleep state.
Mar 10 20:50:29 systemd-sleep[60592]: Entering sleep state 'suspend'...
Mar 10 20:59:44 systemd-sleep[60592]: System returned from sleep state.
Mar 10 21:07:28 systemd-sleep[61120]: Entering sleep state 'suspend'...
Mar 11 10:24:03 systemd-sleep[61120]: System returned from sleep state.
Mar 11 10:43:58 systemd-sleep[63205]: Entering sleep state 'suspend'...
Mar 11 10:54:00 systemd-sleep[63205]: System returned from sleep state.
-- Boot 3321169233dd4ae7ae46fcfddff99a1b --
Mar 12 17:41:23 systemd-sleep[35293]: Entering sleep state 'suspend'...
Mar 12 18:37:34 systemd-sleep[35293]: System returned from sleep state.
Mar 12 18:59:43 systemd-sleep[37152]: Entering sleep state 'suspend'...
Mar 12 19:10:04 systemd-sleep[37152]: System returned from sleep state.
Mar 12 21:14:23 systemd-sleep[43353]: Entering sleep state 'suspend'...
Mar 12 21:15:19 systemd-sleep[43353]: System returned from sleep state.
Mar 12 22:06:16 systemd-sleep[44687]: Entering sleep state 'suspend'...
Mar 13 17:18:29 systemd-sleep[44687]: System returned from sleep state.
Mar 13 19:36:33 systemd-sleep[48035]: Entering sleep state 'suspend'...
Mar 13 19:47:09 systemd-sleep[48035]: System returned from sleep state.
-- Boot 048916a77f4e4b91b97212d155a46bc2 --
Mar 13 20:05:16 systemd-sleep[6063]: Entering sleep state 'suspend'...
Mar 13 20:05:51 systemd-sleep[6063]: System returned from sleep state.
Mar 13 20:07:13 systemd-sleep[6350]: Entering sleep state 'suspend'...
Mar 13 20:07:22 systemd-sleep[6350]: System returned from sleep state.
-- Boot 37f64c442a2a470d8ebeab20503f6dfd --
Mar 16 18:27:19 systemd-sleep[4634]: Entering sleep state 'suspend'...
Mar 16 18:49:06 systemd-sleep[4634]: System returned from sleep state.
-- Boot e837e1c24b884a11b50ae0bde206edd4 --
Mar 16 21:45:41 systemd-sleep[11536]: touchpad-suspend-workaround: unloading i2c_hid
Mar 16 21:45:41 systemd-sleep[11538]: i2c_hid_acpi
Mar 16 21:45:41 systemd-sleep[11525]: Entering sleep state 'suspend'...
Mar 17 07:54:04 systemd-sleep[11525]: System returned from sleep state.
Mar 17 07:54:04 systemd-sleep[11657]: touchpad-suspend-workaround: loading i2c_hid
Mar 17 12:51:07 systemd-sleep[35857]: touchpad-suspend-workaround: unloading i2c_hid
Mar 17 12:51:07 systemd-sleep[35858]: i2c_hid_acpi
Mar 17 12:51:07 systemd-sleep[35850]: Entering sleep state 'suspend'...
Mar 17 12:57:19 systemd-sleep[35850]: System returned from sleep state.
Mar 17 12:57:19 systemd-sleep[35962]: touchpad-suspend-workaround: loading i2c_hid
-- Boot 7fd3c21d951a4a148c4c87b3fa4ac172 --
Mar 18 10:17:11 systemd-sleep[4551]: touchpad-suspend-workaround: unloading i2c_hid
Mar 18 10:17:11 systemd-sleep[4552]: i2c_hid_acpi
Mar 18 10:17:11 systemd-sleep[4539]: Entering sleep state 'hibernate'...
Mar 18 10:18:11 systemd-sleep[4539]: System returned from sleep state.
Mar 18 10:18:11 systemd-sleep[4664]: touchpad-suspend-workaround: loading i2c_hid
Mar 18 10:39:02 systemd-sleep[6613]: touchpad-suspend-workaround: unloading i2c_hid
Mar 18 10:39:02 systemd-sleep[6614]: i2c_hid_acpi
Mar 18 10:39:02 systemd-sleep[6604]: Entering sleep state 'hibernate'...
Mar 18 10:39:53 systemd-sleep[6604]: System returned from sleep state.
Mar 18 10:39:53 systemd-sleep[6750]: touchpad-suspend-workaround: loading i2c_hid
-- Boot 10733b068bfe4fd2888d31bbf7c277e3 --
Mar 18 12:09:33 systemd-sleep[12986]: touchpad-suspend-workaround: unloading i2c_hid
Mar 18 12:09:33 systemd-sleep[12987]: i2c_hid_acpi
Mar 18 12:09:33 systemd-sleep[12974]: Entering sleep state 'hibernate'...
Mar 18 12:09:41 systemd-sleep[12974]: Failed to put system to sleep. System resumed again: No space left on device
Mar 18 12:09:41 systemd-sleep[13110]: touchpad-suspend-workaround: loading i2c_hid
Mar 18 12:10:13 systemd-sleep[13271]: touchpad-suspend-workaround: unloading i2c_hid
Mar 18 12:10:13 systemd-sleep[13273]: i2c_hid_acpi
Mar 18 12:10:13 systemd-sleep[13263]: Entering sleep state 'hibernate'...
Mar 18 12:10:22 systemd-sleep[13263]: Failed to put system to sleep. System resumed again: No space left on device
Mar 18 12:10:22 systemd-sleep[13324]: touchpad-suspend-workaround: loading i2c_hid
Mar 18 12:11:03 systemd-sleep[13566]: touchpad-suspend-workaround: unloading i2c_hid
Mar 18 12:11:03 systemd-sleep[13568]: i2c_hid_acpi
Mar 18 12:11:03 systemd-sleep[13557]: Entering sleep state 'hibernate'...
Mar 18 12:11:11 systemd-sleep[13557]: Failed to put system to sleep. System resumed again: No space left on device
Mar 18 12:11:11 systemd-sleep[13622]: touchpad-suspend-workaround: loading i2c_hid
-- Boot a498c782f0f34b2bbea2aa816367d619 --
Mar 20 10:53:52 systemd-sleep[6507]: touchpad-suspend-workaround: unloading i2c_hid
Mar 20 10:53:52 systemd-sleep[6508]: i2c_hid_acpi
Mar 20 10:53:52 systemd-sleep[6497]: Entering sleep state 'suspend'...
Mar 20 18:04:11 systemd-sleep[6497]: System returned from sleep state.
Mar 20 18:04:11 systemd-sleep[6607]: touchpad-suspend-workaround: loading i2c_hid
Mar 20 18:16:58 systemd-sleep[10117]: touchpad-suspend-workaround: unloading i2c_hid
Mar 20 18:16:58 systemd-sleep[10118]: i2c_hid_acpi
Mar 20 18:16:58 systemd-sleep[10110]: Entering sleep state 'suspend'...
Mar 20 21:52:52 systemd-sleep[10110]: System returned from sleep state.
Mar 20 21:52:52 systemd-sleep[10222]: touchpad-suspend-workaround: loading i2c_hid
Is it behaving correctly atm? looks like sleeping/waking up okay according to logs, let us know if something comes up again.
1 Like
Ok, now that I’m back home I can pay attention to it again
Tasks: 400 total, 1 running, 399 sleeping, 0 stopped, 0 zombie
%Cpu(s): 6.8 us, 1.3 sy, 0.0 ni, 91.8 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st
MiB Mem : 31812.8 total, 20036.0 free, 4245.7 used, 7531.0 buff/cache
MiB Swap: 1956.0 total, 1956.0 free, 0.0 used. 25314.0 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
65499 sam 20 0 2841284 392804 148412 S 72.4 1.2 2:06.13 Isolated Web Co
3021 sam 20 0 12.3g 616496 241116 S 25.2 1.9 38:47.62 firefox
2361 sam 20 0 7265288 392624 178376 S 17.9 1.2 24:38.17 gnome-shell
46180 sam 20 0 2577956 170976 98724 S 4.3 0.5 4:49.73 gnome-control-c
3114 sam 20 0 1353968 101400 63356 S 3.0 0.3 5:35.64 Xwayland
9551 sam 10 -10 1237236 197492 144636 S 2.0 0.6 24:52.29 steam
1212 root 20 0 12592 6640 5068 S 1.0 0.0 0:27.39 bluetoothd
9589 sam 20 0 525088 189284 168328 S 1.0 0.6 8:50.49 steamwebhelper
713 root 19 -1 260096 165940 164224 S 0.7 0.5 0:13.61 systemd-journal
19081 sam 20 0 597644 79768 62680 S 0.7 0.2 0:15.14 gnome-terminal-
57635 root 20 0 0 0 0 I 0.7 0.0 0:04.97 kworker/u32:35-i915
66635 sam 20 0 21976 4412 3276 R 0.7 0.0 0:00.05 top
15 root 20 0 0 0 0 I 0.3 0.0 0:52.19 rcu_preempt
112 root 20 0 0 0 0 S 0.3 0.0 0:00.95 kauditd
339 root 0 -20 0 0 0 I 0.3 0.0 0:01.25 kworker/4:1H-events_highpri
754 root 0 -20 0 0 0 I 0.3 0.0 0:02.04 kworker/15:1H-events_highpri
1551 root 20 0 246496 8980 6120 S 0.3 0.0 1:46.73 upowerd
2705 sam 20 0 171684 7188 6584 S 0.3 0.0 0:02.07 ibus-engine-sim
3436 sam 20 0 7147916 256964 97280 S 0.3 0.8 2:30.38 WebExtensions
3660 sam 20 0 2657012 188592 95212 S 0.3 0.6 1:19.03 Isolated Web Co
55710 root 0 -20 0 0 0 I 0.3 0.0 0:14.47 kworker/u33:4-hci0
58334 sam 20 0 3115740 84160 65660 S 0.3 0.3 0:01.94 gjs
60195 root 20 0 0 0 0 I 0.3 0.0 0:00.50 kworker/10:1-events
64817 root 20 0 0 0 0 I 0.3 0.0 0:02.04 kworker/u32:6-events_unbound
66131 root 20 0 0 0 0 I 0.3 0.0 0:00.26 kworker/2:2-events
66252 root 0 -20 0 0 0 D 0.3 0.0 0:00.49 kworker/u33:3+i915_flip
66268 root 20 0 0 0 0 I 0.3 0.0 0:01.19 kworker/15:1-events
66344 root 20 0 0 0 0 I 0.3 0.0 0:00.33 kworker/u32:5-kcryptd/253:0
1 root 20 0 169860 14484 8680 S 0.0 0.0 0:04.30 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.10 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 slub_flushwq
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-events_highpri
10 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
11 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_kthread
12 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_rude_kthread
13 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_trace_kthread
14 root 20 0 0 0 0 S 0.0 0.0 0:00.55 ksoftirqd/0
16 root rt 0 0 0 0 S 0.0 0.0 0:01.87 migration/0
17 root -51 0 0 0 0 S 0.0 0.0 0:00.00 idle_inject/0
19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
20 root 20 0 0 0 0 S 0.0 0.0 0:00.01 cpuhp/1
As you can see there is web content that’s taking up a lot of the CPU power. That’s flightradar24, which I’ve found the most reliable way to get the fans running. This I don’t have this issue if I run it on my older, much lower spec thinkpad running Ubuntu 22.04
Is web content running on top of chrome?
1 Like
No, it’s running on firefox
Would be interesting to see numbers on the other machine that runs this (web app) lighter? do they have different firefox versions?
1 Like
Here you go, tried best to replicate the circumstances on my Thinkpad T520 (i5-5300, 8 GB RAM) running Ubuntu 22.10 and Firefox 111.0.1 (as opposed to 111.0 on the framework)
top - 10:38:06 up 15 min, 1 user, load average: 3.91, 2.67, 1.70
Tasks: 234 total, 3 running, 231 sleeping, 0 stopped, 0 zombie
%Cpu(s): 47.8 us, 16.4 sy, 0.0 ni, 35.8 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st
MiB Mem : 7822.9 total, 144.8 free, 2949.1 used, 4729.0 buff/cache
MiB Swap: 2048.0 total, 2044.7 free, 3.2 used. 3584.4 avail Mem
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2553 samuel 20 0 11.7g 528636 263828 S 87.5 6.6 4:42.13 firefox
2940 samuel 20 0 2968572 506316 196676 R 75.0 6.3 4:15.20 Isolated Web Co
1782 samuel 20 0 5178952 292648 135808 S 25.0 3.7 1:42.02 gnome-shell
18 root 20 0 0 0 0 I 6.2 0.0 0:00.97 kworker/0:1-events
2132 samuel 20 0 1119892 274940 56140 S 6.2 3.4 0:13.88 snap-store
2189 samuel 20 0 842712 106000 62560 S 6.2 1.3 0:41.88 Xwayland
5430 samuel 20 0 557856 53796 41112 S 6.2 0.7 0:03.64 gnome-terminal-
6267 root 20 0 0 0 0 I 6.2 0.0 0:00.33 kworker/1:0-events
6420 root 20 0 0 0 0 R 6.2 0.0 0:03.40 kworker/2:2-events
6901 samuel 20 0 13036 4016 3280 R 6.2 0.1 0:00.02 top
1 root 20 0 169744 14588 8816 S 0.0 0.2 0:02.14 systemd
2 root 20 0 0 0 0 S 0.0 0.0 0:00.00 kthreadd
3 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_gp
4 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 rcu_par_gp
5 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 slub_flushwq
6 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 netns
8 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/0:0H-events_highpri
10 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 mm_percpu_wq
11 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_kthread
12 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_rude_kthread
13 root 20 0 0 0 0 I 0.0 0.0 0:00.00 rcu_tasks_trace_kthread
14 root 20 0 0 0 0 S 0.0 0.0 0:00.21 ksoftirqd/0
15 root 20 0 0 0 0 I 0.0 0.0 0:01.54 rcu_preempt
16 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0
17 root -51 0 0 0 0 S 0.0 0.0 0:00.00 idle_inject/0
19 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/0
20 root 20 0 0 0 0 S 0.0 0.0 0:00.00 cpuhp/1
21 root -51 0 0 0 0 S 0.0 0.0 0:00.00 idle_inject/1
22 root rt 0 0 0 0 S 0.0 0.0 0:00.16 migration/1
23 root 20 0 0 0 0 S 0.0 0.0 0:00.15 ksoftirqd/1
25 root 0 -20 0 0 0 I 0.0 0.0 0:00.00 kworker/1:0H-events_highpri
I did notice the web app was quite a bit slower on the thinkpad, and and the fan on thinkpad sounds calmer, so perhaps it’s just getting used to a new computer. It seems to have improved with the most recent firefox update
Just popped into this, not seeing out of site temps. The fan can indeed run a bit on the loud side. But from my experience if the fan is running, it’s by design and doing its job.
The Firefox snap can indeed run the fans a bit, would be interesting to see if this is a problem with other browsers. But outside of tweaking TLP to toggle some thing down or getting into ECTool territory, I prefer to let me fan run.
@Samuel_Dyck just got an idea:
Does the situation improve with a new firefox profile? Maybe an addon is acting up.
1 Like