Fedora KDE 31 Freezes Too Much

Before I could write this, my system froze SIX times in just one hour. Everything freezes: screen, keyboard, mouse; all I can do is reboot the system.

Here are some technical aspects of my PC:

-OS: Fedora KDE 31 Workstation
-Kernel: 5.6.8-200.fc31.x86_64
-Shell: bash 5.0.11
-CPU: Intel Celeron E3400 (2) @ 2.603GHz
-GPU: Intel 4 Series Chipset
-RAM: 4GB

Every day I upgrade (dnf upgrade) my system to the latest updates. When the system freezes, in general, I am using the following applications or programs:

-Dolphin
-Firefox (4-5 tabs)
-KTorrent
-Konsole

And someone else, never more than five.

Today I did some things on purpose to test the new kernel (5.6.8-200.fc31.x86_64) that I updated. At the time of the freeze I was using six applications. Among them, Firefox with eight open tabs. As I said, all this on purpose. The CPU marked between 50-60% of use and the RAM 2 of 4GB of use.

I know and I’m aware that I have some shitty hardware. However, Fedora had been running like clockwork. And neither did anything like that ever happen to me in the past with Ubuntu/Kubuntu.

Any idea or possible solution is welcome. However, I’m a basic Linux user, so the step-by-step approach to any hypothetical solution will be very helpful.

Thank you!

Note: I am currently unemployed and broke, so changing the hardware is not an option in the short or medium term, so I appreciate that any idea or possible solution, is with what I have at the moment.

I would begin to “journalctl -p3” or “journalctl -p2” hoping to find:

But my experience is that often there seems to have no interesting information.

You can try older kernels beginning with the one available by “dnf search kernel”.

Hi, man, thanks for the feedback.

This is what journalctl -p3 shows today:

-- Logs begin at Sun 2020-05-03 07:30:36 -05, end at Sun 2020-05-03 12:37:44 -05. --
may 03 07:30:36 localhost.localdomain kernel: usbhid 4-2:1.1: couldn't find an input interrupt endpoint
may 03 12:30:57 localhost.localdomain auditd[707]: Could not open dir /var/log/audit (No such file or directory)
may 03 12:30:57 localhost.localdomain systemd[1]: Failed to start Security Auditing Service.

This is what journalctl -p2 shows today:

-- Logs begin at Sun 2020-05-03 07:30:36 -05, end at Sun 2020-05-03 12:38:29 -05. --
-- No entries --

This is what dnf search kernel shows:

