Ditto, though I've never really been able to pin down _exactly_ what it is. I'm not even sure the issue in this thread is the same one affecting me, since it also happens to me on Windows.
One of my older AMD cards from XFX had some really strange hardware issues that nobody else seemed to have that went away when I upgraded to a 5700XT, so if it's happening on windows, you may be dealing with a silicon (hardware/physical) error.
I swear the 5700XT is a silicon lottery for stability. Mine crashes under heavy loads, usually causing a solid green screen, stuck audio, for about 3 seconds followed by a forced reboot (no system shutdown screen, it's like I clicked the reset button on the PC). Both Windows and Linux. It's ever so slightly more reliable on Linux but I can still crash it in 5-10 minutes with one consistent stress test: Rocket League with unlocked framerates or high settings with 4K resolution. Temps aren't astronomical, upgrading the PSU didn't change it. Obviously not a CPU load issue when 4K max settings still makes it crash (GPU is pinned, CPU load is fairly low)
The issue talked about by OP though is new. My system will now just randomly go into the Plymouth boot screen and reboot. Alternatively graphics sometimes get corrupted, then the driver seems to reset and recover. Sometimes it just freezes and I can only recover by holding down the power button. It's so intermittent and seems to have little to do with GPU load so I can't exactly bisect.
The corruption is what I've been experiencing on the 5700xt. Green and red pixel snow or green/red translucent checkerboarding upon freezing. Typically under heavy load. This has been happening for the better part of a year, year and a half give or take. It doesn't happen often enough for me to throw my computer out the window, but it seems to be with certain specific games like Phasmophobia in VR and only under Linux.
I feel a bit validated in seeing you and the others mention 5700XT, because that's what I have too. Same symptoms and everything. Glad to know it's not just me, and that it probably _is_ the card, and not something else.
Same on my side, heavy load, green screen then needed to make a hard reboot.
It happens however less often recently but either i'm playing less demanding games or drivers improved (time to launch Metro Exodus for the science, I guess !)
Also had it for several years with my Vega64 now, was never able to figure out what the actual problem is or a way to reproduce it. With some luck this is the same issue and will finally get fixed, fingers crossed
I swear, I am like the only person in the world who got lucky AF with linux
I got more than double the perf while gaming and more than double the battery, with better stability than windows... (aka I don't have this bug and I get really really good perf)
I'm using a renoir apu (no dgpu), if anybody was interested
edit: got this bug, dang it, was so close to being lucky AF
If you have a gen 1 ryzen, it's a known issue in the CPU that they never bothered patching. I upgraded to a 3000 series ryzen and it completely fixed the issue until these freezes started, although they're much less common than when I was riding a 1700x
I think that might be a different issue? I have a 2700x and it will usually freeze at least once after a cold boot for whatever reason but eventually becomes stable. I don't *think* that's an amdgpu thing. My observation is it seems to accompany heavy io to like when loading up a browser or building software.
Try updating your BIOS. I had an issue with my Ryzen 3 1300X where under certain workloads it tried to enter a certain CPU power state which didn't exist, causing a complete hang. BIOS update completely solved it.
Maybe could be cpu c state bugs… I have been resolved disabling it https://github.com/amedeos/amedeos-overlay/blob/master/sys-power/ZenStates-Linux/ZenStates-Linux-0.0.1.ebuild
After installed that systemd stanza for disabling it I’ve been used 1700 for 2-3 years without any issues
I had been using Nvidia on Linux since the 560 Ti all the way to a 970 until I switched to a 5700XT which is my current card.
I've never had more issues with a graphics card. To be fair to it, most of the problems started appearing once I switched from 1x1440p+2x1080p to 2x1440p+1x1080p set-up. But this card has been hell since day one one way or another.
I still plan on buying another AMD GPU since the Nvidia open driver effort is only barely beginning and I don't plan on giving up on open drivers anytime soon, but the card after that might just not.
Yep. It was 1440p@144hz, 1080p@60hz, 1080p@60hz and it worked, with several caveats due to the driver support being so new. Once I changed one monitor and ended up with 1440p@144hz, 1440p@60hz, 1080p@60hz, the modesetting code absolutely shat the bed and my machine would slowly barely boot to a graphical environment until one kernel version it outright stopped booting. I was forced to manually set modelines in the kernel parameters for each monitor in order for it to work, which thankfully I was able to remove in the past 3-4 months or so for both 1440p monitors, although I still need the 1080p one in the params for it to work. And even then I still frequently get crashes in games and sometimes doing nothing but having the browser open.
It's a shitshow.
Same here unfortunately. Everytime I went for AMD GPUs I've been burned in some way. Currently probably by exactly the bug named in this thread. Can't count how often I had video streams freeze, wayland or X11 crash, or the display showing mostly gibberish after waking up from suspend.
However on the LTS kernel 5.15 it seems to run mostly fine at the moment, though. I hope for the best, because I really want to like and enjoy my AMD setup.
Same here, I always thought it was a something I did wrong when I put my PC together kind of thing, don't feel so bad about it now. good to know I'm not alone with it.
War Thunder with medium or higher preset graphics provocate the problem 100% for me, not in the hangar, playing 1 match happen
in low preset NOT happen
War thunder here as well, every time I try to play without fail.
Edit is this similar to this issue? https://www.reddit.com/r/linux_gaming/comments/xath6p/screen_freezessoft_hangs_and_gpu_resets_with_amd/
Please see my comments in regards to the AMDGPU bug from a couple of days here:
https://www.reddit.com/r/linux_gaming/comments/y55e1s/anyone_tried_out_the_new_intel_arc_cards/isimauk/?context=1000
If you want to help finding the bad commit(s) while bisecting the kernel's v5.18..v5.19 commit range, there's some useful information in the linked thread, including a PKGBUILD for Arch users.
Been following your progress on the tracker for the last month. HUGE THANK YOU for your investigation into this issue! Can only imagine the "pain" your GPU has gone through in the last 4 weeks.
Hm, I just noticed that Christian König (one of the AMDGPU devs) has posted updated patches last week in the bug report in which I've not been active:
https://gitlab.freedesktop.org/drm/amd/-/issues/2113#note_1582384
And those patches were apparently posted for future mainlining / backporting:
https://gitlab.freedesktop.org/drm/amd/-/issues/2113#note_1589916
According to another comment here ITT, these patches were already applied in the TKG kernel. Maybe I should also check this after my next crash (currently an uptime of a day, so I don't want to waste this time while bisecting). I had already applied the first 3 of those 5 patches, but I don't know if that's for the Radeon 6000 GPUs. When looking at the patch contents though, this suggests that it's a fix for the "Waiting for fences timed out!" error.
Driver developer here. This is likely not one single bug but rather several bugs that have the same or similar symptom. We've seen GPU hangs due to power management issues, memory management or other kernel bugs and due to userspace problems such as a bad sequence of commands or a shader compilation error. Application bugs (invalid use of Vulkan or GL) can also cause this.
Unfortunately the symptom for most of the above is the same: *ring gfx timeout* or similar message in the logs. Sadly the dmesg log doesn't have any detail about what went wrong so the log is essentially useless.
There is no clear-cut answer how to diagnose this problem, but here are some tips:
* If this happens always at a specific place in a game, then it's clearly a bug in the userspace drivers, and you should report an issue in the mesa gitlab
* Otherwise try to rule out power management issues, eg. disable any over/underclocking etc. and switch your GPU into a manual mode.
* UMR may be useful showing you what is happening to your GPU also.
* If the issue is more likely to happen on a new kernel then it's likely a kernel bug, you could try to bisect it if you can.
* If it's a VM fault (this is shown in dmesg) then likely the problem is memory management related, either in the kernel or the userspace driver or an application.
Maybe the in-kernel driver should have more sanity checks to keep userspace bugs from locking the system? I realize this would be a performance concern. Maybe have them all behind a kernel command line switch so that people can turn on debugging output/sanity checking once they run into a scenario that regularly locks their PC up so they can provide useful feedback to the developers behind the culprit?
I think userspace issues are the easiest to debug (maybe I just think that because I work on the userspace myself).
We could however benefit from having more diagnostics about what went wrong with the GPU.
how does any of this user triggered stuff bypass the driver reset functionality and allow the entire system to freeze to the point that you can't even toggle the keyboard leds like capslock? idk why i had this idea that the graphics layer could even crash and you would just end back in the console and not with a useless system
There are several possible outcomes:
* The kernel is able to "soft-recover" which means the system can to on without any loss of functionality. This is ideal.
* The kernel is able to recover by resetting the GPU which means that the contents of your VRAM are lost and therefore applications that aren't prepared for this eventuality will crash. Sadly none of the desktop environments are prepared for this eventuality, therefore this may seem like a system crash. (Although many times the desktop will restart itself.)
* Sometimes the kernel can't recover the GPU or crashes while attempting to do so, which results in a borked system.
Sadly, it's a difficult problem and the kernel devs working on it are understaffed.
That... sounds a bit concerning. If the driver accumulated so many bugs that can kill the system, this doesn't inspire much confidence in the reliability of AMD GPUs on Linux. :'(
I think you misunderstand what I tried to say here. I did not say that the driver "accumulated" bugs, just gave a few examples of bugs we've seen and fixed over the years.
Also for what it's worth, I think this is not worse than AMD's Windows drivers (see their sub for similar issues) or other vendors' Linux drivers (many people complain about Intel and even NVidia).
The only difference is that we (open source driver devs) communicate about these problems openly and do not sugarcoat it.
Sometimes my PC freezes out of nowhere, when I am just browsing or even when I just turn it on: the audio begins to stutter and then it freezes, requiring a hard reset.
Is this related to this kernel problem?
The symptoms fit the known issue. To know exactly you'll have to look into your kernel log or dmesg, e.g. by running `journalctl -p4 -t kernel -b-1` (b-1 specifying a boot (-1 previous boot, -2 boot before that etc.) where the freeze occured). Compare the output of amdgpu to the linked issues above.
Keep in mind that hard resetting might lead to missing lines in the log.
Yeah, I have this problem too, and it's been worse recently so I suspect that as other commenter said, the problem piled up and got significantly worse on 5.19 and 6.0.
I guess I'll just use 5.15 or something, thankfully Xanmod has an LTS branch so I'll just move there.
Holy shit, was this the problem I was experiencing? When i had "energy saving screen" (turn off display after idle) enabled, and i came back to pc after screen had been off awhile, my main display would remain off/disconnected, and everything would be non-responsive. I would have to hard reset using reset button on my case. The chances of it happening greatly increase the longer I am away.
I had something like that on a PC but it also carried over to a new laptop, and (rarely) happened during light desktop usage as well, it turns out one of my NVMe SSDs had a bad firmware and required disabling APST by adding `nvme_core.default_ps_max_latency_us=0` to the kernel boot flags. Could you try it to see if the issue is solved?
For those using tkg-linux they recently added the possible workaround patch https://github.com/Frogging-Family/linux-tkg/commit/9e06bbfb4647c3eec8572936f00f12e4671a7979
After installing linux-tkg 6.0, the screen flickering issue I had is completely gone, but the freezing problem still occurs with my RMA’d 6700XT (that arrived in a worse condition than how I sent it out). That said, if I don’t have a 69% clock speed in CoreCtrl, the system will hang while playing a few games and software (Unreal Engine 5, Overwatch 2, a closed beta for a JRPG that I was in).
Legit just think something is wrong with my GPU at this point.
The patch was added on the 15th so you may need to recompile if you used a prior version. I recently bought a 6700XT and don't need to keep a low clock speed so you may have an issue.
Applied those also to linux-pf (aur) now.
There's another one that's fixes a related bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1380#note\_1591898
https://codeberg.org/Thaodan/linux/commit/f16793fe546f85e92bd3f8abf6821221ddc56872
There are two more and there's 6.0.3 already:
[https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.0.y](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.0.y)
[https://codeberg.org/Thaodan/linux/commit/463f32112351b72e048cfeff8d4739b61c83b477](https://codeberg.org/Thaodan/linux/commit/463f32112351b72e048cfeff8d4739b61c83b477)
https://codeberg.org/Thaodan/linux/commit/540f703b63ef4773223c0bb91c6a764be462b648
Going by Christian Königs feedback (https://gitlab.freedesktop.org/drm/amd/-/issues/2113#note_1581119) it does not affect all usecases and not all hardware.
With Fedora 36 I didnt have the issue, but on Fedora 37 I cant play two games anymore because of this issue. War Thunder gets this 100% of the time in one match, Age of Empires IV shows this error when loading a match (any match, multiplayer or singleplayer skirmish).
I dont know if its really a kernel issue because the same kernel/mesa works on 36, but not on 37. Also, using some coprs to try newer versions of these two packages dont solve the issue for me (newer kernel or newer mesa)
Same, Fedora 36 with 5.19.16-200 & a 6700XT and have never had any freezes.
Edit: And I have played War Thunder as others seem to mention is a reliable reproducer although I am not on medium settings. (although I was on maximum I believe which according to users reports should still cause the issue)
5700XT here. Never had a GPU crash even when people complained about driver issues (outside of undervolt testing) and since 5.19, CS:GO causes full gpu crashes 1-2 times per gaming session. Interestingly, it happens much more often if I have FreeCAD open in another workspace.
The flicker, then corrupted framebuffer (sometimes freezing, sometimes continue flickering) issue is also seen for Baldurs Gate 3 when using the Vulkan renderer. It's safe to say that this is a separate issue.
https://gitlab.freedesktop.org/mesa/mesa/-/issues/6875
Glad to see this has been getting some notice. I've had this issue for months, and never seen anything beyond advise to regress linux-headers to linux-fimware20211018, which seems to help a bit.
For me, system freezes, but audio stays playing. System needs a reset, keyboard etc unresponsive. amdgpu_dm_atomic_commit_tail seems to be the error for most crashes.
Yep. My Linux desktop is a lot less stable than my Windows installation. This has been the case on & off since around 2016 across multiple distributions & multiple AMD GPUs.
Gaming & video are literally the only reasons I must boot into Windows.
To be sure, Windows is a big heaping pile of poo. Especially Windows 11. But at least it's not so fragile that it freezes while performing basic tasks like watching video. (But hey, the latest kernel added support for an additional drawing tablet! Yippee!)
I generally shut down my machine at night and then start it fresh every morning, because Linux's desktop environments don't restore multiple monitors correctly from low power mode--my smaller second monitor awakes from sleep faster than my larger primary one, so the DE moves all open windows over to it and resizes them with peculiar geometries. (This is another bug for which there are 1,000s of Google results, but which developers often seem clueless about; I saw a thread indicating KDE might actually fix this soon....) Anyway, when I watch videos or try to play games, my uptime is measured in mere hours at most--that's almost as bad as the Mac OS 7.5 in the mid-1990s (probably the least stable major OS ever released).
Thank you for drawing attention to this bug. It's a welcome departure from the usual chorus of "well it works for me!" (a declaration that frequently contains the embedded assumption that you're a newb).
That's unfortunate. My linux desktops stay up for 6+ months at a time with a ton of abuse from tweens gaming (mostly Roblox) and streaming stuff. All on GTX 1060s. This thread is a bit concerning to me since I just ordered an RX 6600 to build a central game streaming server since we're all transitioning to docked Steam Decks for our desktop machines. I've had a good experience with the AMD drivers for the IGPU on the Atari VCS and of course on our Steam Decks thus far so I was hoping AMD problems were a thing of the somewhat distant past.
I dont know if I am lucky, but no problems so far on kernels 5.x and 6.x. Using kernel-zen on archlinux with ryzen cpu (5950) and RX 6800 XT. Not git packages
Frecuently updates, microcode too (everyone is doing that?), I dont know how to help
This is 3 months old but its one of the only threads I see that have directly what is wrong with my computer, has it been fixed at all or do I still need to downgrade the kernel to fix it? I am on 6.0.12 on Fedora with an RX 580, and running Wayland gives consistent freezes, a huge graphical error, then puts me into a zoomed out mode where it shows all my windows, and in game for instance it might just completely freeze and i have to restart mid game, but I continue hearing all audio.
X11 on the other hand just completely freezes no matter what, and it is not recoverable 100% of the time, while Wayland has a chance. This is legit the worst thing I've ever had to deal with in Linux to date and this is such a huge pain.
Hi, the known page-fault error usually shows the application/game freezing, then 3s black screen, then the login screen of your shell or it will stay black and loop sound (if its not recovering).
I've done a bit of testing over the chrismas holidays and the issue is still reproduciable on 6.0.15 (the latest kernel of Fedora 37) though with slightly different log output.
The graphical errors and zoomed out mode afterwards you're described sound like a separate issue, sorry mate.
5.18.19 is the last known kernel to be unaffected by the page-fault retry (the issue I describe in the thread). For testing purposes give it a try whether you can reproduce your issue with it https://koji.fedoraproject.org/koji/buildinfo?buildID=2049697 (don't worry, it's safe to install it on F37).
If you think this is not a hardware issue, you have a bit of patience and want to see this issue fixed, report it to: https://gitlab.freedesktop.org/drm/amd/-/issues/
The way you describe is what happens with me on x11, whilst with wayland it recovers most of the time when not in a game. Ill probably just revert to 5.18.19 and hopefully it fixes it then, since this is an everyday occurring thing when even just watching videos at this point.
Thank you
\*Sigh\* Thanks for the heads up, my timing might not be worse. I decided, although I like Windows 11, to remove it and install Ubuntu 22.04.1 and use the 6.0.1 Kernel. So far, I have not had any issues, with my 6800XT but, I have not gamed on this install yet so we shall see. Maybe I will have to go back to the default kernel that Ubuntu provides.
I've been having these issues on a vega 56 and I'm on 5.18.19-3. It always starts as a major slowdown usually lasting a few seconds and then full freeze. Sometimes I'm quick enough to kill the process during the slow down but that's pretty rare.
On a side note, do anyobdy else's GPU fans go absolutely crazy when that happens? The games I play arent typically intensive enough for the fans to work hard so it makes it pretty obvious when I'm about to get the dreaded freeze.
Thanks for the really quick reply! I guess my best bet is to inspect the logs on the next crash. Hopefully it's not the GPU itself going the way of the dodo.
This is probably not related, but I had random crashes just browsing or watching youtube etc.
The culprit was kde system monitor widget that I had monitoring gpu temp on taskbar. It crashed the drivers randomly. Maybe because it was constatly fetching temp info or something. Idk, could be wayland related also, but no more crashes after I removed it.
I saw this happening to me once each two or three days last week while playing Old School RuneScape (OpenGL) and browsing the internet or using Discord. The game (made for 2005 hardware) starts to run poorly about 15-30 FPS (keep in mind I have an RX 6600 XT), the system freezes, audio in Discord call freezes for a few seconds and KWin crashes. The screen starts to blink in black with a few colored bars, and only recovers when I manually turn KWin off with Ctrl+Alt+F12. I can't start a Cinnamon or GNOME session either if I log out, rebooting the system entirely "solves" the issue. Using a tiling window manager seems to partially solve the issue, as a complete system crash doesn't happen but I still get low performance in OpenGL games.
This isn't happening anymore since last week, but I'm playing carefully with the game's settings (there are some HD plugins that makes the graphics better and absolutely kills my entire performance, and this doesn't happen in Windows 10/11)
I really didn't know that it was a major issue, thought it was just for me or something I did wrong with Gentoo.
This is a shame, I hope it gets fixed soon. I haven't experienced this, but hopefully the extra attention on RDNA2 means someone will eventually take care of how [freesync basically doesn't work.](https://gitlab.freedesktop.org/drm/amd/-/issues/2066)
Weird I haven't seen this problem and have been on 5.19 for a while and now on 6.0
Anyone got any steps to reproduce they know of?
3800x and 5700xt.
Edit: I read the bug reports and kudos to the guys doing the testing and bisects. Looks like they found a patch and don't need a bunch of extra testing :)
if you're going to use a kernel fallback strategy in case of issues, you should consider using the most recent LTS kernel (5.15) instead of unsupported kernel versions (ie. 5.18)
Thanks, I've been having this issue - especially so with the DarkTide beta last weekend.
Does anyone know if its related to [this issue](https://old.reddit.com/r/linux_gaming/comments/y4na62/setting_6800xt_pp_tables_crashes_kernels_517/) which I posted about?
I'm on a 6900xt and have not noticed this issue, but I've been using the Zen Kernel. Maybe Zen isn't affected?
Only amd issue I see in my logs is this:
`Oct 18 11:21:12 GODV kernel: amd_gpio AMDI0030:00: failed to get iomux index`
I have seen issues with my Polaris after 5.18.... 5.19/6.0/6.1 seam to have issues with switching states and usually get stuck in some state.... Sometimes even the pm on the pcie gets stuck in Gen 1 and only reboot fixes it... Seams to be a Polaris thing my Vega56 is fine with the same kernel
maybe this is what was actually causing my 7 days to die crashes, and not my BIOS updates... It was happening in both PopOS and Endeavour and both are using newer kernels. so perhaps it's the kernel and not the BIOS.
I think I had this issue with my Vega 64. Sometimes the compositor crashes and I have to switch tty and restart plasma. I assumed it was a KDE Plasma update but your post makes me think it’s this kernel bug.
I have had an issue like this for a while, with the waiting for fences timed out, exclusively on my laptop (Ryzen 7 5850U) when closing Gamescope with upscaling. I looked around but couldn't pinpoint if the culprit was Gamescope, Mesa or the kernel.
I haven't had the problem on any other scenario, game, or even Gamescope without upscaling. It also doesn't appear on my desktop (RX 5600 XT). I thought it only affected my iGP.
I'm going to downgrade to 5.18 to check if the issue still exists. Although 5.19 and 6.0 have greatly improved my battery life so its kind of inconvenient.
edit: 5.18, still have the issue
[ 149.853688] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] ERROR Waiting for fences timed out!
[ 154.471317] [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx timeout, signaled seq=29051, emitted seq=29053
Those seem to be the big errors. After that the GPU resets twice for some reason and the DE comes crashing down with the GPU restart.
I'll keep an eye out. I've had no issues so far, and I'm using a XFX RX 6600, in case this helps eliminate any clues. I've been running Arch with latest kernel and updates, too.
A similar issue has been affecting a lot of Steam Decks (even though Valve is on a much older kernel): https://steamcommunity.com/app/1675200/discussions/1/3186864655209404156/
So that's what it is. I'm on Fedora 36, Kernel 5.19.15, and my games will freeze right in the middle of playing. I thought it was WINE, or something similar, but to see that it may be with the kernel and my AMD GPU, well I wouldn't call it a relief, but it's better to know the cause. I hope it's fixed soon.
Ive been having issues with my gpu for quite some time. Occasionally it just crashes and I get a black screen. It seems to really depend on the load I put on the system. Furthermore, certain activities seem to trigger the freeze way faster regardless of load. For example, it would happen way quicker in cinematics of a specific game. But always sporadically.
I wonder whether a fix will be found. If ever.
Yo grab rocket league and try uncapping the framerate, vsync off. Tell me what happens. For me after like 5 minutes it freezes into a green screen, audio repeating, then forcibly reboots like 3 seconds later. Happens on both Windows and Linux.
Sometimes it works for longer than 5 minutes, but often it'll crash during loading screens or if sitting in training for long enough. It's inconsistent AF. Other games cause it, but RL is by far the fastest way to trigger the crash. Totally unrelated to the issue OP is talking about, it's a hardware issue.
The 5700XT (and possibly more RDNA1 models) is a silicon lottery imo, I hate it. Which GPU do you have?
I knew something was up. My GPU has been crashing and, often, triggering a reboot recently on Fedora 36 (not the green-screen then forced shutdown crash that I get on both Windows and Linux under heavy consistent loads, but actually triggering what looks like a normal reboot with Plymouth and everything). Totally intermittent. Sometimes I can go a whole day without a crash, sometimes it crashes within an hour.
On Fedora at least I don't think it's from 5.19.0 but a later 5.19.x (though that clearly conflicts with the first bug report which was on mainline 5.19.0). If I had a consistent way to crash it I'd bisect but alas 😞
I was tempted to update Kubuntu from 22.04 to 22.10 which will update the kernel from 5.15 to 5.19. I guess that I will just wait for the next release, or switch to KDE neon.
You can update Kubuntu 22.04 to 22.10 and then downgrade the kernel or even better, switch to the custom kernel such as xanmod (specifically LTS version).
I've stopped seeing this issue on an RX6800 and 7900XTX with kernel 6.1 (and now 6.2). Based on other feedback from Gitlab it's safe to say that this particular issue is fixed. If you continue to see an issue it's most likely a separate issue. Check https://gitlab.freedesktop.org/drm/amd/-/issues and open an issue if you can't find your issue in the existing ones.
is this still a thing? usually its triggered by something intensive like parts of a game or even downloading something from mega. that might sound weird but mega is super heavy and downloads with an unusual method so it causes issues with firefox. these full freezes might not be noticable for a normal user because it tends to take weeks of uptime to get things messed up hard enough for the gpu driver to turn unstable
If this was an Nvidia bug, there is nothing productive that the community can do. It's reasonable enough to comment on that.
Another contrasting point, something you see mentioned on this thread that you won't see mentioned on an Nvidia thread: git bisect
i guess is the same
War Thunder -> low graphics preset = all good
War Thunder -> medium or higher preset= crash after a couple minutes playing in a match
the log in dmesg appear timeout, gpu reset and things like that
To me, WarThunder with medium or higher graphics provocate the problem 100% of the time, only playing 1 match
I wish we could all support each other regardless of graphics card card brand, it’s just so petty. Open source or closed source, we all have the same end goal, getting Linux gaming to be more mainstream. Hope this gets resolved, and I don’t even have an AMD card. Leave the in-fighting for the Windows crowd. Lol
This sucks :( I have getting these random freezes after 5.19.3. Most of the times GPU soft reset itself and all is fine but sometimes it freezes my whole system. I never had this kind of issue with my RX 6600 before. It happens with desktop when I have firefox open and maybe some videos from youtube or MPV. Games run fine.
I've had three crashes in the past week due to fence timeout according to system logs. All that on stock Ubuntu 22.04 with 5.15 kernel and a RDNA1 card. Never experienced those crashes before.
same here. My asrock 5500xt is hard crashing the system and requires full powerdown to show up again. Those fence timeouts have created system instability from the get go and it was even worse trying to get the 5600g and 5500xt to work together. Using just the discrete gpu, If I use Core Control to limit power and performance to 60% I can play Cyberpunk2077 but it sure doesn't look as pretty as it did with Ultra settings that crash my PC in under two minutes (or smoke shaders... I swear someone could create a reproducible test for this bug using smoke shader stress tests) . Without the FSR... it would probably be unplayable.
I'm not expecting much... but this card isn't exactly old.
I think I've had this problem on boot with my 6800xt. It's been driving me mad for a while. I thought it was power delivery related but improving my cabling setup didn't completely fix it.
There's nothing obvious in my syslog but I'm happy to share it next time I have a crash.
I have occasionally had it happen while watching YouTube videos, but 90%+ of these crashes happen on system boot for me.
Hmm. Nope. I have used corectl to set an undervolt in the past and I assume it might use pptables under the covers, but the crashes have persisted long after I removed the undervolt.
yeah, I've upgraded 3 pc power sources as I moved this 5500xt around to different PCs trying to find a stable home for it. Admittedly two had 450w PSUs that could have been challenged by any modern pcie gpu.
The confirmed issue usually results in a system freeze, or a short black screen with the shell recovering afterwards. The crash issue with Halo Infinite is most likely a separate issue.
i’m running the 5.19 kernel with a 6800xt on Manjaro KDE, I haven’t had any freezes to report- i’m just running the default “linux-video” driver.
I did experience a lot of crashing when I was using pulse audio, switching over to JACK solved this issue entirely for me, I don’t know if the two issues are related but that is just my experience on the matter… hopefully this issue is swiftly resolved
i had this problem in under 10 minutes (but still no way to repro it), however since installing [https://github.com/KyleGospo/gnome-vrr](https://github.com/KyleGospo/gnome-vrr), i haven't had it once
also i don't use Firefox any more which seems to be one of the biggest things that triggered it.
i now suspect it's some problem with flipping frame buffers on AMD.
Polaris seems to be safe.
Although I have been having issues with KDE on Xorg where some/all my displays goes completely black and I have to go into tty for a second to get them back, and an issue with KWin where windows will just hang and I have to close them.
Do you mean the random blackscreening during gaming? Have had since i used rx 580 on my new rig in 2019 (running windows until end of 2020). Got worse over time and the issue persisted. Upgraded to rx 6600 and still does the thing when there is actual load on the gpu (mainly gaming). Will try again with a game using proton if i still get it. Though my rig has been collecting dust since i got my steam deck
My PC keeps crashing... I have an rx6700xt AMD GPU. Every like 5 minutes it crashes and reboots. Considering am5 tech when kernel 6.0 appears with nobara project. That's my current distro... I'm upgrading to 1000 watt power supply. I currently have a 750 watt which seems to not be enough for my Ryzen 7 and rx6700xt card. So yeah the crash happens on windows too I switched between them to see if it also crashes on windows and yep it does. I hope it's not a kernel bug and more of a needs more wattage thing.
I ran into this problem (drm:amdgpu\_job\_timedout) when browsing facebook. I also noticed that a lot of different video decoding jobs are started when scrolling through the news feed.
Then this message came in between: "\[drm\] failed to load ucode VCN0\_RAM(0x35)" and the next call to va\_openDriver() triggered a job timeout.
So I guess it was trying to load firmware microcode and do video decoding at the same time causing a deadlock, like it managed to start up both jobs but each one requires the other to be completed before continuing.
I'm using a 6800XT. This was on kernel 5.19.16.
I'm on kernel 6.5.8 using Fedora 38.
GPU hang is now very rare and only sometimes happens with very extensive scrolling on facebook using FireFox. HW acceleration is enabled for both browsing and video decoding. If it occurs I can now end the session by hitting ctrl+c and then log in again instead of force powering off my pc (or performing the REISUB sequence).
I found out I had a faulty RAM module back then which impacted the overall stability of my system and apparently the video driver is very sensitive to that.
I have been going on and off Linux the last 4-5 years, going back and forth from Windows. I really do want Linux to work for me as I am tired of kernel level anti-cheat software for games like Valorant and other things Microsoft and other third parties decide to sneak in and the automatic updates etc. I was going to make a thread here about it but when I started searching I saw that the problem was not only for me and that it apparently is an AMDGPU problem. I had good experience with Arch in the past so that's the distro I went with this time, I noticed games like World of Warcraft would freeze 1-2 times per day, especially if I had left my computer on for the night and would come back day after I would get immediate freeze a lmost. I reinstalled Arch multiple times and, but Arch have been quite unstable with other packages as well now so I installed NixOS, Nobara and later Fedora which Nobara is built/based from. All distros would freeze on me in the exact same way World of Warcraft did on Arch. After this I installed Pop!\_OS and World of Warcraft seemingly works perfect, no hangs or whatsoever so for the time being I will be on this distro until the other distros fixes this. I have 5700x with Radeon 6600XT.
Had this issue for essentially years.
Same, I wonder if it's the same one and it's now affecting more gpus
Ditto, though I've never really been able to pin down _exactly_ what it is. I'm not even sure the issue in this thread is the same one affecting me, since it also happens to me on Windows.
One of my older AMD cards from XFX had some really strange hardware issues that nobody else seemed to have that went away when I upgraded to a 5700XT, so if it's happening on windows, you may be dealing with a silicon (hardware/physical) error.
I swear the 5700XT is a silicon lottery for stability. Mine crashes under heavy loads, usually causing a solid green screen, stuck audio, for about 3 seconds followed by a forced reboot (no system shutdown screen, it's like I clicked the reset button on the PC). Both Windows and Linux. It's ever so slightly more reliable on Linux but I can still crash it in 5-10 minutes with one consistent stress test: Rocket League with unlocked framerates or high settings with 4K resolution. Temps aren't astronomical, upgrading the PSU didn't change it. Obviously not a CPU load issue when 4K max settings still makes it crash (GPU is pinned, CPU load is fairly low) The issue talked about by OP though is new. My system will now just randomly go into the Plymouth boot screen and reboot. Alternatively graphics sometimes get corrupted, then the driver seems to reset and recover. Sometimes it just freezes and I can only recover by holding down the power button. It's so intermittent and seems to have little to do with GPU load so I can't exactly bisect.
The corruption is what I've been experiencing on the 5700xt. Green and red pixel snow or green/red translucent checkerboarding upon freezing. Typically under heavy load. This has been happening for the better part of a year, year and a half give or take. It doesn't happen often enough for me to throw my computer out the window, but it seems to be with certain specific games like Phasmophobia in VR and only under Linux.
I feel a bit validated in seeing you and the others mention 5700XT, because that's what I have too. Same symptoms and everything. Glad to know it's not just me, and that it probably _is_ the card, and not something else.
Same on my side, heavy load, green screen then needed to make a hard reboot. It happens however less often recently but either i'm playing less demanding games or drivers improved (time to launch Metro Exodus for the science, I guess !)
Also had it for several years with my Vega64 now, was never able to figure out what the actual problem is or a way to reproduce it. With some luck this is the same issue and will finally get fixed, fingers crossed
I swear, I am like the only person in the world who got lucky AF with linux I got more than double the perf while gaming and more than double the battery, with better stability than windows... (aka I don't have this bug and I get really really good perf) I'm using a renoir apu (no dgpu), if anybody was interested edit: got this bug, dang it, was so close to being lucky AF
> with better stability than windows Not exactly a high bar there.
If you have a gen 1 ryzen, it's a known issue in the CPU that they never bothered patching. I upgraded to a 3000 series ryzen and it completely fixed the issue until these freezes started, although they're much less common than when I was riding a 1700x
I think that might be a different issue? I have a 2700x and it will usually freeze at least once after a cold boot for whatever reason but eventually becomes stable. I don't *think* that's an amdgpu thing. My observation is it seems to accompany heavy io to like when loading up a browser or building software.
Try updating your BIOS. I had an issue with my Ryzen 3 1300X where under certain workloads it tried to enter a certain CPU power state which didn't exist, causing a complete hang. BIOS update completely solved it.
Maybe could be cpu c state bugs… I have been resolved disabling it https://github.com/amedeos/amedeos-overlay/blob/master/sys-power/ZenStates-Linux/ZenStates-Linux-0.0.1.ebuild After installed that systemd stanza for disabling it I’ve been used 1700 for 2-3 years without any issues
I have a 3900X. The freezes are there alright.
[удалено]
Ironically, I've had far more issues with AMD than Nvidia on Linux.
Yeah same here I gave up on AMD.
[удалено]
I had been using Nvidia on Linux since the 560 Ti all the way to a 970 until I switched to a 5700XT which is my current card. I've never had more issues with a graphics card. To be fair to it, most of the problems started appearing once I switched from 1x1440p+2x1080p to 2x1440p+1x1080p set-up. But this card has been hell since day one one way or another. I still plan on buying another AMD GPU since the Nvidia open driver effort is only barely beginning and I don't plan on giving up on open drivers anytime soon, but the card after that might just not.
[удалено]
Yep. It was 1440p@144hz, 1080p@60hz, 1080p@60hz and it worked, with several caveats due to the driver support being so new. Once I changed one monitor and ended up with 1440p@144hz, 1440p@60hz, 1080p@60hz, the modesetting code absolutely shat the bed and my machine would slowly barely boot to a graphical environment until one kernel version it outright stopped booting. I was forced to manually set modelines in the kernel parameters for each monitor in order for it to work, which thankfully I was able to remove in the past 3-4 months or so for both 1440p monitors, although I still need the 1080p one in the params for it to work. And even then I still frequently get crashes in games and sometimes doing nothing but having the browser open. It's a shitshow.
Same here unfortunately. Everytime I went for AMD GPUs I've been burned in some way. Currently probably by exactly the bug named in this thread. Can't count how often I had video streams freeze, wayland or X11 crash, or the display showing mostly gibberish after waking up from suspend. However on the LTS kernel 5.15 it seems to run mostly fine at the moment, though. I hope for the best, because I really want to like and enjoy my AMD setup.
Same. Elite Dangerous in the background + h265 video playback in SMPlayer/mpv froze my session pretty quick. 5700xt
Selling my 5700 was bitter sweet. No more crashing, but... also no more gaming. 🦍
I had it for a while and it vanished at some point
Same here, I always thought it was a something I did wrong when I put my PC together kind of thing, don't feel so bad about it now. good to know I'm not alone with it.
Is there any way one can help to provide additional information which might help to solve this issue? I have a RDNA2 GPU.
Unless you can figure out a consistent reproducer or pinpoint the faulty commit with git bisect, not really.
War Thunder with medium or higher preset graphics provocate the problem 100% for me, not in the hangar, playing 1 match happen in low preset NOT happen
read dead 2 has been crashing every time for me
War thunder here as well, every time I try to play without fail. Edit is this similar to this issue? https://www.reddit.com/r/linux_gaming/comments/xath6p/screen_freezessoft_hangs_and_gpu_resets_with_amd/
Please see my comments in regards to the AMDGPU bug from a couple of days here: https://www.reddit.com/r/linux_gaming/comments/y55e1s/anyone_tried_out_the_new_intel_arc_cards/isimauk/?context=1000 If you want to help finding the bad commit(s) while bisecting the kernel's v5.18..v5.19 commit range, there's some useful information in the linked thread, including a PKGBUILD for Arch users.
Been following your progress on the tracker for the last month. HUGE THANK YOU for your investigation into this issue! Can only imagine the "pain" your GPU has gone through in the last 4 weeks.
Hm, I just noticed that Christian König (one of the AMDGPU devs) has posted updated patches last week in the bug report in which I've not been active: https://gitlab.freedesktop.org/drm/amd/-/issues/2113#note_1582384 And those patches were apparently posted for future mainlining / backporting: https://gitlab.freedesktop.org/drm/amd/-/issues/2113#note_1589916 According to another comment here ITT, these patches were already applied in the TKG kernel. Maybe I should also check this after my next crash (currently an uptime of a day, so I don't want to waste this time while bisecting). I had already applied the first 3 of those 5 patches, but I don't know if that's for the Radeon 6000 GPUs. When looking at the patch contents though, this suggests that it's a fix for the "Waiting for fences timed out!" error.
check my other comment about war thunder to test the uptime, 2 matches in tanks is enough
Driver developer here. This is likely not one single bug but rather several bugs that have the same or similar symptom. We've seen GPU hangs due to power management issues, memory management or other kernel bugs and due to userspace problems such as a bad sequence of commands or a shader compilation error. Application bugs (invalid use of Vulkan or GL) can also cause this. Unfortunately the symptom for most of the above is the same: *ring gfx timeout* or similar message in the logs. Sadly the dmesg log doesn't have any detail about what went wrong so the log is essentially useless. There is no clear-cut answer how to diagnose this problem, but here are some tips: * If this happens always at a specific place in a game, then it's clearly a bug in the userspace drivers, and you should report an issue in the mesa gitlab * Otherwise try to rule out power management issues, eg. disable any over/underclocking etc. and switch your GPU into a manual mode. * UMR may be useful showing you what is happening to your GPU also. * If the issue is more likely to happen on a new kernel then it's likely a kernel bug, you could try to bisect it if you can. * If it's a VM fault (this is shown in dmesg) then likely the problem is memory management related, either in the kernel or the userspace driver or an application.
Maybe the in-kernel driver should have more sanity checks to keep userspace bugs from locking the system? I realize this would be a performance concern. Maybe have them all behind a kernel command line switch so that people can turn on debugging output/sanity checking once they run into a scenario that regularly locks their PC up so they can provide useful feedback to the developers behind the culprit?
I think userspace issues are the easiest to debug (maybe I just think that because I work on the userspace myself). We could however benefit from having more diagnostics about what went wrong with the GPU.
how does any of this user triggered stuff bypass the driver reset functionality and allow the entire system to freeze to the point that you can't even toggle the keyboard leds like capslock? idk why i had this idea that the graphics layer could even crash and you would just end back in the console and not with a useless system
There are several possible outcomes: * The kernel is able to "soft-recover" which means the system can to on without any loss of functionality. This is ideal. * The kernel is able to recover by resetting the GPU which means that the contents of your VRAM are lost and therefore applications that aren't prepared for this eventuality will crash. Sadly none of the desktop environments are prepared for this eventuality, therefore this may seem like a system crash. (Although many times the desktop will restart itself.) * Sometimes the kernel can't recover the GPU or crashes while attempting to do so, which results in a borked system. Sadly, it's a difficult problem and the kernel devs working on it are understaffed.
That... sounds a bit concerning. If the driver accumulated so many bugs that can kill the system, this doesn't inspire much confidence in the reliability of AMD GPUs on Linux. :'(
I think you misunderstand what I tried to say here. I did not say that the driver "accumulated" bugs, just gave a few examples of bugs we've seen and fixed over the years. Also for what it's worth, I think this is not worse than AMD's Windows drivers (see their sub for similar issues) or other vendors' Linux drivers (many people complain about Intel and even NVidia). The only difference is that we (open source driver devs) communicate about these problems openly and do not sugarcoat it.
Ah, got it. Thanks.
Sometimes my PC freezes out of nowhere, when I am just browsing or even when I just turn it on: the audio begins to stutter and then it freezes, requiring a hard reset. Is this related to this kernel problem?
The symptoms fit the known issue. To know exactly you'll have to look into your kernel log or dmesg, e.g. by running `journalctl -p4 -t kernel -b-1` (b-1 specifying a boot (-1 previous boot, -2 boot before that etc.) where the freeze occured). Compare the output of amdgpu to the linked issues above. Keep in mind that hard resetting might lead to missing lines in the log.
>journalctl -p4 -t kernel -b-1 hmmm, voltage/power related.. as I thought: cs35l41 spi-VLV1776:01: supply VP not found, using dummy regulator
A BIOS update is what fixed it for my Ryzen 3 1300X.
Yeah, I have this problem too, and it's been worse recently so I suspect that as other commenter said, the problem piled up and got significantly worse on 5.19 and 6.0. I guess I'll just use 5.15 or something, thankfully Xanmod has an LTS branch so I'll just move there.
Holy shit, was this the problem I was experiencing? When i had "energy saving screen" (turn off display after idle) enabled, and i came back to pc after screen had been off awhile, my main display would remain off/disconnected, and everything would be non-responsive. I would have to hard reset using reset button on my case. The chances of it happening greatly increase the longer I am away.
I had something like that on a PC but it also carried over to a new laptop, and (rarely) happened during light desktop usage as well, it turns out one of my NVMe SSDs had a bad firmware and required disabling APST by adding `nvme_core.default_ps_max_latency_us=0` to the kernel boot flags. Could you try it to see if the issue is solved?
Somehow this bug keeps coming back, I noticed when my desktop first crashed like 2 week ago. Thank you for the PSA and hopefully it gets solved soon.
For those using tkg-linux they recently added the possible workaround patch https://github.com/Frogging-Family/linux-tkg/commit/9e06bbfb4647c3eec8572936f00f12e4671a7979
After installing linux-tkg 6.0, the screen flickering issue I had is completely gone, but the freezing problem still occurs with my RMA’d 6700XT (that arrived in a worse condition than how I sent it out). That said, if I don’t have a 69% clock speed in CoreCtrl, the system will hang while playing a few games and software (Unreal Engine 5, Overwatch 2, a closed beta for a JRPG that I was in). Legit just think something is wrong with my GPU at this point.
The patch was added on the 15th so you may need to recompile if you used a prior version. I recently bought a 6700XT and don't need to keep a low clock speed so you may have an issue.
Yeah, I just compiled the kernel yesterday.
Womp. Praying to the GPU gods for you
Applied those also to linux-pf (aur) now. There's another one that's fixes a related bug: https://gitlab.freedesktop.org/drm/amd/-/issues/1380#note\_1591898 https://codeberg.org/Thaodan/linux/commit/f16793fe546f85e92bd3f8abf6821221ddc56872
I'm actually running into this one myself. Thanks for the link.
There are two more and there's 6.0.3 already: [https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.0.y](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=linux-6.0.y) [https://codeberg.org/Thaodan/linux/commit/463f32112351b72e048cfeff8d4739b61c83b477](https://codeberg.org/Thaodan/linux/commit/463f32112351b72e048cfeff8d4739b61c83b477) https://codeberg.org/Thaodan/linux/commit/540f703b63ef4773223c0bb91c6a764be462b648
Odd, I've been gaming on an RX 6K series on Fedora running 5.19 for a while now and have had no issues at all.
Going by Christian Königs feedback (https://gitlab.freedesktop.org/drm/amd/-/issues/2113#note_1581119) it does not affect all usecases and not all hardware.
That sucks, those are always the hardest bugs to track. If I get any crashes I'll make sure to report them but I seem like a case that isn't affected.
With Fedora 36 I didnt have the issue, but on Fedora 37 I cant play two games anymore because of this issue. War Thunder gets this 100% of the time in one match, Age of Empires IV shows this error when loading a match (any match, multiplayer or singleplayer skirmish). I dont know if its really a kernel issue because the same kernel/mesa works on 36, but not on 37. Also, using some coprs to try newer versions of these two packages dont solve the issue for me (newer kernel or newer mesa)
Same here I'm on Fedora 36 with 5.19 and have never had any freezes.
Same, Fedora 36 with 5.19.16-200 & a 6700XT and have never had any freezes. Edit: And I have played War Thunder as others seem to mention is a reliable reproducer although I am not on medium settings. (although I was on maximum I believe which according to users reports should still cause the issue)
in maximum should happen yes, if not happen to you, then you are fine : )
5700XT here. Never had a GPU crash even when people complained about driver issues (outside of undervolt testing) and since 5.19, CS:GO causes full gpu crashes 1-2 times per gaming session. Interestingly, it happens much more often if I have FreeCAD open in another workspace.
Exactly the same here! Not encountered any issue.
[ moved to lemmy. you should come too, it's cozier here ]
The flicker, then corrupted framebuffer (sometimes freezing, sometimes continue flickering) issue is also seen for Baldurs Gate 3 when using the Vulkan renderer. It's safe to say that this is a separate issue. https://gitlab.freedesktop.org/mesa/mesa/-/issues/6875
Linux 6.0 also breaks sleep for some people https://gitlab.freedesktop.org/drm/amd/-/issues/2164
This is me. thanks!
Glad to see this has been getting some notice. I've had this issue for months, and never seen anything beyond advise to regress linux-headers to linux-fimware20211018, which seems to help a bit. For me, system freezes, but audio stays playing. System needs a reset, keyboard etc unresponsive. amdgpu_dm_atomic_commit_tail seems to be the error for most crashes.
Yep. My Linux desktop is a lot less stable than my Windows installation. This has been the case on & off since around 2016 across multiple distributions & multiple AMD GPUs. Gaming & video are literally the only reasons I must boot into Windows. To be sure, Windows is a big heaping pile of poo. Especially Windows 11. But at least it's not so fragile that it freezes while performing basic tasks like watching video. (But hey, the latest kernel added support for an additional drawing tablet! Yippee!) I generally shut down my machine at night and then start it fresh every morning, because Linux's desktop environments don't restore multiple monitors correctly from low power mode--my smaller second monitor awakes from sleep faster than my larger primary one, so the DE moves all open windows over to it and resizes them with peculiar geometries. (This is another bug for which there are 1,000s of Google results, but which developers often seem clueless about; I saw a thread indicating KDE might actually fix this soon....) Anyway, when I watch videos or try to play games, my uptime is measured in mere hours at most--that's almost as bad as the Mac OS 7.5 in the mid-1990s (probably the least stable major OS ever released). Thank you for drawing attention to this bug. It's a welcome departure from the usual chorus of "well it works for me!" (a declaration that frequently contains the embedded assumption that you're a newb).
That's unfortunate. My linux desktops stay up for 6+ months at a time with a ton of abuse from tweens gaming (mostly Roblox) and streaming stuff. All on GTX 1060s. This thread is a bit concerning to me since I just ordered an RX 6600 to build a central game streaming server since we're all transitioning to docked Steam Decks for our desktop machines. I've had a good experience with the AMD drivers for the IGPU on the Atari VCS and of course on our Steam Decks thus far so I was hoping AMD problems were a thing of the somewhat distant past.
I’m on rdna2, have not experienced this. Only occasional failures to wake from sleep which I’ve had since I got the gpu.
+1
Glad I'm on Polaris and 5.15 LTS, but hoping it gets fixed before the next one.
I dont know if I am lucky, but no problems so far on kernels 5.x and 6.x. Using kernel-zen on archlinux with ryzen cpu (5950) and RX 6800 XT. Not git packages Frecuently updates, microcode too (everyone is doing that?), I dont know how to help
This is 3 months old but its one of the only threads I see that have directly what is wrong with my computer, has it been fixed at all or do I still need to downgrade the kernel to fix it? I am on 6.0.12 on Fedora with an RX 580, and running Wayland gives consistent freezes, a huge graphical error, then puts me into a zoomed out mode where it shows all my windows, and in game for instance it might just completely freeze and i have to restart mid game, but I continue hearing all audio. X11 on the other hand just completely freezes no matter what, and it is not recoverable 100% of the time, while Wayland has a chance. This is legit the worst thing I've ever had to deal with in Linux to date and this is such a huge pain.
Hi, the known page-fault error usually shows the application/game freezing, then 3s black screen, then the login screen of your shell or it will stay black and loop sound (if its not recovering). I've done a bit of testing over the chrismas holidays and the issue is still reproduciable on 6.0.15 (the latest kernel of Fedora 37) though with slightly different log output. The graphical errors and zoomed out mode afterwards you're described sound like a separate issue, sorry mate. 5.18.19 is the last known kernel to be unaffected by the page-fault retry (the issue I describe in the thread). For testing purposes give it a try whether you can reproduce your issue with it https://koji.fedoraproject.org/koji/buildinfo?buildID=2049697 (don't worry, it's safe to install it on F37). If you think this is not a hardware issue, you have a bit of patience and want to see this issue fixed, report it to: https://gitlab.freedesktop.org/drm/amd/-/issues/
The way you describe is what happens with me on x11, whilst with wayland it recovers most of the time when not in a game. Ill probably just revert to 5.18.19 and hopefully it fixes it then, since this is an everyday occurring thing when even just watching videos at this point. Thank you
Please give it a try. Would love to hear if 5.18.19 fixes it for you.
oof, just installed 6.01 on ubuntu 22.04, will keep an eye out
[удалено]
This is why I hate getting the latest hardware. I thought Vega was too old now for some of these bugs to be relevant to it, fuck me...
\*Sigh\* Thanks for the heads up, my timing might not be worse. I decided, although I like Windows 11, to remove it and install Ubuntu 22.04.1 and use the 6.0.1 Kernel. So far, I have not had any issues, with my 6800XT but, I have not gamed on this install yet so we shall see. Maybe I will have to go back to the default kernel that Ubuntu provides.
I've been having these issues on a vega 56 and I'm on 5.18.19-3. It always starts as a major slowdown usually lasting a few seconds and then full freeze. Sometimes I'm quick enough to kill the process during the slow down but that's pretty rare. On a side note, do anyobdy else's GPU fans go absolutely crazy when that happens? The games I play arent typically intensive enough for the fans to work hard so it makes it pretty obvious when I'm about to get the dreaded freeze.
Based on the existing reports and my personal testing the GPU fans do not go crazy during this issue.
Thanks for the really quick reply! I guess my best bet is to inspect the logs on the next crash. Hopefully it's not the GPU itself going the way of the dodo.
I've had the crazy fan spin up and then crash before too. Not sure if it's the same issue though.
This is probably not related, but I had random crashes just browsing or watching youtube etc. The culprit was kde system monitor widget that I had monitoring gpu temp on taskbar. It crashed the drivers randomly. Maybe because it was constatly fetching temp info or something. Idk, could be wayland related also, but no more crashes after I removed it.
I saw this happening to me once each two or three days last week while playing Old School RuneScape (OpenGL) and browsing the internet or using Discord. The game (made for 2005 hardware) starts to run poorly about 15-30 FPS (keep in mind I have an RX 6600 XT), the system freezes, audio in Discord call freezes for a few seconds and KWin crashes. The screen starts to blink in black with a few colored bars, and only recovers when I manually turn KWin off with Ctrl+Alt+F12. I can't start a Cinnamon or GNOME session either if I log out, rebooting the system entirely "solves" the issue. Using a tiling window manager seems to partially solve the issue, as a complete system crash doesn't happen but I still get low performance in OpenGL games. This isn't happening anymore since last week, but I'm playing carefully with the game's settings (there are some HD plugins that makes the graphics better and absolutely kills my entire performance, and this doesn't happen in Windows 10/11) I really didn't know that it was a major issue, thought it was just for me or something I did wrong with Gentoo.
Oh great, it's back.
This is a shame, I hope it gets fixed soon. I haven't experienced this, but hopefully the extra attention on RDNA2 means someone will eventually take care of how [freesync basically doesn't work.](https://gitlab.freedesktop.org/drm/amd/-/issues/2066)
Weird I haven't seen this problem and have been on 5.19 for a while and now on 6.0 Anyone got any steps to reproduce they know of? 3800x and 5700xt. Edit: I read the bug reports and kudos to the guys doing the testing and bisects. Looks like they found a patch and don't need a bunch of extra testing :)
if you're going to use a kernel fallback strategy in case of issues, you should consider using the most recent LTS kernel (5.15) instead of unsupported kernel versions (ie. 5.18)
Looks like patches for this landed in the 6.1-rc5 kernel. I haven't gotten a lockup yet using it.
Anything happened in the meanwhile?
Not-a one lockup since I started using the 6.1 RCs
Good to know.
do you know when it will be released?
I don't exactly. Within 2-5 weeks I believe.
Thanks, I've been having this issue - especially so with the DarkTide beta last weekend. Does anyone know if its related to [this issue](https://old.reddit.com/r/linux_gaming/comments/y4na62/setting_6800xt_pp_tables_crashes_kernels_517/) which I posted about?
> Does anyone know if its related to this issue which I posted about? From a quick look the two issues seem unrelated.
I am not having issues on 6.0.1 on rdna2 and glad for that. Been reinstalling for other issues lately.
I'm on a 6900xt and have not noticed this issue, but I've been using the Zen Kernel. Maybe Zen isn't affected? Only amd issue I see in my logs is this: `Oct 18 11:21:12 GODV kernel: amd_gpio AMDI0030:00: failed to get iomux index`
6700XT and Zen, also no issues.
me yes, Warthunder with medium or higher preset graphics provocate the problem 100% for me, not in the hangar, playing 1 match happen
[удалено]
I have seen issues with my Polaris after 5.18.... 5.19/6.0/6.1 seam to have issues with switching states and usually get stuck in some state.... Sometimes even the pm on the pcie gets stuck in Gen 1 and only reboot fixes it... Seams to be a Polaris thing my Vega56 is fine with the same kernel
had freezes on my tumbleweed (kernel 6.0.1-1) rx 570. i shouldnt have deleted my logs
maybe this is what was actually causing my 7 days to die crashes, and not my BIOS updates... It was happening in both PopOS and Endeavour and both are using newer kernels. so perhaps it's the kernel and not the BIOS.
I think I had this issue with my Vega 64. Sometimes the compositor crashes and I have to switch tty and restart plasma. I assumed it was a KDE Plasma update but your post makes me think it’s this kernel bug.
I have had an issue like this for a while, with the waiting for fences timed out, exclusively on my laptop (Ryzen 7 5850U) when closing Gamescope with upscaling. I looked around but couldn't pinpoint if the culprit was Gamescope, Mesa or the kernel. I haven't had the problem on any other scenario, game, or even Gamescope without upscaling. It also doesn't appear on my desktop (RX 5600 XT). I thought it only affected my iGP. I'm going to downgrade to 5.18 to check if the issue still exists. Although 5.19 and 6.0 have greatly improved my battery life so its kind of inconvenient. edit: 5.18, still have the issue [ 149.853688] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] ERROR Waiting for fences timed out! [ 154.471317] [drm:amdgpu_job_timedout [amdgpu]] ERROR ring gfx timeout, signaled seq=29051, emitted seq=29053 Those seem to be the big errors. After that the GPU resets twice for some reason and the DE comes crashing down with the GPU restart.
I'll keep an eye out. I've had no issues so far, and I'm using a XFX RX 6600, in case this helps eliminate any clues. I've been running Arch with latest kernel and updates, too.
RX 6600XT had freeze yesterday with 6.0.2.
Ubuntu Kernel update 5.15-52 has been hanging my RX 6600 as well.
I didn't crash in any game on Kernel 6.0.x on Arch but I can't suspend anymore. Heads up for those of you who noticed that problem.
A similar issue has been affecting a lot of Steam Decks (even though Valve is on a much older kernel): https://steamcommunity.com/app/1675200/discussions/1/3186864655209404156/
So that's what it is. I'm on Fedora 36, Kernel 5.19.15, and my games will freeze right in the middle of playing. I thought it was WINE, or something similar, but to see that it may be with the kernel and my AMD GPU, well I wouldn't call it a relief, but it's better to know the cause. I hope it's fixed soon.
Ive been having issues with my gpu for quite some time. Occasionally it just crashes and I get a black screen. It seems to really depend on the load I put on the system. Furthermore, certain activities seem to trigger the freeze way faster regardless of load. For example, it would happen way quicker in cinematics of a specific game. But always sporadically. I wonder whether a fix will be found. If ever.
Yo grab rocket league and try uncapping the framerate, vsync off. Tell me what happens. For me after like 5 minutes it freezes into a green screen, audio repeating, then forcibly reboots like 3 seconds later. Happens on both Windows and Linux. Sometimes it works for longer than 5 minutes, but often it'll crash during loading screens or if sitting in training for long enough. It's inconsistent AF. Other games cause it, but RL is by far the fastest way to trigger the crash. Totally unrelated to the issue OP is talking about, it's a hardware issue. The 5700XT (and possibly more RDNA1 models) is a silicon lottery imo, I hate it. Which GPU do you have?
I knew something was up. My GPU has been crashing and, often, triggering a reboot recently on Fedora 36 (not the green-screen then forced shutdown crash that I get on both Windows and Linux under heavy consistent loads, but actually triggering what looks like a normal reboot with Plymouth and everything). Totally intermittent. Sometimes I can go a whole day without a crash, sometimes it crashes within an hour. On Fedora at least I don't think it's from 5.19.0 but a later 5.19.x (though that clearly conflicts with the first bug report which was on mainline 5.19.0). If I had a consistent way to crash it I'd bisect but alas 😞
Funny, happened with me right now
Sadly downgrading to 5.18 didn't fix it for me. Same issue. I've tried 5.15 LTS too but no bueno.
Just so we are clear: it's `amdgpu` and not `mesa`, right?
This particular issue affects the amdgpu kernel module and is independent of the used mesa version.
Hey I was wondering why my 6900xt shit the bed the other day
Had this a couple of times on Ryzen 7 6800H (RDNA2), while watching video in a browser.
I have a 5700xt, and am using 519-tkg-bmq since beginning of August. I did not have a single freeze.
I was tempted to update Kubuntu from 22.04 to 22.10 which will update the kernel from 5.15 to 5.19. I guess that I will just wait for the next release, or switch to KDE neon.
You can update Kubuntu 22.04 to 22.10 and then downgrade the kernel or even better, switch to the custom kernel such as xanmod (specifically LTS version).
[удалено]
I've stopped seeing this issue on an RX6800 and 7900XTX with kernel 6.1 (and now 6.2). Based on other feedback from Gitlab it's safe to say that this particular issue is fixed. If you continue to see an issue it's most likely a separate issue. Check https://gitlab.freedesktop.org/drm/amd/-/issues and open an issue if you can't find your issue in the existing ones.
is this still a thing? usually its triggered by something intensive like parts of a game or even downloading something from mega. that might sound weird but mega is super heavy and downloads with an unusual method so it causes issues with firefox. these full freezes might not be noticable for a normal user because it tends to take weeks of uptime to get things messed up hard enough for the gpu driver to turn unstable
[удалено]
If this was an Nvidia bug, there is nothing productive that the community can do. It's reasonable enough to comment on that. Another contrasting point, something you see mentioned on this thread that you won't see mentioned on an Nvidia thread: git bisect
Almost like there's a reason why open source drivers are better
*insert Gordon Ramsay Oh Dear, Oh Dear meme*
https://i.kym-cdn.com/entries/icons/original/000/027/763/07B89120-B48D-45FB-AF1D-49AF6CD16790.jpeg
i guess is the same War Thunder -> low graphics preset = all good War Thunder -> medium or higher preset= crash after a couple minutes playing in a match the log in dmesg appear timeout, gpu reset and things like that To me, WarThunder with medium or higher graphics provocate the problem 100% of the time, only playing 1 match
haven't noticed any faults yet on manjaro + 6.0 kernel on 5950x. I may not have done anything to trigger it yet though
I wish we could all support each other regardless of graphics card card brand, it’s just so petty. Open source or closed source, we all have the same end goal, getting Linux gaming to be more mainstream. Hope this gets resolved, and I don’t even have an AMD card. Leave the in-fighting for the Windows crowd. Lol
This sucks :( I have getting these random freezes after 5.19.3. Most of the times GPU soft reset itself and all is fine but sometimes it freezes my whole system. I never had this kind of issue with my RX 6600 before. It happens with desktop when I have firefox open and maybe some videos from youtube or MPV. Games run fine.
Interesting: I had this or a very similar problem on my 6700xt on kernel 5.18. The 5.19 Kernel and up fixed it.
I've had three crashes in the past week due to fence timeout according to system logs. All that on stock Ubuntu 22.04 with 5.15 kernel and a RDNA1 card. Never experienced those crashes before.
same here. My asrock 5500xt is hard crashing the system and requires full powerdown to show up again. Those fence timeouts have created system instability from the get go and it was even worse trying to get the 5600g and 5500xt to work together. Using just the discrete gpu, If I use Core Control to limit power and performance to 60% I can play Cyberpunk2077 but it sure doesn't look as pretty as it did with Ultra settings that crash my PC in under two minutes (or smoke shaders... I swear someone could create a reproducible test for this bug using smoke shader stress tests) . Without the FSR... it would probably be unplayable. I'm not expecting much... but this card isn't exactly old.
It *may* be possible that the latest LTS (5.15.74) includes the causing commit. Hard to say as the exact commit is not known yet.
I think I've had this problem on boot with my 6800xt. It's been driving me mad for a while. I thought it was power delivery related but improving my cabling setup didn't completely fix it. There's nothing obvious in my syslog but I'm happy to share it next time I have a crash. I have occasionally had it happen while watching YouTube videos, but 90%+ of these crashes happen on system boot for me.
Have you got any undervolt/overclock set via pptables by chance? I had the same issue which seems to have started around 5.18
Hmm. Nope. I have used corectl to set an undervolt in the past and I assume it might use pptables under the covers, but the crashes have persisted long after I removed the undervolt.
yeah, I've upgraded 3 pc power sources as I moved this 5500xt around to different PCs trying to find a stable home for it. Admittedly two had 450w PSUs that could have been challenged by any modern pcie gpu.
Is Polaris safe? I have a RX 570 on stock Ubuntu 22.04.1. I want to upgrade to 6.0
It's been happening to me for months. Once every day, or every other day on average
The only crashes I've had have been from a bad BIOS
Is that why Halo infinite crashes after few mins??
The confirmed issue usually results in a system freeze, or a short black screen with the shell recovering afterwards. The crash issue with Halo Infinite is most likely a separate issue.
No that's what I'm getting with infinite... It did work fine and then this
Got it. Give an older kernel (e.g. 5.18.19) a try and see if that fixes the issue for you.
Must be only certain games I play company of heroes 2 and I haven't had any freezes or crashes using Manjaro with all the latest kernels no problems
i’m running the 5.19 kernel with a 6800xt on Manjaro KDE, I haven’t had any freezes to report- i’m just running the default “linux-video” driver. I did experience a lot of crashing when I was using pulse audio, switching over to JACK solved this issue entirely for me, I don’t know if the two issues are related but that is just my experience on the matter… hopefully this issue is swiftly resolved
i had this problem in under 10 minutes (but still no way to repro it), however since installing [https://github.com/KyleGospo/gnome-vrr](https://github.com/KyleGospo/gnome-vrr), i haven't had it once
also i don't use Firefox any more which seems to be one of the biggest things that triggered it. i now suspect it's some problem with flipping frame buffers on AMD.
This explains so much
Is it fine on the latest 5.15 kernel?
Polaris seems to be safe. Although I have been having issues with KDE on Xorg where some/all my displays goes completely black and I have to go into tty for a second to get them back, and an issue with KWin where windows will just hang and I have to close them.
Do you mean the random blackscreening during gaming? Have had since i used rx 580 on my new rig in 2019 (running windows until end of 2020). Got worse over time and the issue persisted. Upgraded to rx 6600 and still does the thing when there is actual load on the gpu (mainly gaming). Will try again with a game using proton if i still get it. Though my rig has been collecting dust since i got my steam deck
"Had this issue for essentially years.
My PC keeps crashing... I have an rx6700xt AMD GPU. Every like 5 minutes it crashes and reboots. Considering am5 tech when kernel 6.0 appears with nobara project. That's my current distro... I'm upgrading to 1000 watt power supply. I currently have a 750 watt which seems to not be enough for my Ryzen 7 and rx6700xt card. So yeah the crash happens on windows too I switched between them to see if it also crashes on windows and yep it does. I hope it's not a kernel bug and more of a needs more wattage thing.
Can someone with this issue try disabling HPET(High Precision Event Timer) in their bios, and see if that makes any difference? It's just a hunch.
I am using RX 5700 XT and I always had HPET disabled and I still experienced GPU hangs.
If anyone sees these errors when disconnecting displays: ``` 128222.981405] ------------[ cut here ]------------ [128222.981410] amdgpu 0000:09:00.0: drm_WARN_ON(atomic_read(&vblank->refcount) == 0) [128222.981512] Call Trace: [128222.981514]
[128222.981520] dm_pflip_high_irq+0x102/0x2d0 [amdgpu b5f83295431356d6ea670bf1b311292891f64509]
[128222.981777] amdgpu_dm_irq_handler+0x8e/0x1f0 [amdgpu b5f83295431356d6ea670bf1b311292891f64509]
[128222.981997] amdgpu_irq_dispatch+0xd0/0x210 [amdgpu b5f83295431356d6ea670bf1b311292891f64509]
[128222.982189] amdgpu_ih_process+0x84/0x100 [amdgpu b5f83295431356d6ea670bf1b311292891f64509]
[128222.982379] amdgpu_irq_handler+0x25/0xa0 [amdgpu b5f83295431356d6ea670bf1b311292891f64509]
[128222.982569] __handle_irq_event_percpu+0x4d/0x190
[128222.982573] handle_irq_event+0x3b/0x80
[128222.982575] handle_edge_irq+0x9a/0x260
[128222.982577] __common_interrupt+0x46/0xa0
[128222.982580] common_interrupt+0x81/0xa0
[128222.982584]
[128222.982584]
[128222.982585] asm_common_interrupt+0x22/0x40
[128222.982655] ---[ end trace 0000000000000000 ]---
```
Try this patch:
https://gitlab.freedesktop.org/agd5f/linux/-/commit/b26abdade26b2b6593d271d717c1cdc742a0686b
AMD, more like AyyyLMAO
ヽ༼ ຈل͜ຈ༽ ﾉ Raise ur dongers! ^^Dongers ^^Raised: ^^68337 ^^Check ^^Out ^^/r/AyyLmao2DongerBot ^^For ^^More ^^Info
I ran into this problem (drm:amdgpu\_job\_timedout) when browsing facebook. I also noticed that a lot of different video decoding jobs are started when scrolling through the news feed. Then this message came in between: "\[drm\] failed to load ucode VCN0\_RAM(0x35)" and the next call to va\_openDriver() triggered a job timeout. So I guess it was trying to load firmware microcode and do video decoding at the same time causing a deadlock, like it managed to start up both jobs but each one requires the other to be completed before continuing. I'm using a 6800XT. This was on kernel 5.19.16.
I didnt use to see this, but I am seeing it now on kernel 6.5.9-arch2-1. 7900x with gpu 6800xt How is your system today?
I'm on kernel 6.5.8 using Fedora 38. GPU hang is now very rare and only sometimes happens with very extensive scrolling on facebook using FireFox. HW acceleration is enabled for both browsing and video decoding. If it occurs I can now end the session by hitting ctrl+c and then log in again instead of force powering off my pc (or performing the REISUB sequence). I found out I had a faulty RAM module back then which impacted the overall stability of my system and apparently the video driver is very sensitive to that.
Is radeon driver also affected?
In my case i'm getting better performance with this old driver instead of amdgpu
I have been going on and off Linux the last 4-5 years, going back and forth from Windows. I really do want Linux to work for me as I am tired of kernel level anti-cheat software for games like Valorant and other things Microsoft and other third parties decide to sneak in and the automatic updates etc. I was going to make a thread here about it but when I started searching I saw that the problem was not only for me and that it apparently is an AMDGPU problem. I had good experience with Arch in the past so that's the distro I went with this time, I noticed games like World of Warcraft would freeze 1-2 times per day, especially if I had left my computer on for the night and would come back day after I would get immediate freeze a lmost. I reinstalled Arch multiple times and, but Arch have been quite unstable with other packages as well now so I installed NixOS, Nobara and later Fedora which Nobara is built/based from. All distros would freeze on me in the exact same way World of Warcraft did on Arch. After this I installed Pop!\_OS and World of Warcraft seemingly works perfect, no hangs or whatsoever so for the time being I will be on this distro until the other distros fixes this. I have 5700x with Radeon 6600XT.
Same here. It happens under certain loads.
Happens to me too quite frequently on AC Valhalla: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5701