Why does the fan run at full speed and my Fedora crashes a little later?

Ask Fedora Ask in English
, , , ,
1

Hello dear community,

I have a problem with my fresh installation on my new used bought laptop. :frowning:

I thought it was a problem with my battery. Because after some time the device crashes as if the battery was removed without warning. But even another battery did not solve the problem.

The fan is turned up to full speed without the CPU or memory being used to capacity. Then it shuts down a little later.
The solution for me is currently that I put the laptop into hibernation briefly when the fan starts up and wake it up again. Then the runs normally again for a while.

Unfortunately, this is not a condition I can work with. :frowning:
I did not notice anything in the logs either.

$ journalctl -b -1 -n 50 
Sep 24 09:48:01 fedora gdm-password][13570]: gkr-pam: unlocked login keyring
Sep 24 09:48:01 fedora audit[13570]: USER_AUTH pid=13570 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam>
Sep 24 09:48:01 fedora audit[13570]: USER_ACCT pid=13570 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="jakob>
Sep 24 09:48:01 fedora audit[13570]: CRED_REFR pid=13570 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_gnome_keyr>
Sep 24 09:48:01 fedora audit: BPF prog-id=95 op=LOAD
Sep 24 09:48:01 fedora audit: BPF prog-id=96 op=LOAD
Sep 24 09:48:01 fedora systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Sep 24 09:48:01 fedora systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Sep 24 09:48:01 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/s>
Sep 24 09:48:02 fedora NetworkManager[10480]: <info>  [1664005682.0349] agent-manager: agent[971f15887422b13e,:1.42/org.gnome.Shell.NetworkAgent/1000]: agent registered
Sep 24 09:48:01 fedora gdm-password][13570]: gkr-pam: unlocked login keyring
Sep 24 09:48:01 fedora audit[13570]: USER_AUTH pid=13570 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:authentication grantors=pam_usertype,pam_localuser,pam>
Sep 24 09:48:01 fedora audit[13570]: USER_ACCT pid=13570 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:accounting grantors=pam_unix,pam_localuser acct="jakob>
Sep 24 09:48:01 fedora audit[13570]: CRED_REFR pid=13570 uid=0 auid=1000 ses=1 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:setcred grantors=pam_localuser,pam_unix,pam_gnome_keyr>
Sep 24 09:48:01 fedora audit: BPF prog-id=95 op=LOAD
Sep 24 09:48:01 fedora audit: BPF prog-id=96 op=LOAD
Sep 24 09:48:01 fedora systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
Sep 24 09:48:01 fedora systemd[1]: Started systemd-hostnamed.service - Hostname Service.
Sep 24 09:48:01 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/s>
Sep 24 09:48:02 fedora NetworkManager[10480]: <info>  [1664005682.0349] agent-manager: agent[971f15887422b13e,:1.42/org.gnome.Shell.NetworkAgent/1000]: agent registered
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
Sep 24 09:48:02 fedora gnome-shell[10737]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
Sep 24 09:48:04 fedora bluetoothd[10355]: /org/bluez/hci0/dev_D8_37_3B_12_F6_2B/sep2/fd2: fd(28) ready
Sep 24 09:48:04 fedora gnome-shell[10737]: g_settings_get_enum() called on key 'control-nightlight' which is not associated with an enumerated type
Sep 24 09:48:12 fedora wireplumber[10706]: error reading timerfd: Die Ressource ist zur Zeit nicht verfĂźgbar
Sep 24 09:48:32 fedora systemd[1]: systemd-hostnamed.service: Deactivated successfully.
Sep 24 09:48:32 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/sy>
Sep 24 09:48:32 fedora audit: BPF prog-id=0 op=UNLOAD
Sep 24 09:48:32 fedora audit: BPF prog-id=0 op=UNLOAD
Sep 24 09:49:25 fedora systemd[1]: fprintd.service: Deactivated successfully.
Sep 24 09:49:25 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=fprintd comm="systemd" exe="/usr/lib/systemd/systemd" hos>
Sep 24 09:49:25 fedora audit: BPF prog-id=0 op=UNLOAD
Sep 24 09:49:30 fedora wireplumber[10706]: error reading timerfd: Die Ressource ist zur Zeit nicht verfĂźgbar
Sep 24 09:49:48 fedora wireplumber[10706]: error reading timerfd: Die Ressource ist zur Zeit nicht verfĂźgbar
Sep 24 09:49:52 fedora wireplumber[10706]: error reading timerfd: Die Ressource ist zur Zeit nicht verfĂźgbar
Sep 24 09:49:58 fedora systemd[1]: flatpak-system-helper.service: Deactivated successfully.
Sep 24 09:49:58 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=flatpak-system-helper comm="systemd" exe="/usr/lib/system>
Sep 24 09:49:58 fedora systemd[1]: flatpak-system-helper.service: Consumed 1.529s CPU time.
Sep 24 09:50:18 fedora wireplumber[10706]: error reading timerfd: Die Ressource ist zur Zeit nicht verfĂźgbar
Sep 24 09:50:24 fedora wireplumber[10706]: error reading timerfd: Die Ressource ist zur Zeit nicht verfĂźgbar