kernel.x86_64 : The Linux kernel
kernel-core.x86_64 : The Linux kernel
python3-metakernel.noarch : Metakernel for Jupyter
python3-ipykernel.noarch : IPython Kernel for Jupyter
abrt-addon-kerneloops.x86_64 : abrt's kerneloops addon
texlive-l3kernel-doc.noarch : Documentation for l3kernel
kernel-tools-libs.x86_64 : Libraries for the kernels-tools
python3-octave-kernel.noarch : A Jupyter kernel for Octave
kernel-tools-libs.i686 : Libraries for the kernels-tools
gap-pkg-jupyterkernel.noarch : Jupyter kernel written in GAP
php-symfony-http-kernel.noarch : Symfony HttpKernel Component
R-IRkernel.noarch : Native R Kernel for the 'Jupyter Notebook'
kernel-debug.x86_64 : kernel meta-package for the debug kernel
kernel-tools.x86_64 : Assortment of tools for the Linux kernel
python3-metakernel-tests.noarch : Tests for python3-metakernel
kernel-modules.x86_64 : kernel modules to match the core kernel
python-ipykernel-doc.noarch : Documentation for python-ipykernel
python-metakernel-doc.noarch : Documentation for python-metakernel
python3-jupyter-c-kernel.noarch : Minimalistic C kernel for Jupyter
python3-jupyter-kernel-singular.noarch : Jupyter kernel for Singular
kernel-debug-modules.x86_64 : kernel modules to match the core kernel
kernel-modules-extra.x86_64 : Extra kernel modules to match the kernel
python3-metakernel-python.noarch : A Python kernel for Jupyter/IPython
python3-spyder-kernels.noarch : Jupyter kernels for the Spyder console
gap-pkg-jupyterkernel-doc.noarch : Jupyter kernel for GAP documentation
kernel-modules-internal.x86_64 : Extra kernel modules to match the kernel
kernel-tools-libs-devel.x86_64 : Assortment of tools for the Linux kernel
python3-metakernel-echo.noarch : A simple echo kernel for Jupyter/IPython
kernel-tools-libs-devel.i686 : Assortment of tools for the Linux kernel
kernel-headers.x86_64 : Header files for the Linux kernel for use by glibc
php-symfony3-http-kernel.noarch : Symfony HttpKernel Component (version 3)
php-symfony4-http-kernel.noarch : Symfony HttpKernel Component (version 4)
libreport-plugin-kerneloops.x86_64 : libreport's kerneloops reporter plugin
kernel-debug-modules-extra.x86_64 : Extra kernel modules to match the kernel
kernel-debug-modules-internal.x86_64 : Extra kernel modules to match the kernel
kernel-debug-core.x86_64 : The Linux kernel compiled with extra debugging enabled
kernel-rpm-macros.noarch : Macros and scripts for building kernel module packages
lirc-disable-kernel-rc.noarch : Disable kernel ir device handling in favor of lirc
kernel-cross-headers.x86_64 : Header files for the Linux kernel for use by cross-glibc
kernel-devel.x86_64 : Development package for building kernel modules to match the kernel
kernel-debug-devel.x86_64 : Development package for building kernel modules to match the kernel
python3-jupyter-kernel-test.noarch : Machinery for testing Jupyter kernels via the messaging protocol
buildsys-build-rpmfusion-kerneldevpkgs-current.x86_64 : Meta-package to get all current kernel-devel packages into the buildroot
==================================================================== Coincidencia en Nombre: kernel ====================================================================
kernelshark.x86_64 : GUI analysis for Ftrace data captured by trace-cmd
erlang-kernel.x86_64 : Main erlang library
texlive-l3kernel.noarch : LaTeX3 programming conventions
=================================================================== Coincidencia en Resumen: kernel ====================================================================
python3-jupyroot.x86_64 : ROOT Jupyter kernel
kup.noarch : Kernel.org Uploader
gromacs-opencl.x86_64 : GROMACS OpenCL kernels
kcbench.noarch : Kernel compile benchmark
python3-jupyter-polymake.noarch : Jupyter kernel for polymake
polymake-jupyter.noarch : Jupyter kernel for polymake
dropwatch.x86_64 : Kernel dropped packet monitor
ksmtuned.x86_64 : Kernel Samepage Merging services
texlive-sphack.noarch : Patch LaTeX kernel spacing macros
glassfish-hk2.noarch : Glassfish Hundred Kilobytes Kernel
crystalhd.x86_64 : Kernel module (kmod) for crystalhd
libevdev.x86_64 : Kernel Evdev Device Wrapper Library
libevdev.i686 : Kernel Evdev Device Wrapper Library
audit.x86_64 : User space tools for kernel auditing
python3-rtslib.noarch : API for Linux kernel LIO SCSI target
uml_utilities.x86_64 : Utilities for user-mode linux kernel
VirtualBox-kmodsrc.noarch : VirtualBox kernel module source code
kup-utils.noarch : Kernel.org Uploader - extra utilities
akmod-wl.x86_64 : Akmod package for wl kernel module(s)
lksctp-tools.i686 : User-space access to Linux Kernel SCTP
lksctp-tools.x86_64 : User-space access to Linux Kernel SCTP
kup-server.noarch : Kernel.org Uploader - server utilities
linux-firmware.noarch : Firmware files used by the Linux kernel
dkms.noarch : Dynamic Kernel Module Support Framework
bcache-tools.x86_64 : Tools for Linux kernel block layer cache
kmod.x86_64 : Linux kernel module management utilities
edac-utils.i686 : Userspace helper for kernel EDAC drivers
edac-utils.x86_64 : Userspace helper for kernel EDAC drivers
python3-kmod.x86_64 : Python module to work with kernel modules
akmod-nvidia.x86_64 : Akmod package for nvidia kernel module(s)
perf.x86_64 : Performance monitoring for the Linux kernel
texlive-latex-base-dev.noarch : Development pre-release of the LaTeX kernel
abrt-addon-coredump-helper.x86_64 : abrt's /proc/sys/kernel/core_pattern helper
qemu-sanity-check.x86_64 : Simple qemu and Linux kernel sanity checker
akmod-wireguard.x86_64 : Akmod package for wireguard kernel module(s)
akmod-crystalhd.x86_64 : Akmod package for crystalhd kernel module(s)
adjtimex.x86_64 : A utility for adjusting kernel time variables
akmod-VirtualBox.x86_64 : Akmod package for VirtualBox kernel module(s)
xorg-x11-drv-nvidia-kmodsrc.x86_64 : xorg-x11-drv-nvidia kernel module source code
libnl3.x86_64 : Convenience library for kernel netlink sockets
libnl3.i686 : Convenience library for kernel netlink sockets
python3-uinput.x86_64 : Pythonic API to the Linux uinput kernel module
akmod-ndiswrapper.x86_64 : Akmod package for ndiswrapper kernel module(s)
systemd-udev.x86_64 : Rule-based device node and kernel event manager
cockpit-kdump.noarch : Cockpit user interface for kernel crash dumping
kabi-dw.x86_64 : Detect changes in the ABI between kernel builds
akmod-nvidia-340xx.x86_64 : Akmod package for nvidia-340xx kernel module(s)
akmod-nvidia-390xx.x86_64 : Akmod package for nvidia-390xx kernel module(s)
xorg-x11-drv-wacom-serial-support.x86_64 : Files for enabling the wacom_w8001 kernel driver
libnozzle1.i686 : Simple userland wrapper around kernel tap devices
libnozzle1.x86_64 : Simple userland wrapper around kernel tap devices
xeus.i686 : C++ implementation of the Jupyter kernel protocol
xeus.x86_64 : C++ implementation of the Jupyter kernel protocol
xeus-devel.i686 : C++ implementation of the Jupyter kernel protocol
xeus-devel.x86_64 : C++ implementation of the Jupyter kernel protocol
pythran.x86_64 : Ahead of Time Python compiler for numeric kernels
akmod-xtables-addons.x86_64 : Akmod package for xtables-addons kernel module(s)
libkcapi.x86_64 : User space interface to the Linux Kernel Crypto API
libkcapi.i686 : User space interface to the Linux Kernel Crypto API
xorg-x11-drv-nvidia-340xx-kmodsrc.x86_64 : xorg-x11-drv-nvidia-340xx kernel module source code
xorg-x11-drv-nvidia-390xx-kmodsrc.x86_64 : xorg-x11-drv-nvidia-390xx kernel module source code
libevdev-utils.x86_64 : Kernel Evdev Device Wrapper Library Utilities Package
dahdi-tools.x86_64 : Userspace tools to configure the DAHDI kernel modules
golang-github-prometheus-procfs-devel.noarch : Retrieve system, kernel and process metrics from proc
syslinux.x86_64 : Simple kernel loader which boots from a FAT filesystem
kmod-libs.x86_64 : Libraries to handle kernel module loading and unloading
libevdev-devel.i686 : Kernel Evdev Device Wrapper Library Development Package
libevdev-devel.x86_64 : Kernel Evdev Device Wrapper Library Development Package
kmod-libs.i686 : Libraries to handle kernel module loading and unloading
pam_cifscreds.x86_64 : PAM module to manage NTLM credentials in kernel keyring
php-stack-builder.noarch : Builder for stack middleware based on HttpKernelInterface
netdump-server.x86_64 : Server for network kernel message logging and crash dumps
rsyslog.x86_64 : Enhanced system logging and kernel message trapping daemon
mkelfimage.x86_64 : Utility to create ELF boot images from Linux kernel images
iptables.x86_64 : Tools for managing Linux kernel packet filtering capabilities
man-pages.noarch : Linux kernel and C library user-space interface documentation
iptables.i686 : Tools for managing Linux kernel packet filtering capabilities
qemu-sanity-check-nodeps.x86_64 : Simple qemu and Linux kernel sanity checker (no dependencies)
arptables-legacy.x86_64 : Legacy user space tool to set up tables of ARP rules in kernel
kmod-wl.x86_64 : Metapackage which tracks in wl kernel module for newest kernel
wraplinux.x86_64 : Utility to wrap a Linux kernel and initrd into an ELF or NBI file
R-lokern.x86_64 : Kernel Regression Smoothing with Local or Global Plug-in Bandwidth
kmod-nvidia.x86_64 : Metapackage which tracks in nvidia kernel module for newest kernel
libnozzle1-devel.i686 : Simple userland wrapper around kernel tap devices (developer files)
libnozzle1-devel.x86_64 : Simple userland wrapper around kernel tap devices (developer files)
blktrace.x86_64 : Utilities for performing block layer IO tracing in the Linux kernel
ebtables-legacy.x86_64 : Legacy user space tool to configure bridge netfilter rules in kernel
ebtables-legacy.i686 : Legacy user space tool to configure bridge netfilter rules in kernel
rubygem-awesome_spawn.noarch : A module that provides some useful features over Ruby's Kernel.spawn
embree.x86_64 : Collection of high-performance ray tracing kernels developed at Intel
embree2.x86_64 : Collection of high-performance ray tracing kernels developed at Intel
kmod-wireguard.x86_64 : Metapackage which tracks in wireguard kernel module for newest kernel
kmod-crystalhd.x86_64 : Metapackage which tracks in crystalhd kernel module for newest kernel
kmod-VirtualBox.x86_64 : Metapackage which tracks in VirtualBox kernel module for newest kernel
nvidia-modprobe.x86_64 : Load the NVIDIA kernel module and create NVIDIA character device files
libsoc.i686 : Interface with common SoC peripherals through generic kernel interfaces
libsoc.x86_64 : Interface with common SoC peripherals through generic kernel interfaces
kmod-ndiswrapper.x86_64 : Metapackage which tracks in ndiswrapper kernel module for newest kernel
kmod-nvidia-340xx.x86_64 : Metapackage which tracks in nvidia-340xx kernel module for newest kernel
kmod-nvidia-390xx.x86_64 : Metapackage which tracks in nvidia-390xx kernel module for newest kernel
nfs-utils.x86_64 : NFS utilities and supporting clients and daemons for the kernel NFS server
kmod-xtables-addons.x86_64 : Metapackage which tracks in xtables-addons kernel module for newest kernel
linuxconsoletools.x86_64 : Tools for connecting joysticks & legacy devices to the kernel's input subsystem
crash.x86_64 : Kernel analysis utility for live systems, netdump, diskdump, kdump, LKCD or mcore dumpfiles
crash-devel.i686 : kernel crash analysis utility for live systems, netdump, diskdump, kdump, LKCD or mcore dumpfiles
crash-devel.x86_64 : kernel crash analysis utility for live systems, netdump, diskdump, kdump, LKCD or mcore dumpfiles
iucode-tool.x86_64 : iucode_tool is a program to manipulate microcode update collections for Intel i686 and X86-64 system processors, and prepare them for use by the
                   : Linux kernel

