System Lockup when Gaming

blgrace · 2025-12-01 06:49:52

I've been trying to troubleshoot this lockup for some time without any success.
The lockup is guaranteed to occur when gaming and at no other time.
Here are the relevant log files :

http://0x0.st/KJQV.txt

http://0x0.st/KJQW.txt

http://0x0.st/KJQ4.txt

http://0x0.st/KJQJ.txt

Thank you for any assistance as I have no idea where to start.
Regards

Last edited by blgrace (2025-12-08 16:34:48)

seth · 2025-12-01 08:43:45

https://bbs.archlinux.org/viewtopic.php … 5#p2275505 ?

blgrace · 2025-12-01 23:48:21

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 5#p2275505 ?

Thank you, I followed the links and information but my issue may be different?
I'm not experiencing "frequent" GPU crashes or consistent system instability.

I cannot reproduce the system lockup by running stress tests:

Stressing the CPU with:

stress-ng --cpu 0 --cpu-method fft --timeout 20m --metrics-brief

does not cause any system freeze or GPU crash. I have run it multiple times without lockups.
What will (eventually) cause the lockup is gaming.

Still no closer to finding the cause.

I don't know if the logs provided offer and clues - I'm not skilled enough to understand them.

seth · 2025-12-02 08:36:15

Does the journal in http://0x0.st/KJQJ.txt cover such lockup?
How hard is such lockup?
Can you still
* switch the VT (ctrl+alt+F3)
* ssh into the system
* Reboot using https://wiki.archlinux.org/title/Keyboa … el_(SysRq) + REISUB ? (nb. you'll have to explicitly enable the feature first!)

Do the keyboard LEDs start to blink?
Do you get a fancy bluescreen w/ a QR code about a kernel panic?

blgrace · 2025-12-02 16:57:54

Hi and Thank you
Here is a log report with most recent system lock-up
http://0x0.st/KyHk.txt

When the lockups happen I can REISUB.
It's more of a freeze I guess - but I can't ALT TAB or do anything besides REISUB.
To be honest, I haven't tried switching into VT

seth · 2025-12-02 20:23:15

To be honest, I haven't tried switching into VT

Oct 31 22:44:21 MAZ systemd[1998]: Started Konsole - Terminal.
Oct 31 22:44:21 MAZ systemd[1998]: Started app-org.kde.konsole-80113.scope.
Oct 31 22:44:24 MAZ systemd[1998]: Activating special unit Exit the Session

it actually looks you started a konsole towards the end of the session?

Can you cause a lockup w/ any of https://aur.archlinux.org/packages?O=0&K=unigine or is it just some steam game?

blgrace · 2025-12-02 23:45:15

I start my steam games with a script that disables sleep while I'm playing and re enables when the game quits.
However, the lockups were happening before I started using the script.
The lockup usually happens when playing Elden Ring because that's what I'm playing right now, but I tested on another title and also eventually got a freeze / lockup requiring REISUB.
I haven't tried any unigine benchmarking progs . . .
I'll report back

Last edited by blgrace (2025-12-03 00:03:35)

blgrace · 2025-12-03 09:17:59

I haven't been able to get my system to freeze by running benchmarking or stress testing.
I used Superposition at extreme settings and I also ran OCCT stress testing on CPU, GPU/VRAM and finally a power stress test.
No lockups.... it's a mystery
What does lock it up is playing Elden Ring or Horizon Zero Dawn . . . so far

seth · 2025-12-03 09:38:39

The journal you posted has no REISUB,

Oct 31 22:23:27 MAZ sudo[54913]:  blgrace : TTY=pts/1 ; PWD=/home/blgrace/Downloads ; USER=root ; COMMAND=/usr/bin/pacman -S --needed wine winetricks wget curl p7zip tar jq zstd
Oct 31 22:29:43 MAZ systemd-coredump[62253]: Process 62234 (mscorsvw.exe) of user 1000 dumped core.
Oct 31 22:31:53 MAZ systemd-coredump[69116]: Process 69099 (mscorsvw.exe) of user 1000 dumped core.
Oct 31 22:39:39 MAZ konsole[54739]: Url QUrl("file:///home/blgrace/Downloads/Affinity x64.exe") already represents a local file, cancelling job.
Oct 31 22:40:54 MAZ konsole[54739]: Url QUrl("file:///home/blgrace/Downloads/Affinity x64.exe") already represents a local file, cancelling job.
Oct 31 22:41:19 MAZ konsole[54739]: QObject::disconnect: Unexpected nullptr parameter
Oct 31 22:41:27 MAZ systemd[1998]: Started Affinity.
Oct 31 22:41:27 MAZ env[78937]: 0048:fixme:seh:WerSetFlags (2) stub
Oct 31 22:41:27 MAZ env[78937]: 0048:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!