<pre># lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
00:01.0 PCI bridge: Intel Corporation 6th-10th Gen Core Processor PCIe Controller (x16) (rev 05)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics P630 (rev 04)
00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
00:16.3 Serial controller: Intel Corporation 100 Series/C230 Series Chipset Family KT Redirection (rev 31)
00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1 (rev f1)
00:1c.1 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #2 (rev f1)
00:1c.2 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1)
00:1c.4 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
00:1f.0 ISA bridge: Intel Corporation CM238 Chipset LPC/eSPI Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31)
00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (5) I219-LM (rev 31)
01:00.0 3D controller: NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] (rev a1)
01:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1)
03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS524A PCI Express Card Reader (rev 01)
05:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
06:00.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
06:01.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
06:02.0 PCI bridge: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] (rev 02)
3c:00.0 USB controller: Intel Corporation JHL6340 Thunderbolt 3 USB 3.1 Controller (C step) [Alpine Ridge 2C 2016] (rev 02)
3d:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983</pre>

# rpm -qa | grep -i firmware
zd1211-firmware-1.5-10.fc36.noarch
atmel-firmware-1.3-26.fc36.noarch
alsa-sof-firmware-2.1.1-1.fc36.noarch
linux-firmware-whence-20220815-139.fc36.noarch
amd-gpu-firmware-20220815-139.fc36.noarch
intel-gpu-firmware-20220815-139.fc36.noarch
nvidia-gpu-firmware-20220815-139.fc36.noarch
linux-firmware-20220815-139.fc36.noarch
iwlax2xx-firmware-20220815-139.fc36.noarch
iwl7260-firmware-25.30.13.0-139.fc36.noarch
iwl100-firmware-39.31.5.1-139.fc36.noarch
iwl1000-firmware-39.31.5.1-139.fc36.noarch
iwl105-firmware-18.168.6.1-139.fc36.noarch
iwl135-firmware-18.168.6.1-139.fc36.noarch
iwl2000-firmware-18.168.6.1-139.fc36.noarch
iwl2030-firmware-18.168.6.1-139.fc36.noarch
iwl3160-firmware-25.30.13.0-139.fc36.noarch
iwl3945-firmware-15.32.2.9-139.fc36.noarch
iwl4965-firmware-228.61.2.24-139.fc36.noarch
iwl5000-firmware-8.83.5.1_1-139.fc36.noarch
iwl5150-firmware-8.24.2.2-139.fc36.noarch
iwl6000-firmware-9.221.4.1-139.fc36.noarch
iwl6000g2a-firmware-18.168.6.1-139.fc36.noarch
iwl6000g2b-firmware-18.168.6.1-139.fc36.noarch
iwl6050-firmware-41.28.5.1-139.fc36.noarch
libertas-usb8388-firmware-20220815-139.fc36.noarch

System Infos:

-------------------------------System Information----------------------------
Hostname:			fedora
uptime:				35 min
Manufacturer:		FUJITSU
Product Name:		CELSIUS H770
Version:			10601736746
Machine Type:		Physical
Operating System:	Fedora Linux 36 (Workstation Edition)
Kernel:				5.19.9-200.fc36.x86_64
Architecture:		x86_64
Processor Name:		Intel(R) Xeon(R) CPU E3-1505M v6 @ 3.00GHz
System Main IP:		192.168.0.8 
-------------------------------CPU/Memory Usage------------------------------
Memory Usage:	7.88%
Swap Usage:	0.00%
CPU Usage:	8.64%

I would be very happy if you had a tip for me. :slight_smile:

And also how I can reduce the start-up of the system. Or is that related?

Your home user

Jack

2

Hi Jack,

Unless I am mistaken, this laptop comes with either Quadro M1200 or M2200 graphics. Have you enabled the RPM Fusion repositories and installed the nVidia driver?

Once everything is installed and working, check the output of systemd-analyze blame and systemd-analyze critical-chain. These should give you some hints as to what can be improved.

3

Hi Alexpl, :smiley:

thanks for the info.
It is right, I use the Quadro M2200:

lspci | grep Quadro
01:00.0 3D controller: NVIDIA Corporation GM206GLM [Quadro M2200 Mobile] (rev a1)

I actually want to use only open source software. It does not have to be free under the GPL. But I thought RPM Fusion nonfree also means closed source. This is a wrong assumption or?

nonfree for redistributable software that is not Open Source Software (as defined by the Fedora Licensing Guidelines); this *includes* software with publicly available source-code that has "no commercial use"-like restrictions

I think the word “includes” is meant as a “is” or?
09f4a987013efad4655617dc5f4bdcdc2e2cd2d0.png

Then I just need to activate nonfree - nvidia and install it?

Thanks a lot!

Jack

4

The thing is that the nouveau open-source driver provides very limited functionality compared to that provided by the nVidia driver and more pertinent to your issue, it cannot change clock speeds and that is why your laptop is heating up. Unless you are using Intel graphics or some older graphics card that is well-supported by nouveau, you can’t have a fully open-source system and full control over your hardware, that is the sad truth.