I understand nothing.

On the other hand, I have been with the following message for several days:

Message from syslogd@localhost at May 3 13:00:22 ...
sssd[kcm][4281]:Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Broadcast message from systemd-journald@localhost.localdomain (Sun 2020-05-03 13:00:22 -05):
sssd[kcm][4281]: Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Broadcast message from systemd-journald@localhost.localdomain (Sun 2020-05-03 13:00:22 -05):
sssd[kcm][4279]: Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Message from syslogd@localhost at May 3 13:00:22 ...
sssd[kcm][4277]:Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Message from syslogd@localhost at May 3 13:00:22 ...
sssd[kcm][4279]:Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Broadcast message from systemd-journald@localhost.localdomain (Sun 2020-05-03 13:00:22 -05):
sssd[kcm][4273]: Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Message from syslogd@localhost at May 3 13:00:22 ...
sssd[kcm][4269]:Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Message from syslogd@localhost at May 3 13:00:22 ...
sssd[kcm][4273]:Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Broadcast message from systemd-journald@localhost.localdomain (Sun 2020-05-03 13:00:22 -05):
sssd[kcm][4277]: Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio]
Broadcast message from systemd-journald@localhost.localdomain (Sun 2020-05-03 13:00:22 -05):
sssd[kcm][4269]: Could not open file [/var/log/sssd/sssd_kcm.log]. Error: [2][No existe el fichero o el directorio] 