…
Oct 31 22:42:00 MAZ systemd[1998]: app-Affinity@d956d5aad6e640919951884f44d8de86.service: Main process exited, code=exited, status=82/n/a
Oct 31 22:43:30 MAZ systemd[1998]: Started Affinity.
Oct 31 22:43:30 MAZ env[79988]: 0088:fixme:seh:WerSetFlags (2) stub
Oct 31 22:43:30 MAZ env[79988]: 0088:fixme:heap:RtlSetHeapInformation HEAP_INFORMATION_CLASS 1 not implemented!
Oct 31 22:43:30 MAZ env[79988]: 0094:fixme:process:SetProcessShutdownParameters (00000380, 00000000): partial stub.
…
Oct 31 22:44:21 MAZ systemd[1998]: Started Konsole - Terminal.
Oct 31 22:44:21 MAZ systemd[1998]: Started app-org.kde.konsole-80113.scope.
Oct 31 22:44:24 MAZ systemd[1998]: Activating special unit Exit the Session...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping app-org.kde.konsole-80113.scope...
Oct 31 22:44:24 MAZ systemd[1998]: Removed slice Slice /app/dbus-:1.1-org.kde.KSplash.
Oct 31 22:44:24 MAZ systemd[1998]: Stopped target Bluetooth.
Oct 31 22:44:24 MAZ systemd[1998]: Stopped target Main User Target.
Oct 31 22:44:24 MAZ systemd[1998]: Stopped target plasma-workspace-wayland.target.
Oct 31 22:44:24 MAZ systemd[1998]: Stopped target Sound Card.
Oct 31 22:44:24 MAZ systemd[1998]: Stopped target Startup of XDG autostart applications.
Oct 31 22:44:24 MAZ systemd[1998]: Closed Socket to launch DrKonqi for a systemd-coredump crash.
Oct 31 22:44:24 MAZ kwin_wayland[2093]: atomic commit failed: Permission denied
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Discover...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Dolphin - File Manager...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Konsole - Terminal...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Steam...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Accessibility services bus...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping dbus-:1.22-org.a11y.atspi.Registry@0.service...
Oct 31 22:44:24 MAZ dbus-broker[2258]: Dispatched 73 messages @ 4(±6)μs / message.
Oct 31 22:44:24 MAZ systemd[1998]: Stopping User preferences database...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping PipeWire PulseAudio...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping KRunner provider for baloo file indexer...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping KRunner...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Xdg Desktop Portal For KDE...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Portal service (GTK/GNOME implementation)...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping Portal service...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping flatpak document portal service...
Oct 31 22:44:24 MAZ systemd[1998]: Stopping sandboxed app permission store...
Oct 31 22:44:24 MAZ kded6[2261]: context kaput
…
Oct 31 22:44:24 MAZ systemd[1998]: plasma-plasmashell.service: Main process exited, code=dumped, status=11/SEGV
Oct 31 22:44:24 MAZ systemd[1998]: plasma-plasmashell.service: Failed with result 'core-dump'.
Oct 31 22:44:24 MAZ systemd[1998]: Stopped KDE Plasma Workspace.
Oct 31 22:44:24 MAZ systemd[1998]: plasma-plasmashell.service: Consumed 36.523s CPU time, 384.1M memory peak.
Oct 31 22:44:24 MAZ systemd[1998]: Stopping KDE Session Management Server...
Oct 31 22:44:24 MAZ systemd[1998]: Stopped KDE Session Management Server.
Oct 31 22:44:24 MAZ systemd[1998]: Stopping KDE Window Manager...
Oct 31 22:44:24 MAZ systemd[1998]: Stopped KDE Window Manager.
Oct 31 22:44:24 MAZ systemd[1998]: plasma-kwin_wayland.service: Consumed 34min 1.710s CPU time, 409.4M memory peak.
Oct 31 22:44:25 MAZ steamwebhelper[80488]: pressure-vessel-wrap[80474]: W: X11 socket /tmp/.X11-unix/X1 does not exist in filesystem, trying to use abstract socket instead.
Oct 31 22:44:25 MAZ dbus-broker-launch[2025]: Activation request for 'org.a11y.Bus' failed.
Oct 31 22:44:25 MAZ steamwebhelper[80488]: pressure-vessel-wrap[80474]: N: Can't find a11y bus: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not activate remote peer 'org.a11y.Bus': activation request failed: unit is invalid
Oct 31 22:44:26 MAZ steamwebhelper[80488]: setlocale "en_US.UTF-8": No such file or directory
Oct 31 22:44:26 MAZ steamwebhelper[80488]: pv-locale-gen: Missing locale en_US.UTF-8
Oct 31 22:44:26 MAZ steamwebhelper[80488]: pv-locale-gen: Generating locale en_AU.UTF-8...
Oct 31 22:44:26 MAZ steamwebhelper[80488]: pv-locale-gen: Generated locale en_AU.UTF-8 successfully
Oct 31 22:44:26 MAZ steamwebhelper[80488]: pv-locale-gen: Generating locale en_US.UTF-8...
Oct 31 22:44:26 MAZ steamwebhelper[80488]: pv-locale-gen: Generated locale en_US.UTF-8 successfully
Oct 31 22:44:26 MAZ steamwebhelper[80488]: pv-adverb[80574]: W: Container startup will be faster if missing locales are created at OS level
Oct 31 22:44:26 MAZ steamwebhelper[80488]: exec ./steamwebhelper -nocrashdialog -lang=en_US -cachedir=/home/blgrace/.local/share/Steam/config/htmlcache -steampid=8778 -buildid=1759461205 -steamid=76561198000816259 -logdir=/home/blgrace/.local/share/Steam/logs -uimode=7 -startcount=2 -steamuniverse=Public -realm=Global -clientui=/home/blgrace/.local/share/Steam/clientui -steampath=/home/blgrace/.local/share/Steam/ubuntu12_32/steam -launcher=0 --valve-initial-threadpool-size=8 --valve-enable-site-isolation --enable-smooth-scrolling --password-store=basic --log-file=/home/blgrace/.local/share/Steam/logs/cef_log.txt --disable-quick-menu --disable-component-update --enable-features=PlatformHEVCDecoderSupport --disable-features=SpareRendererForSitePerProcess,DcheckIsFatal,BlockPromptsIfIgnoredOften,ValveFFmpegAllowLowDelayHEVC
Oct 31 22:44:26 MAZ systemd[1998]: Stopped Steam.
Oct 31 22:44:26 MAZ systemd[1998]: app-steam@9c340c8e623b4b2a85e3c03d6566804f.service: Consumed 23h 25min 42.813s CPU time, 25.7G memory peak.
Oct 31 22:44:26 MAZ systemd[1998]: Stopped target Basic System.
Oct 31 22:44:26 MAZ systemd[1998]: Stopped target Paths.
Oct 31 22:44:26 MAZ systemd[1998]: Stopped Submitting pending crash events (file monitor).
Oct 31 22:44:26 MAZ systemd[1998]: Stopped target Sockets.
Oct 31 22:44:26 MAZ systemd[1998]: Stopped target Timers.
Oct 31 22:44:26 MAZ systemd[1998]: Stopped Cleanup lingering KCrash metadata.
Oct 31 22:44:26 MAZ systemd[1998]: Closed GnuPG network certificate management daemon.
Oct 31 22:44:26 MAZ systemd[1998]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers).
Oct 31 22:44:26 MAZ systemd[1998]: Closed GnuPG cryptographic agent and passphrase cache (restricted).
Oct 31 22:44:26 MAZ systemd[1998]: Closed GnuPG cryptographic agent (ssh-agent emulation).
Oct 31 22:44:26 MAZ systemd[1998]: Closed GnuPG cryptographic agent and passphrase cache.
Oct 31 22:44:26 MAZ systemd[1998]: Closed GnuPG public key management service.
Oct 31 22:44:26 MAZ systemd[1998]: Closed p11-kit server.
Oct 31 22:44:26 MAZ systemd[1998]: Closed PipeWire PulseAudio.
Oct 31 22:44:26 MAZ systemd[1998]: Closed PipeWire Multimedia System Sockets.
Oct 31 22:44:26 MAZ systemd[1998]: Closed Query the User Interactively for a Password.
Oct 31 22:44:26 MAZ dbus-broker[2026]: Dispatched 26514 messages @ 4(±6)μs / message.
Oct 31 22:44:26 MAZ systemd[1998]: Stopping D-Bus User Message Bus...
Oct 31 22:44:26 MAZ systemd[1998]: Stopped D-Bus User Message Bus.
Oct 31 22:44:26 MAZ systemd[1998]: Removed slice User Core Session Slice.
Oct 31 22:44:26 MAZ systemd[1998]: session.slice: Consumed 42min 38.222s CPU time, 894.5M memory peak.
Oct 31 22:44:26 MAZ systemd[1998]: Closed D-Bus User Message Bus Socket.
Oct 31 22:44:26 MAZ systemd[1998]: Removed slice User Application Slice.
Oct 31 22:44:26 MAZ systemd[1998]: app.slice: Consumed 1d 1h 25min 11.512s CPU time, 28.3G memory peak, 280K memory swap peak.
Oct 31 22:44:26 MAZ systemd[1998]: Reached target Shutdown.
Oct 31 22:44:26 MAZ systemd[1998]: Finished Exit the Session.
Oct 31 22:44:26 MAZ systemd[1998]: Reached target Exit the Session.
Oct 31 22:44:26 MAZ (sd-pam)[2016]: pam_unix(systemd-user:session): session closed for user blgrace