See the relevant section in the FAQ.
By the way, any video player you might want to install, e.g. vlc, mpv, smplayer, etc. is found in RPM Fusion.

Well, I guess so, but in the long run you might be better off enabling the full RPM Fusion repositories following the instructions I linked to in my first post.

5

Oh ok. Thanks alexpl. I thought nouveau is as good as the original. :confused: I installed the nonfree. Next time I will buy intel. :zipper_mouth_face:

Only networking takes now some time. The rest is fine I think:

$ systemd-analyze blame
21.323s plymouth-quit-wait.service
11.681s dracut-initqueue.service
11.297s systemd-cryptsetup@luks\x2d9c7c2ad4\x2d2a5e\x2d423d\x2d8fac\x2d0c8f6b17c279.service
 6.255s NetworkManager-wait-online.service
 1.678s nvidia-powerd.service
 1.556s fwupd.service
 1.087s initrd-switch-root.service
  760ms akmods.service
  696ms lvm2-monitor.service
  552ms firewalld.service
  291ms udisks2.service
  276ms initrd-cleanup.service
  242ms upower.service
  229ms ModemManager.service
  213ms systemd-udev-trigger.service
  210ms power-profiles-daemon.service
  207ms user@1000.service
  205ms accounts-daemon.service
  202ms polkit.service
  195ms dracut-cmdline.service
  166ms avahi-daemon.service
  165ms bluetooth.service
  154ms initrd-parse-etc.service
  148ms systemd-resolved.service
  148ms switcheroo-control.service
  145ms rtkit-daemon.service
  137ms systemd-logind.service
  134ms thermald.service
  124ms var-lib-nfs-rpc_pipefs.mount
  118ms systemd-oomd.service
  115ms abrtd.service
  114ms plymouth-switch-root.service
  111ms systemd-rfkill.service
  103ms systemd-journal-flush.service
   97ms systemd-tmpfiles-setup.service
   94ms systemd-fsck@dev-disk-by\x2duuid-fdfb735d\x2d3a3b\x2d4508\x2d8fa6\x2d97044efae8df.service
   82ms dracut-pre-udev.service
   81ms dev-zram0.swap
   80ms systemd-fsck@dev-disk-by\x2duuid-0543\x2d2D36.service
   78ms chronyd.service
   77ms systemd-remount-fs.service
   77ms nfs-convert.service
   72ms home.mount
   70ms systemd-network-generator.service
   68ms systemd-zram-setup@zram0.service
   64ms initrd-udevadm-cleanup-db.service
   64ms packagekit.service
   63ms systemd-modules-load.service
   61ms systemd-vconsole-setup.service
   59ms modprobe@drm.service
   57ms geoclue.service
   57ms systemd-fsck-root.service
   55ms dbus-broker.service
   54ms systemd-udevd.service
   53ms systemd-sysusers.service


$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @24.401s
└─multi-user.target @24.401s
  └─plymouth-quit-wait.service @3.069s +21.323s
    └─systemd-user-sessions.service @3.044s +20ms
      └─remote-fs.target @3.042s
        └─remote-fs-pre.target @3.042s
          └─nfs-client.target @3.042s
            └─gssproxy.service @3.016s +25ms
              └─network.target @3.010s
                └─wpa_supplicant.service @3.822s +12ms
                  └─dbus-broker.service @2.271s +55ms
                    └─dbus.socket @2.196s
                      └─sysinit.target @2.191s
                        └─systemd-update-utmp.service @2.172s +19ms
                          └─auditd.service @2.127s +42ms
                            └─systemd-tmpfiles-setup.service @2.026s +97ms
                              └─import-state.service @1.976s +42ms
                                └─local-fs.target @1.973s
                                  └─run-user-1000-doc.mount @6.263s
                                    └─run-user-1000.mount @3.236s
                                      └─swap.target @1.737s
                                        └─dev-zram0.swap @1.654s +81ms
                                          └─systemd-zram-setup@zram0.service @1.526s +68ms
                                            └─dev-zram0.device @1.523s

It is ok, is’n it?

6

Running on 100% open-source software is very hard. I think you should accept a bit of compromise. For example, your intel CPU (and all intel CPUs starting from 2008) has a second processor running the intel management engine that has full access to everything without your OS knowing a thing about it. Also your BIOS is very likely proprietary unless it is a Libreboot/coreboot device. Add to that the firmware that ships with the kernel also mostly proprietary. (The kernel itself is open source, but the firmware required by some devices isn’t).

If you want to be safer while using proprietary drivers (and any driver in general), enable IOMMU which restricts each device to its allocated memory only.

7

You are right and that is a whole other discussion.

In the case of RPM Fusion, most packages end up there because of US patent laws and not because of their source code being unavailable.

8

Hopefully by then everyone will have seen the light and everything will be free software!

Everything seems in order. There’s some delay until the LUKS-encrypted volume is unlocked (as one would expect). Do you mount anything over the network? I see the nfs-client and friends loading.

9

No, I do not use nfs. I juast have my local btrfs volumen. :face_with_monocle: