System Performance Issues After Upgrading to Fedora 42

Ask Fedora
, , , , , , ,
1

Hello,

I recently upgraded my system from Fedora 41 to Fedora 42, and I have been experiencing performance issues. The system feels slow and not as responsive as before. Here are the details of my system :

System Details Report

Report details

  • Date generated: 2025-04-17 22:41:05

Hardware Information:

  • Hardware Model: Dell Inc. G3 3500
  • Memory: 8.0 GiB
  • Processor: Intel® Core™ i5-10300H × 8
  • Graphics: Intel® UHD Graphics (CML GT2)
  • Graphics 1: NVIDIA GeForce GTX 1650
  • Disk Capacity: 1.0 TB

Software Information:

  • Firmware Version: 1.32.0
  • OS Name: Fedora Linux 42 (Workstation Edition)
  • OS Build: (null)
  • OS Type: 64-bit
  • GNOME Version: 48
  • Windowing System: Wayland
  • Kernel Version: Linux 6.14.2-300.fc42.x86_64

Disk Usage: I checked my disk usage and here are the results:

Filesystem      Size  Used Avail Use% Mounted on
/dev/dm-0       435G  367G   66G  85% /
devtmpfs        4.0M     0  4.0M   0% /dev
tmpfs           3.8G  153M  3.7G   4% /dev/shm
efivarfs        374K  187K  183K  51% /sys/firmware/efi/efivars
tmpfs           1.6G  2.7M  1.6G   1% /run
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-cryptsetup@luks\x2d151dc833\x2d486e\x2d4b22\x2d989e\x2d32afa0c55f2e.service
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs           3.8G   41M  3.8G   2% /tmp
/dev/dm-0       435G  367G   66G  85% /home
/dev/nvme0n1p2  974M  379M  529M  42% /boot
/dev/nvme0n1p1  599M   51M  549M   9% /boot/efi
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
tmpfs           773M  8.5M  764M   2% /run/user/1000

Memory Usage: I also checked my memory usage:

               total        used        free      shared  buff/cache   available
Mem:           7.5Gi       4.7Gi       360Mi       884Mi       3.6Gi       2.8Gi
Swap:          8.0Gi       1.8Gi       6.2Gi

Running Services: I looked at the running services to see if there are any that I can disable:

  UNIT                                         LOAD      ACTIVE SUB     DESCRIPTION                                            
  abrt-journal-core.service                    loaded    active running ABRT coredumpctl message creator
  abrt-oops.service                            loaded    active running ABRT kernel log watcher
  abrt-xorg.service                            loaded    active running ABRT Xorg log watcher
  abrtd.service                                loaded    active running ABRT Daemon
  accounts-daemon.service                      loaded    active running Accounts Service
  alsa-state.service                           loaded    active running Manage Sound Card State (restore and store)
  auditd.service                               loaded    active running Security Audit Logging Service
  avahi-daemon.service                         loaded    active running Avahi mDNS/DNS-SD Stack
  bluetooth.service                            loaded    active running Bluetooth service
  bolt.service                                 loaded

and i cheack journalctl -b -p 3

$ journalctl -b -p 3
Apr 18 00:06:06 fedora kernel: x86/cpu: SGX disabled or unsupported by BIOS.
Apr 17 21:06:21 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:22 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:22 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:22 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:22 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:23 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:24 fedora kernel: 
Apr 17 21:06:24 fedora kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20240827/psargs-332)
Apr 17 21:06:24 fedora kernel: ACPI Error: Aborting method \_SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20240827/psparse-529)
Apr 17 21:06:24 fedora bluetoothd[1335]: Failed to set mode: Failed (0x03)
Apr 17 21:06:23 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:24 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:25 fedora /usr/bin/nvidia-powerd[1349]: SBIOS support not found for NVPCF GET_SUPPORTED function
Apr 17 21:06:25 fedora /usr/bin/nvidia-powerd[1349]: No matching GPU found
Apr 17 21:06:25 fedora /usr/bin/nvidia-powerd[1349]: Failed to initialize Dynamic Boost
Apr 17 21:06:25 fedora /usr/bin/nvidia-powerd[1349]: Failed to detach GPU id 256
Apr 17 21:06:25 fedora /usr/bin/nvidia-powerd[1349]: Failed to initialize Dynamic Boost
Apr 17 21:06:25 fedora /usr/bin/nvidia-powerd[1349]: Failed to detach GPU id 256
Apr 17 21:06:25 fedora systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:30 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:31 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:32 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:32 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:32 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:32 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:32 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:32 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:44 ConnectON gdm-password][2537]: gkr-pam: unable to locate daemon control file
Apr 17 21:06:44 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:45 ConnectON systemd[2557]: Failed to start app-gnome-gnome\x2dkeyring\x2dpkcs11-2715.scope - Application launched by gnome-session-binary.
Apr 17 21:06:45 ConnectON systemd[2557]: Failed to start app-gnome-gnome\x2dkeyring\x2dsecrets-2718.scope - Application launched by gnome-session-binary.
Apr 17 21:06:45 ConnectON systemd[2557]: Failed to start app-gnome-gnome\x2dkeyring\x2dssh-2712.scope - Application launched by gnome-session-binary.
Apr 17 21:06:46 ConnectON systemd[2557]: Failed to start app-gnome-user\x2ddirs\x2dupdate\x2dgtk-2912.scope - Application launched by gnome-session-binary.
Apr 17 21:06:47 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:47 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:47 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:50 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:06:55 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:07:00 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:07:18 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:08:03 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:08:03 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:08:12 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:10:12 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:11:43 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Apr 17 21:11:46 ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
2