It might be useful to see a journal that actually covers such "freeze", doesn't seem to be the hardware/kernel?

blgrace · 2025-12-03 17:54:10

I get a message that the files were truncated . . .
I cleaned up my logs
Here's another log that includes the last 2 boots:
http://0x0.st/KyxS.txt
Thank you

Here is another log that should include my last lockup / crash/freeze

http://0x0.st/Ky69.txt

Last edited by blgrace (2025-12-03 20:57:21)

seth · 2025-12-03 22:28:17

http://0x0.st/Ky69.txt is only 2 minutes, http://0x0.st/KyxS.txt covers Nov 26th - Nov 27th
Neither has any sysrq, nor drm, i915 or amdgpu issues, no kernel panics, oopses or even warnings.

Reboot.
Cause the crash.
Reboot w/ sysrq+REISUB (wait 3 seconds between each step) and from the next boot

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st # nb. the "-1" for the previous boot

Virus1x · 2025-12-04 12:55:35

Sounds like your GPU or driver crashed. Check your system temps, update your graphics drivers, and maybe try using a different kernel to figure out what's causing the trouble.

blgrace · 2025-12-04 19:41:57

seth wrote:

http://0x0.st/Ky69.txt is only 2 minutes, http://0x0.st/KyxS.txt covers Nov 26th - Nov 27th
Neither has any sysrq, nor drm, i915 or amdgpu issues, no kernel panics, oopses or even warnings.
Reboot.
Cause the crash.
Reboot w/ sysrq+REISUB (wait 3 seconds between each step) and from the next boot
sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st # nb. the "-1" for the previous boot

