I installed Fedora on my older laptop(details further below). While setting it up I had no freezes at all. Today I decided to install an emulator(eden switch emulator) and play some games. The laptop froze after 5mins thrice and I think that it freezes on high CPU or GPU load.
I am a linux newbie so I googled how to investigate why it crashed and on a reddit post it was recommended to run journalctl -b -1 -p 3 and this is the output but I don’t understand most of it and wanted to ask for help here. I also downloaded X11 and switched it on the user login screen but it crashes on that desktop manager or how its called as well. I enabled the magic keys on the first crash but somehow I could not make it work and I reset my laptop by holding the power button but maybe I used the wrong keys to trigger reisub I tried with CTRL/Fn/Alt but I saw that there are other combinations as well that I didnt test yet. Also I waited multiple minutes the freeze didnt go away and I could not switch to another virtual console(CTRL+ALT+F3) while it was frozen. Asking an LLM recommended to update my bios but I am already on latest bios version according to the official acer site.
Nov 28 15:38:55 kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[4] not in IVRS table
Nov 28 15:38:55 kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[5] not in IVRS table
Nov 28 15:38:55 kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
Nov 28 15:38:55 kernel: AMD-Vi: Disabling interrupt remapping
Nov 28 15:38:55 kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0x8f771000-0x8f774fff]
Nov 28 15:38:55 kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Nov 28 15:39:40 systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
Nov 28 15:39:40 systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
Nov 28 15:39:44 kernel: i2c i2c-4: SMBus Timeout!
Nov 28 15:39:44 kernel: i2c i2c-4: Failed reset at end of transaction (01)
Nov 28 15:39:44 kernel: i2c i2c-4: Failed! (01)
Nov 28 15:40:27 systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
Nov 28 15:40:27 systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
Nov 28 15:40:28 bluetoothd[1209]: Failed to set mode: Failed (0x03)
Nov 28 15:40:53 bluetoothd[1209]: Failed to set mode: Failed (0x03)
Nov 28 15:43:16 sudo[5824]: gg : a password is required ; TTY=pts/1 ; PWD=/home/gg ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda
Nov 28 15:45:47 sudo[6078]: pam_systemd(sudo:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
Nov 28 15:53:37 kscreenlocker_greet[6868]: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!
Nov 28 16:04:13 sudo[7968]: pam_systemd(sudo:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
Nov 28 16:08:30 sudo[9618]: pam_systemd(sudo:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
System details:
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.8-300.fc43.x86_64 (64-bit)
Graphics Platform: X11
Processors: 8 × AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx
Memory: 8 GiB of RAM (6.7 GiB usable)
Graphics Processor: AMD Radeon Vega 8 Graphics
Manufacturer: Acer
Product Name: Swift SF315-41
System Version: V2.12
Thank you for the response!
I installed the plasma x11 package or how its called to switch to it but since it didnt work anyway I switched back to wayland and removed the package. That was one of the solutions that I found while googling the error lines one by one.
Some lines from journalctl end in > which indicates they were truncated. You can get the complete lines (and omit hostname which we don’t need) using journalctl --no-hostname --no-pager ... per:
% man journalctl | grep hostname
--no-hostname
Do not show the hostname field of log messages. This switch has an effect only on the short family of output
Note: this option does not remove occurrences of the hostname from log entries themselves, so it does not
prevent the hostname from being visible in the logs.
There isn’t much in the journalctl output. The tpm messages are normal for older systems, but the
may indicate a hard drive (hd) issue. Try checking drive health with Gnome disks.
Nov 28 15:38:55 kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[4] not in IVRS table
Nov 28 15:38:55 kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[5] not in IVRS table
Nov 28 15:38:55 kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
Nov 28 15:38:55 kernel: AMD-Vi: Disabling interrupt remapping
Nov 28 15:38:55 kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0x8f771000-0x8f774fff]
Nov 28 15:38:55 kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Nov 28 15:39:40 systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
Nov 28 15:39:40 systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
Nov 28 15:39:44 kernel: i2c i2c-4: SMBus Timeout!
Nov 28 15:39:44 kernel: i2c i2c-4: Failed reset at end of transaction (01)
Nov 28 15:39:44 kernel: i2c i2c-4: Failed! (01)
Nov 28 15:40:27 systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
Nov 28 15:40:27 systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
Nov 28 15:40:28 bluetoothd[1209]: Failed to set mode: Failed (0x03)
Nov 28 15:40:53 bluetoothd[1209]: Failed to set mode: Failed (0x03)
Nov 28 15:43:16 sudo[5824]: gg : a password is required ; TTY=pts/1 ; PWD=/home/gg ; USER=root ; COMMAND=/sbin/hddtemp -nq -u C /dev/sda
Nov 28 15:45:47 sudo[6078]: pam_systemd(sudo:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
Nov 28 15:53:37 kscreenlocker_greet[6868]: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration!
Nov 28 16:04:13 sudo[7968]: pam_systemd(sudo:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
Nov 28 16:08:30 sudo[9618]: pam_systemd(sudo:session): Failed to check if /run/user/0/bus exists, ignoring: Permission denied
I also installed gnome-disks and ran the benchmark and the three self tests it has. There was not a single error while running the three tests and the assessment was reported as OK.
I am wondering if it might be a good idea to use journalctl to take a snapshot of what is happening at the time of the crash using the -S and -U options as explained in the third post of this thread…
Also you can use the -b1 option if you reboot and want to look at what happened previously in the last session. And finally the -p err option to get only error information…
Edit: I just went back and looked at your first post and saw that you were aware of the -b1 option already. However, I think that the timestamp option might give you the ability to narrow down the messages to the time of the crash. Also using -p err can narrow things down to error messages…
Just to clarify, the -p 3 argument I used in my initial command is equivalent to -p err . The output appeared bloated mainly due to the hostname-related entries.
The system crashed again today and I can reliably reproduce the crash by playing a video game.
After searching for my laptop model online, I found similar reports on other Linux distributions. The issue seems exclusive to Linux, as Windows users with the same hardware are not experiencing it. This could be a kernel? bug.
For testing, I even ran a emulator and configured it to run with memory leaks to check if it might happen when the memory is full but no freeze happened.
I believe it is either the GPU or an CPU/Kernel interaction but I don’t know how to pinpoint the crash further.
Here is the most recent log but it is almost identical as the one above:
gg@fedora-2:~$ sudo journalctl -b -1 -p 3 --no-hostname --no-pager
[sudo] password for gg:
Nov 29 10:28:33 kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[4] not in IVRS table
Nov 29 10:28:33 kernel: AMD-Vi: [Firmware Bug]: : IOAPIC[5] not in IVRS table
Nov 29 10:28:33 kernel: AMD-Vi: [Firmware Bug]: : No southbridge IOAPIC found
Nov 29 10:28:33 kernel: AMD-Vi: Disabling interrupt remapping
Nov 29 10:28:33 kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0x8f771000-0x8f774fff]
Nov 29 10:28:33 kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Nov 29 10:29:18 systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
Nov 29 10:29:18 systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
Nov 29 10:29:22 kernel: i2c i2c-4: SMBus Timeout!
Nov 29 10:29:22 kernel: i2c i2c-4: Failed reset at end of transaction (01)
Nov 29 10:29:22 kernel: i2c i2c-4: Failed! (01)
Nov 29 10:30:06 systemd[1]: Timed out waiting for device dev-tpm0.device - /dev/tpm0.
Nov 29 10:30:06 systemd[1]: Timed out waiting for device dev-tpmrm0.device - /dev/tpmrm0.
Nov 29 10:30:06 bluetoothd[1189]: Failed to set mode: Failed (0x03)
Nov 29 10:31:07 bluetoothd[1189]: Failed to set mode: Failed (0x03)
Hardware vendors put a lot of effort into Windows support, while Linux often relies on the user community to find bugs and create detailed reports that allow linux devs to fix issues with hardware they don’t have. For older hardware there may be kernel command-line options that work around bugs in hardware firmware that vendors won’t fix, or newer replacements for removable components.
It has become more difficult to find workarounds and kernel options for specific bugs due to the mass of clickbait AI sites promising easy fixes and the number of AI scrapers overloading quality sites.