So, I recently started using Fedora (and Linux in general) for the first time, and while I have been loving the experience, I have been encountering constant random crashes while working on non-demanding tasks like document editing and web browsing journalctl (I know it exists, I don’t know how to use it), the only thing I can say is that this happens randomly without any particular reason, it sometimes happens after 20 minutes, other times it happens after 8 hours. When this occurs, music keeps playing (if I had any), however not even the CAPS Lock or NUM Lock function at all.
This is my hardware:
16 GB ram
512 storage
AMD Ryzen 7 7735HS with Radeon Graphics
NVIDIA 4050 Laptop GPU
Secure Boot enabled (have tried disabling it)
glb
May 5, 2025, 1:15am
2
It is a command you enter in a terminal app (or on a console if your graphical environment isn’t working). It displays the system’s logs with timestamps and the command has many options to filter the logs to show only certain time periods or the records for certain system services. The only real “trick” to it is that you need to run it with “super user” privileges in order to access all the logs. You do that by prefixing the command with sudo and providing your password when prompted.
You’ll need to take note of the time when a crash occurs and then, when you get your system going again, run something like sudo journalctl --since="2025-05-04 20:00:00" to dump the logs that were recorded at that time and after. You could also add something like --until="2025-05-04 20:05:00" so you only get a few minutes worth of logs.
gnwiii
May 5, 2025, 1:02pm
3
You may find https://LinuxCommand.org useful. I used to run practical sessions for some specialized software that runs on Linux. Since many participants had never used Linux, we found it important to devote an afternoon just learning some command-line basics. The goal was not become command-line experts, just be able to use Linux Command to work with command-line tools.
Random crashes often indicate a hardware problem. Make sure you have the latest UEFI/BIOS firmware and Fedora updates. journalctl will help determine if crashes are associated with a particular software component. If not, then start hardware testing with Fedora’s memtest86+ package.
lakiboom
May 5, 2025, 2:34pm
4
The same story except i’ve got AMD Ryzen 7 8845HS. Last 2 weeks i use “Power Off” button too often. Waiting for next kernel version but I’m running out of patience. Very unstable. 41 was much better.
glb
May 5, 2025, 2:56pm
5
As stated earlier, power management problems tend to be due either to hardware/firmware bugs or it could be something in the kernel/drivers. The problem is unlikely to be in the higher levels of the OS code (i.e. it probably isn’t anything in the “user space” code that makes up Fedora Linux 42).
Have you tried running Fedora Linux 42 on one of the older Linux kernels that came with Fedora Linux 41? You can install an older kernel with sudo dnf --repo=fedora --releasever=41 downgrade kernel\*. You would need to reboot and manually select the older kernel from the boot menu to test it.
HTH.
lakiboom
May 5, 2025, 3:01pm
6
A few minutes ago for example.
Спойлер
мая 05 17:18:59 fedora kernel: slab sock_inode_cache start ffff89a089dd5480 pointer offset 8 size 768#1 ] PREEMPT SMP NOPTI#1 irq_exit_rcu+0x4c/0xf0 >#PF: supervisor instruction fetch in kernel mode#PF: error_code(0x0010) - not-present page#2 ] PREEMPT SMP NOPTI#1 sys_sendto+0x137/0x200 >
glb
May 5, 2025, 3:05pm
7
It looks like you might have added a third-party driver to the kernel. Have you tried running your system without that third-party driver? Did you make sure the third-party driver was compatible with your current kernel version before adding it?
lakiboom
May 5, 2025, 3:10pm
8
Didn’t do anything manually :\ Was Fedora 41 and then upgraded to 42. Only official repos out of the box.
glb
May 5, 2025, 3:12pm
9
There might be other ways the kernel could get marked as tainted. I’m not sure.
In any case, the problem is occurring in the kernel. I would try running the system with a different kernel.