Fedora completely freezes up after a random amount of gaming

ombrezz · June 14, 2024, 11:50pm

I’m starting off here with my system specs. My CPU is an AMD FX-8350 with 16 GB of DDR3, my motherboard is an ASRock 970A-G/3.1 and I have a GTX 970 (proprietary drivers). My system isn’t exactly good, but nonetheless it can run most things on low settings.

I’ve recently started playing Titanfall 2 and my system randomly freezes up and becomes completely unresponsive to any keyboard or mouse inputs. Despite my system not being great, I don’t believe this is a problem related to my system resources running out because I can go through a several hours session just fine, but other times it locks up on the first match, it’s completely random. The worst part is when hard resetting my computer, I have to wait 10 minutes for Fedora to boot from an improper reset (it usually takes a minute to boot after an actual shutdown).

At minimum, I’m hoping to learn some key combination that can reset my system safely even if everything is locked up. If possible it would also be nice to solve this, if I can do that without a hardware upgrade.

I’m also including the journalctl from this boot and the previous two (those two got crashed by the game). Apologies if I made a mistake getting this data, I’m not very familiar with the journalctl command.

Current boot
Previous boot
Boot before that

barryascott · June 16, 2024, 9:50am

Are you using the rpmfusion nvidia drivers?
If not then uninstall the nvidia drivers you are using and try rpmfusion instead.

Can you ssh into the system when it frozen to get some diagnostic information? If so does sudo dmesg have errors?

barryascott · June 16, 2024, 9:51am

Also you are likely to lose the journal of the failure reason.

rinkeby · June 16, 2024, 2:55pm

Hey,

I assume you use proton of sorts. So if you download ProtonPlus as flatpack. You can then install proton made for just Titanfall 2. I dont know if that helps. But if they have a separate proton for just Titanfall, it might solve something.

ombrezz · June 16, 2024, 7:41pm

I am using the RPMFusion drivers, I’ll setup SSH and see if I can trigger the crash again. I’m not too confident though since the system doesn’t even respond to SysRq commands (which I did enable) which makes me think even the kernel is locking up.

ombrezz · June 16, 2024, 9:33pm

Results are in: The SSH server stops working when my PC locks up. Is there any way I can configure dmesg to write to a file upon a kernel panic? Or maybe have the kernel try and spit out some diagnostic data to the screen?

barryascott · June 16, 2024, 9:55pm

I think you need a serial console to see the messages live.
But I have set one up so cannot advise how to do this,

But given you see the machine lock up hard I would suspect a hardware issue. Check that your power supply can meet the power requirements of the GPU.

Edit: Oh you have 970 I don’t think that is very demanding, but check anyway.

ombrezz · June 16, 2024, 10:07pm

My CPU and GPU draw ~150W each, let’s overestimate another ~150W for the rest of my PC’s functions, that’s ~450W. My PSU can supply 650W, it’s safe to say that nothing in my computer is running out of power.

barryascott · June 16, 2024, 10:11pm

You could monitor system temperatures from an ssh session while you play and see if sensors shows high temp anywhere.

ombrezz · June 16, 2024, 10:22pm

I feel like there should be a lot more data than this, is there a driver I’m missing?

fam15h_power-pci-00c4
Adapter: PCI adapter
power1:       45.89 W  (crit = 125.19 W)

k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +51.4°C  (high = +70.0°C)
                       (crit = +70.0°C, hyst = +67.0°C)

barryascott · June 16, 2024, 10:51pm

As root run sensors-detect to configure lm-sensors.
Then see what sensors reports.

ombrezz · June 16, 2024, 10:54pm

Gotcha, there’s way more data now.
Next time I play I’ll set it up with the watch command and see what happens.

gnwiii · June 18, 2024, 1:33pm

This is probably due to repairing filesystems after an improper shutdown. You want to avoid those – sometimes the damage to the filesystem isn’t repairable.

Your journalctl files are no longer available. Journalctl collects an enormous amount of detail but has many options available to filter output to just those relevant to a particular problem, see man journalctl. Start with journalctl --no-hostname -b -<N> -p 4| cat (the | cat) will wrap long lines that the usual display truncates.

ombrezz · June 18, 2024, 11:57pm

Got another crash to trigger, interestingly the watch -n 1 sensors command kept updating after my PC locked up. Though trying to start another SSH connection or trying any other command did not work. Here’s the screenshots.

@gnwiii I also ran the journalctl command for the previous boot that crashed, with the filtering options you gave me the log is small enough to fit in PasteBin so it shouldn’t expire this time. Here’s the link.

Espionage724 · June 19, 2024, 12:07am

I use REISUB! It’s a series of key presses that do actions based on the letters; S is sync, U unmounts drives, and B reboots. I think it’s called Magic sysrq.

On Fedora I enable it with:

echo 'kernel.sysrq = 1' | sudo tee '/etc/sysctl.d/99-sysrq.conf' > '/dev/null'

Hold Alt + Print Screen, then press the letters of REISUB while still holding Alt + Print Screen. I like to spam S a few times to make sure sync is good, and wait like half a second before pressing the next keys.

If sensors was still updating with the computer frozen, it’s possible REISUB will still work.

ombrezz · June 19, 2024, 12:12am