Welcome to Fedora @ahmednn72

It looks like your swap is not working correctly, this could cause the less smooth experience.

ConnectON systemd[1]: Failed to start systemd-zram-setup@zram0.service - Create swap on /dev/zram0

What does your lsblk show?

Mine gives me with 16GB Memory a :

zram0  252:0    0     8G  0 disk [SWAP]
1 Like
3 
nvme0n1                                       259:0    0 476.9G  0 disk  
├─nvme0n1p1                                   259:1    0   600M  0 part  /boot/efi
├─nvme0n1p2                                   259:2    0     1G  0 part  /boot
├─nvme0n1p3                                   259:3    0   435G  0 part  
│ └─luks-151dc833-486e-4b22-989e-32afa0c55f2e 253:0    0   435G  0 crypt /home
│                                                                        /
├─nvme0n1p4                                   259:4    0    16M  0 part  
├─nvme0n1p5                                   259:5    0  39.7G  0 part  
└─nvme0n1p6                                   259:6    0   642M  0 part
4

And what shows you the status message?

sudo systemctl status /dev/zram0

6

I also have performance issues since the upgrade to F42. Can you elaborate yours a little more?

In my case, applications/processes freeze for several seconds, but always in an isolated manner (so everythin else keeps working responsive). So far I had freezes of around 10 seconds of kate when I clicked in the text window to write something, Firefox when opening new tabs, the WiFi itself (I presume that was wpa_supplicant), and the sleep mode (when initiating sleep, the screen goes locked and freezes around 10 seconds before finally going sleep). Also, the desktop/KDE itself can freeze, and at a boot, I had the same issue with cryptsetup that did not respond some time until my encrypted disks had been decrypted and subsequently mounted (I already feared the system no longer boots :classic_smiley: ). But in all cases in which I could test it (firefox, desktop/KDE, kate), everything else worked fine and I could still do other things while they had been frozen.

My logs only indicate that processes sometimes don’t respond for some time, but at first glance not much more. However, I have not yet done a sophisticated check of what is going on, and did not yet review logs in detail. But when I saw your topic, I wanted to roughly summarize my case and see if that is about what you experience?

I have no taints in the kernel (taint = 0) and no nvidia, only default Fedora repos plus the mesa drivers from rpmfusion (I limited rpmfusion to these drivers’ packages). AMD Ryzen 7 PRO 6850U with Radeon Graphics. 6.14.2-300.fc42.x86_64. I have no swap but 32 GB RAM, which definitely is more than a normal Fedora installation needs. F42 KDE, originally installed at the time of F37. I hope I can spare some time in the next days to check this out more detailed, but my time is slightly limited these days :classic_smiley:

Anyway, would be good to check out if we experience the same thing, and see if we can identify (maybe also with others) what those who experience this issue have in common.

Supplement: I added kernel and KDE for now, the first as this could be linked to a kernel issue (including your elaboration as far as known), and as long as we cannot link it to something that explicitly is related to only Workstation, performance issues like ours are likely to be not linked to the DE, so it might be useful to also lead KDE people with performance issues here so that they can compare. I can split the topics later if we find out that its different. I hope that is in your interest too, otherwise I can remove it again - its your topic :classic_smiley:

If we find out that your issue is the same as mine, I suggest we remove nvidia (which I do not yet do to keep focused on your case), as it then is likely to be not related and only distracts in such a case.

1 Like
9 
○ dev-zram0.device - /dev/zram0
     Loaded: loaded
     Active: inactive (dead)
10

In order to keep together all data that belongs together (which fosters solution of the issue for everyone affected), I suggested to consolidate experiences and what people have in common in the topic that already consolidates several cases: Consistent screen freezes after upgrading to F42 - #10 by airdiz → you might use this IF its elaborations apply to you. Feel free to add more information to help identifying what all have in common in order to identify what cases are the same, and what might be the origin.

I leave all other topics open as the elaborations of the three topics (this one, the one I just mentioned, plus No.3, and maybe more) do not yet make clear if that really are all the same issue. So if you think the one I mentioned does not apply to you but any of the other, you may of course keep posting there. But I suggest to mention your reasons in order to help delimiting the issues.

Everybody is free to open a bug report of course, but I suggest to invest the time to fill its fields carefully and produce and provide relevant data/logs that get attached, in order to get a real chance that a maintainer can pick it up (especially in times of a new release maintainers have to focus).

If you see more related topics that might resemble one of the existing ones, feel free to let them know about the others.

1 Like