What is going on? :cold_sweat:

I’m here because you reported the same problem I had

and I noticed that our hardware is pretty similar. I only have a Core 2 Duo T4300 (notebook) which is as old as your E3400 (2009/2010) and the rest of the hardware is the same. Maybe is some issue with the integrated GPU?.
I’m running Fedora 32 so it’s not related to the fedora version. I’m running MATE Desktop so it’s not DE-related.
I’m running a newer version of the kernel (5.6.8-300.fc32.x86_64). With this version tha I updated yesterday, I haven’t had any other freeze in the last 2 days

1 Like

Does “LANG=C abrt-cli list” in a terminal give something interesting?

My system has just frozen once again. Here is some information that the journalctl command gives me:

journalctl -p3
-- Logs begin at Mon 2020-05-04 08:54:29 -05, end at Mon 2020-05-04 13:57:24 -05. --
may 04 08:54:29 localhost.localdomain kernel: usbhid 4-2:1.1: couldn't find an input interrupt endpoint
may 04 13:54:56 localhost.localdomain auditd[711]: Could not open dir /var/log/audit (No such file or directory)
may 04 13:54:56 localhost.localdomain systemd[1]: Failed to start Security Auditing Service.

journalctl -p2
-- Logs begin at Mon 2020-05-04 08:54:29 -05, end at Mon 2020-05-04 13:57:24 -05. --
-- No entries --