Hi, thanks again.
Here's the log

http://0x0.st/KtpG.txt

blgrace · 2025-12-04 19:46:43

Virus1x wrote:

Sounds like your GPU or driver crashed. Check your system temps, update your graphics drivers, and maybe try using a different kernel to figure out what's causing the trouble.

I was of the belief that my GPU driver was crashing also, but I don't know how to trouble shoot it properly.
I have tried running LTS and still the problem persists.
My GPU hardly breaks a sweat when playing most games. Temperatures (CPU and GPU) are fine, I use Mangohud to keep an eye on such things - - - It's a mystery to me.
(waves feathers over a pile of sacred ashes and hopes for the best)

seth · 2025-12-04 19:58:19

Dec 05 05:24:44 MAZ steam[121673]: ProtonFixes[169736] INFO: Using global protonfix for "ELDEN RING" (1245620

Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card2/device/devcoredump/data
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=12222298, emitted seq=12222300
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu:  Process eldenring.exe pid 169874 thread vkd3d_queue pid 170095
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
…
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card2/device/devcoredump/data
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=12222377, emitted seq=12222379
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu:  Process plasmashell pid 16849 thread plasmashel:cs0 pid 16860
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
Dec 05 06:27:29 MAZ kernel: amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset

You're getting this every 10s for 7m approaximately 1h into the game - sounds right?

There seems to be an intel IGP w/ no monitors attached - can you disable that in the BIOS/UEFI?

Dec 05 06:20:29 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card2/device/devcoredump/data

AMD is gonna want to see that data - can you ssh into the system resp. just kill the display server and/or switch to a different VT to copy that into a permanent file ?

blgrace · 2025-12-04 21:22:08

I will disable IGP in UEFI . . .
/devcoredump/data <---- no such file or directory

Path only goes as far as: /sys/class/drm/card2/device/

seth · 2025-12-04 21:22:43

You'll only get that *after* a crash.

blgrace · 2025-12-04 23:59:20

seth wrote:

You'll only get that *after* a crash.

Thanks for the help
I disabled IGP
just had another lockup - still no data in /sys/class/drm/card2/device/

Here's the log
http://0x0.st/KtxY.txt

blgrace · 2025-12-05 04:45:27

Crashed again and log says :

[drm] AMDGPU device coredump file has been created
Dec 05 15:36:10 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Dec 05 15:36:10 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=3469852, emitted seq=3469855
Dec 05 15:36:10 MAZ kernel: amdgpu 0000:03:00.0: amdgpu:  Process eldenring.exe pid 42786 thread vkd3d_queue pid 43007
Dec 05 15:36:10 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Dec 05 15:36:10 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
Dec 05 15:36:10 MAZ kernel: amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Dumping IP State Completed
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] AMDGPU device coredump file has been created
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: [drm] Check your /sys/class/drm/card1/device/devcoredump/data
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 timeout, signaled seq=3469853, emitted seq=3469857
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu:  Process eldenring.exe pid 42786 thread vkd3d_queue pid 43007
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Starting gfx_0.0.0 ring reset
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: amdgpu: Ring gfx_0.0.0 reset succeeded
Dec 05 15:36:21 MAZ kernel: amdgpu 0000:03:00.0: [drm] device wedged, but recovered through reset