Enabling SysRq was one of the first things I tried and it didn’t respond during the freeze, though I didn’t do all the commands in the acronym (including switching the keyboard mode), so I’ll try that next time.

gnwiii · June 19, 2024, 12:34am

I don’t use PasteBin (due to their cookie policy). Most issues generate only a few lines of key details and can be posted as pre-formatted text.

ombrezz · June 19, 2024, 12:49am

Well, this looks to be some important error related looking stuff at the end, does this help?

Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): CRT-0: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): Samsung S22E200 (DFP-0): connected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): Samsung S22E200 (DFP-0): Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): Samsung S22E200 (DFP-0): 330.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-1: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-2: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-3: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-4: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-5: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-6: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-7: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): CRT-0: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): Samsung S22E200 (DFP-0): connected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): Samsung S22E200 (DFP-0): Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): Samsung S22E200 (DFP-0): 330.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-1: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-1: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-1: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-2: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-3: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-4: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-4: Internal DisplayPort
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-4: 960.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-5: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-5: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-5: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-6: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-6: Internal DisplayPort
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-6: 960.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-7: disconnected
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-7: Internal TMDS
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0): DFP-7: 165.0 MHz maximum pixel clock
Jun 18 18:54:19 /usr/libexec/gdm-x-session[2062]: (--) NVIDIA(GPU-0):
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-0-rescue.conf:7: Unknown line 'grub_users', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-0-rescue.conf:8: Unknown line 'grub_arg', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-0-rescue.conf:9: Unknown line 'grub_class', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.11-300.fc40.x86_64.conf:7: Unknown line 'grub_users', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.11-300.fc40.x86_64.conf:8: Unknown line 'grub_arg', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.11-300.fc40.x86_64.conf:9: Unknown line 'grub_class', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.10-300.fc40.x86_64.conf:7: Unknown line 'grub_users', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.10-300.fc40.x86_64.conf:8: Unknown line 'grub_arg', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.10-300.fc40.x86_64.conf:9: Unknown line 'grub_class', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.9-300.fc40.x86_64.conf:7: Unknown line 'grub_users', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.9-300.fc40.x86_64.conf:8: Unknown line 'grub_arg', ignoring.
Jun 18 18:54:20 systemd-logind[877]: /boot/loader/entries/ed0fdc3ea4084dd58cacee9253444a08-6.8.9-300.fc40.x86_64.conf:9: Unknown line 'grub_class', ignoring.
Jun 18 19:10:55 gnome-shell[2301]: Object .Gjs_ui_messageTray_Notification (0x5640cd6ed180), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                   == Stack trace for context 0x5640ccd86000 ==
                                   #0   5640cce4cef8 i   resource:///org/gnome/shell/ui/messageTray.js:477 (28776a935d80 @ 74)
                                   #1   5640cce4ce50 i   resource:///org/gnome/shell/ui/messageTray.js:473 (28776a935d30 @ 63)
                                   #2   5640cce4cdc8 i   resource:///org/gnome/shell/ui/calendar.js:812 (28776a93f740 @ 22)
                                   #3   5640cce4cd38 i   resource:///org/gnome/shell/ui/init.js:21 (173bac270bf0 @ 48)
Jun 18 19:10:55 gnome-shell[2301]: Object .Gjs_ui_messageTray_Notification (0x5640cd6ed180), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs.
                                   == Stack trace for context 0x5640ccd86000 ==
                                   #0   5640cce4cef8 i   resource:///org/gnome/shell/ui/messageTray.js:478 (28776a935d80 @ 89)
                                   #1   5640cce4ce50 i   resource:///org/gnome/shell/ui/messageTray.js:473 (28776a935d30 @ 63)
                                   #2   5640cce4cdc8 i   resource:///org/gnome/shell/ui/calendar.js:812 (28776a93f740 @ 22)
                                   #3   5640cce4cd38 i   resource:///org/gnome/shell/ui/init.js:21 (173bac270bf0 @ 48)
Jun 18 19:12:03 kernel: BTRFS warning (device sda3): csum failed root 256 ino 1166750 off 43487232 csum 0xbb3c82dd expected csum 0xe6cd9537 mirror 1
Jun 18 19:12:03 kernel: BTRFS error (device sda3): bdev /dev/sda3 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0
Jun 18 19:12:55 packagekitd[17134]: Failed to get cache filename for kernel-devel-matched
Jun 18 19:12:55 packagekitd[17134]: Failed to get cache filename for kernel

@Espionage724 Unfortunately REISUB did not work, and I also tried watching dmesg but this time it stopped updating once my PC locked up so no useful data could appear.

Topic		Replies	Views
Desktop freezing up, requires hard restart \| F40 \| Nvidia Ask Fedora wayland , gnome , nvidia , f40	3	842	July 2, 2024
Random freezes on fedora 36 with AMD GPU Ask Fedora f36 , amd	28	3962	November 10, 2022
Fedora Driver or Flash freezes (CPU Intel 9700k, GPU Nvidia GTX 1080) Ask Fedora	3	835	March 1, 2020
Fedora 31 freezes after login Ask Fedora f31 , gnome , desktop , driver	17	3804	April 8, 2020
Desktop complete freeze up, but can SSH into and restart lightdm, otherwise have to reboot Ask Fedora xfce , nouveau , nvidia	3	2163	October 4, 2019

Fedora completely freezes up after a random amount of gaming

Related topics