journalctl
-- Logs begin at Mon 2020-05-04 08:54:29 -05, end at Mon 2020-05-04 13:57:24 -05. --
may 04 08:54:29 localhost.localdomain kernel: microcode: microcode updated early to revision 0xa0b, date = 2010-09-28
may 04 08:54:29 localhost.localdomain kernel: Linux version 5.6.8-200.fc31.x86_64 (mockbuild@bkernel03.phx2.fedoraproject.org) (gcc version 9.3.1 20200408 (Red Hat 9.3>
may 04 08:54:29 localhost.localdomain kernel: Command line: BOOT_IMAGE=(hd0,msdos5)/vmlinuz-5.6.8-200.fc31.x86_64 root=/dev/mapper/fedora_localhost--live-root ro resum>
may 04 08:54:29 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
may 04 08:54:29 localhost.localdomain kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
may 04 08:54:29 localhost.localdomain kernel: x86/fpu: Enabled xstate features 0x3, context size is 576 bytes, using 'standard' format.
may 04 08:54:29 localhost.localdomain kernel: BIOS-provided physical RAM map:
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000cdd9ffff] usable
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000cdda0000-0x00000000cddadfff] ACPI data
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000cddae000-0x00000000cddeffff] ACPI NVS
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000cddf0000-0x00000000cddfffff] reserved
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x00000000fff00000-0x00000000ffffffff] reserved
may 04 08:54:29 localhost.localdomain kernel: BIOS-e820: [mem 0x0000000100000000-0x000000012fffffff] usable
may 04 08:54:29 localhost.localdomain kernel: NX (Execute Disable) protection: active
may 04 08:54:29 localhost.localdomain kernel: SMBIOS 2.5 present.
may 04 08:54:29 localhost.localdomain kernel: DMI: QBEX Electronics Corp. O.E.M/G41MXE/G41MXE-K, BIOS 080015  10/14/2010
may 04 08:54:29 localhost.localdomain kernel: tsc: Fast TSC calibration using PIT
may 04 08:54:29 localhost.localdomain kernel: tsc: Detected 2599.943 MHz processor
may 04 08:54:29 localhost.localdomain kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
may 04 08:54:29 localhost.localdomain kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
may 04 08:54:29 localhost.localdomain kernel: last_pfn = 0x130000 max_arch_pfn = 0x400000000
may 04 08:54:29 localhost.localdomain kernel: MTRR default type: uncachable
may 04 08:54:29 localhost.localdomain kernel: MTRR fixed ranges enabled:
may 04 08:54:29 localhost.localdomain kernel:   00000-9FFFF write-back
may 04 08:54:29 localhost.localdomain kernel:   A0000-BFFFF uncachable
may 04 08:54:29 localhost.localdomain kernel:   C0000-CFFFF write-protect
may 04 08:54:29 localhost.localdomain kernel:   D0000-DFFFF uncachable
may 04 08:54:29 localhost.localdomain kernel:   E0000-EFFFF write-through
may 04 08:54:29 localhost.localdomain kernel:   F0000-FFFFF write-protect
may 04 08:54:29 localhost.localdomain kernel: MTRR variable ranges enabled:
may 04 08:54:29 localhost.localdomain kernel:   0 base 000000000 mask F00000000 write-back
may 04 08:54:29 localhost.localdomain kernel:   1 base 100000000 mask FE0000000 write-back
may 04 08:54:29 localhost.localdomain kernel:   2 base 120000000 mask FF0000000 write-back
may 04 08:54:29 localhost.localdomain kernel:   3 base 0D0000000 mask FF0000000 uncachable
may 04 08:54:29 localhost.localdomain kernel:   4 base 0E0000000 mask FE0000000 uncachable
may 04 08:54:29 localhost.localdomain kernel:   5 base 0CDE00000 mask FFFE00000 uncachable
lines 1-41