But there is no such file or directory.

seth · 2025-12-05 10:13:33

Did you reboot after the crash?
That "file" will not survive a reboot.

blgrace · 2025-12-05 22:38:09

seth wrote:

Did you reboot after the crash?
That "file" will not survive a reboot.

IC, I'm doing REISUB, that explains it I guess

I will try to access the log without rebooting through VT or ssh next time it occurs
Thanks

blgrace · 2025-12-06 20:14:13

ok, so this is the coredump from amdgpu for the last crash

https://0x0.st/Kvmt.txt
If it's useful, how would I go about sharing with the amdgpu people?
cheers

seth · 2025-12-06 20:46:05

https://gitlab.freedesktop.org/drm/amd/-/issues/
Have you already tried mesa 1:25.3.1-2 ?

blgrace · 2025-12-07 00:10:48

seth wrote:

https://gitlab.freedesktop.org/drm/amd/-/issues/
Have you already tried mesa 1:25.3.1-2 ?

Yes, currently running that version:

pacman -Qi mesa
Name            : mesa
Version         : 1:25.3.1-2
Description     : Open-source OpenGL drivers

seth · 2025-12-07 21:16:58

Ftr, https://gitlab.freedesktop.org/drm/amd/-/issues/4761

Arch Linux

#1 2025-12-01 06:49:52

System Lockup when Gaming

#2 2025-12-01 08:43:45

Re: System Lockup when Gaming

#3 2025-12-01 23:48:21

Re: System Lockup when Gaming

#4 2025-12-02 08:36:15

Re: System Lockup when Gaming

#5 2025-12-02 16:57:54

Re: System Lockup when Gaming

#6 2025-12-02 20:23:15

Re: System Lockup when Gaming

#7 2025-12-02 23:45:15

Re: System Lockup when Gaming

#8 2025-12-03 09:17:59

Re: System Lockup when Gaming

#9 2025-12-03 09:38:39

Re: System Lockup when Gaming

#10 2025-12-03 17:54:10

Re: System Lockup when Gaming

#11 2025-12-03 22:28:17

Re: System Lockup when Gaming

#12 2025-12-04 12:55:35

Re: System Lockup when Gaming

#13 2025-12-04 19:41:57

Re: System Lockup when Gaming

#14 2025-12-04 19:46:43

Re: System Lockup when Gaming

#15 2025-12-04 19:58:19

Re: System Lockup when Gaming

#16 2025-12-04 21:22:08

Re: System Lockup when Gaming

#17 2025-12-04 21:22:43

Re: System Lockup when Gaming

#18 2025-12-04 23:59:20

Re: System Lockup when Gaming

#19 2025-12-05 04:45:27

Re: System Lockup when Gaming

#20 2025-12-05 10:13:33

Re: System Lockup when Gaming

#21 2025-12-05 22:38:09

Re: System Lockup when Gaming

#22 2025-12-06 20:14:13

Re: System Lockup when Gaming

#23 2025-12-06 20:46:05

Re: System Lockup when Gaming

#24 2025-12-07 00:10:48

Re: System Lockup when Gaming

#25 2025-12-07 21:16:58

Re: System Lockup when Gaming

Board footer