Any ideas?

I have the same kernel and my system just freezes once again.

LANG=C abrt-cli list
Id         9076e72  
Component  kf5-kglobalaccel  
Count      1  
Time       2020-04-27 13:09:04  
User id    1000 (user)  
             
Id         d4d9bee  
Component  kf5-kglobalaccel  
Count      1  
Time       2019-11-28 15:56:25  
User id    0 (root)  
             
Id         3d5d92c  
Component  stacer  
Count      7  
Time       2019-12-27 12:41:41  
User id    1000 (user)  
             
Id         888ab88  
Component  kernel  
Count      1  
Time       2019-12-20 12:44:20  
           No se puede informar  
           La traza inversa no contiene suficientes marcos de función significativos para ser reportado. Es molesto pero no necesariamente señala un problema con tu computadora. ABRT no permitirá la creación del reporte en sistema de rastreo de errores; pero puedes contactar a los mantenedores del kernel por correo electrónico.  
             
Id         951f824  
Component  yacreader  
Count      1  
Time       2020-03-31 13:57:45  
User id    1000 (user)

Try “abrt-cli list” as suggested by @pauld in my other thread

EDIT: I’ve wrote while you were posting the results. Let’s wait for some more expert opinion, but I see “old dates” in this report. The most recent is March 31…

You can try too boot with an older kernel. At the boot, choose the oldest kernel you can

Those are the reports the system gives me. I don’t understand anything; I’ve never asked for them before.

As for the kernel, the oldest one is 5.6.6 and it’s not even a week old. The kernels have been updated a lot lately. With both 5.6.6 and 5.6.7, the problem was the same. In fact the problem comes from some kernel of the 5.5.1x family.

Ah, finally, I do see a difference between our kernels: mine has a 200 after 8 and yours has a 300.

Indeed the “abrt-cli list” command does not show something recent mentioned. Frankly I am not too surprised because of the symptoms: total freeze. To be honest, even myself, if the freeze are not too frequent I tend to not search to much because I don’t know any obvious way to debug those.

But let’s try to go a bit further, if you accept.

What is the output of “lspci -nnvk”?

sudo part is like optional, but it will give a little more details… and force you to write your password. I removed the sudo before the command, because it can then give serial number of your equipment, which you might not want to make public… and the details givent goes farther that I personally understand about.

Man, I’m sorry for the late response. I’m actually a little down in the dumps and a little frustrated. I also asked for help on Reddit and the final answer I received was that I better change my distro; that Fedora is not for me. I’m sure they think that Fedora is something very exclusive or premium for the common user.

I had considered upgrading my OS to Fedora 32, but seeing the problems @enrico has had, I don’t see it as an option. Besides, I feel that it is too early to upgrade. I prefer to wait a few weeks for some bugs to be reported and fixed so I can have a more stable OS.

I’m following the thread with @enrico, hoping and trusting that the desired solution will appear.

In my last session of a little more than an hour and a half, I didn’t have any freezing. But the use of my PC is completely limited: no more than two open applications, Firefox with only one tab, no music or video players, etc. A rather poor and boring use.

I will continue to report; any news will be reported immediately. For the time being I’ll keep updating the system every day as I usually do, hoping that in one of those at last everything will be solved and my system will return to normal.

Thank you very much for taking a minute of your time to come and read and try to find a solution. :nerd_face:

Okay, Friday, May 8th. A new freeze. Approximately forty minutes after ignition. CPU between 60 and 70%, RAM in less than 2GB. Three applications in use (Dolphin, KTorrent and Firefox); Firefox with four open tabs (including the Spotify web player).

Here is the only command that gives any results:

journalctl -p3
-- Logs begin at Fri 2020-05-08 07:55:27 -05, end at Fri 2020-05-08 12:59:12 -05. --
may 08 07:55:27 localhost.localdomain kernel: usbhid 4-2:1.1: couldn't find an input interrupt endpoint
may 08 12:55:52 localhost.localdomain auditd[708]: Could not open dir /var/log/audit (No such file or directory)
may 08 12:55:52 localhost.localdomain systemd[1]: Failed to start Security Auditing Service.

It’s only been a few minutes and I’ve had another freeze. This time only two applications in use: Dolphin and KTorrent.

Besides downloading a torrent, I was transferring files to a USB stick.

Here the journalctl -p3:

-- Logs begin at Fri 2020-05-08 08:46:22 -05, end at Fri 2020-05-08 13:49:35 -05. --
may 08 08:46:22 localhost.localdomain kernel: usbhid 4-2:1.1: couldn't find an input interrupt endpoint
may 08 13:46:46 localhost.localdomain auditd[707]: Could not open dir /var/log/audit (No such file or directory)
may 08 13:46:46 localhost.localdomain systemd[1]: Failed to start Security Auditing Service.

This should be easily fixable with a dnf reinstall audit.

For the rest of your issues, have you tried ruling out a hardware problem (power, memory) with tools like memtest86+ and prime95? I would start there.
Our kernel test suite could also help you identify problem areas (you don’t need to submit results).

I was holding myself to suggest a memtest because it was discussed on the devel mailing list that the one in the Fedora images, freeze on recent CPUs. But I guess a Celeron E3400 would not be affected… who knows.

https://bugzilla.redhat.com/show_bug.cgi?id=1815742

To be honest… I doubt the answer will show up in the logs.

@enrico seems to have think he upgraded to F32, but seems he did not yet
Upgrading to F32 seems to me the best option for you.

I see I did not help you understand journalctl… you could read “man journalctl” which is what I do… but guess it would help I give you some hints.

journalctl --list-boots
should give you many boot entries… if it give an error it probably means your log are volatile (are erased at every boot) rather than being persistent. And we should help you fix that if it is the case for you.

journalctl --list-boots
give at first column a negative number… 0 or -0 is your current session,
-1 is the previous session,
-2 is the previous session of the previous session,
etc.

So when you reboots because of a freeze, the log with the session that frozed is in the past… -1 if you just rebooted, -2 if you rebooted twice, etc.

And you do things like:
journalctl -b -1
journalctl -b -2
to see these older sessions.

So you have to make a note to yourself of when freeze happens… and looks in journalctl --list-boots entries to find which one contains the session that have frozen.

And then you could send your logs to fpaste web site, with:
journalctl -b -1 --no-pager | fpaste
the -b -1 would means the session before the current one,
-p4 would limit to error messages
–no-pager would make sure it would not wait for you to press keys
| fpaste would send to paste site for 24h the contents…
that should result in a link that you can first check yourself in the browser to make sure it does not contains something you would not wish to publish

There is a more recent version, which is supposed to have better support for newer models, but the regex on Anitya would not pick it up. I’ve updated the filter and it filed a bug against the package.

When I have no other clues and I suspect faulty hardware, I usually start with memtest86+, because it’s relatively fast and easy on the tested system. However, prime95 can catch memory errors that memtest86+ doesn’t.
For the rest of the errors that prime95 reveals, more often than not, it takes a significant amount of work to pinpoint what’s at fault.

I’d like to share this.

It’s from another distro (Manjaro) and this one is Spanish (sorry about that). In short: exactly the same problem. Same symptoms, everything. I was surprised how perfectly described it is. I could copy/paste almost all the content and just change Manjaro for Fedora.

The thread starts in July 17. The last comment is from January this year: there is no solution.

This leads me to think that the problem is not Fedora’s. And from what I have read, this kernel is the main suspect.

I am a simple, ordinary system user. All I want to do is turn on my PC, surf the Internet while listening to music and then watch a movie or read a book. Many of these hypothetical solutions simply outweigh me; my use of commands is basic and limited. Test the kernel? Man, until recently I didn’t even know which version I had installed.

I’ll keep typing some of these commands, pressing enter, and I’ll bring back the results.

I couldn’t find a solution on Reddit either. It’s okay, maybe it’s something extremely particular.

As always, thank you very much for every input. :nerd_face:

Well… the part mention in english seems to suggest to remove the xf86-video-intel driver… which make some sense at first because I think it would then use glamor… Oh well, I do use it on my computer… I’ll try to remove it and will give feedback… If I am able to use may computer again :wink:

I did: sudo dnf remove xorg-x11-drv-intel

I am back… I see that I still use i915 (that’s in the kernel… I tend to confuse those)… Still on Gnome on Wayland… at first glance I see no change. But I need to investigate a bit more… I don’t fully understand what it change.

I do have:

[paul@localhost ~]$ journalctl -b0 -o short-monotonic|grep glamor
[   46.473104] localhost.localdomain org.gnome.Shell.desktop[1259]: glamor: No eglstream capable devices found
[   64.597533] localhost.localdomain gnome-shell[1815]: glamor: No eglstream capable devices found

but it is unclear it is causing problems.

The page on Glamor:
**PLEASE NOTE: Glamor has been [merged](https://cgit.freedesktop.org/xorg/xserver/commit/?id=1d76b02fac79c0360ae201e4d1a8ba0e9a00e810) into Xorg server 1.16 (released July 2014)**
https://www.freedesktop.org/wiki/Software/Glamor/

So yeah… bug could be in: xorg-x11-drv-intel and you probably don’t need it.