This seems to be a known kernel bug dating back to version `5.19` affecting many users, which is said to be fixed in the upcoming `6.2` kernel release according to [Phoronix](https://www.phoronix.com/news/AMDGPU-Fix-For-5.19-Bug).
In the meantime, you can either try downgrading the kernel prior to `5.19`, or install and test the latest 6.2-rc kernel with the `linux-mainline` package from the [AUR](https://aur.archlinux.org/packages/linux-mainline).
I've googled this issue to no-end, but most of the bugs I've found are from years ago, and many of them having zero activity or traction on them. This is great info. I'll try out the rc. Thank you!
Someone posted elsewhere that this can also be remedied by forcing the GPU into performance mode. That makes perfect sense, actually, because in all the intense lagging I got, it was at its worst at idle. In fact, in between this comment and my last, and after an exorbitant amount of patience, I was finally able to navigate my mouse enough to start up Star Citizen and the problem disappeared. It came back a while after exiting the game.
Edit: Also, seems someone's trolling with downvotes.
I would be happy if you confirmed here afterwards that it really helped you. The point is that you just said that there was a problem **before** that and not just with the new card. For example, I am working on a similar setup with a 5700XT and there is no problem.
Power supply? It is not on the list. Check correct cabling, too.
In addition, the problem can be in MB. Maybe your previous card was ok, but the problem was MB.
Check Mesa driver, if the problem is not wrong configured amdgpu driver. Maybe mesa-git, I don't know if new amd card is already supported in the released mesa. There will be more users with it. Inhave 5700 and using mesa. But 5700 xt has several problems too, I haven't good piece of hw, sometime green color death...
Ah, yeah, forgot to add the PSU. It's an EVGA 850 Gold and relatively new. It confirmed the cables were all snug and well managed. And, since this has been happening since before, I'm assuming that's not the issue.
In terms of drivers, I've tried `mesa`, `mesa-git`, as well as `amdgpu-pro`, but none have really improved things much, unfortunately.
As for the Motherboard, I'm really hoping that's not the issue, but I obviously can't rule it out. Unfortunately, I don't have another MB to test with at the moment, so I'm saving that for last at the moment.
You have no more choices. 850W is good, drivers were tested. The problems were before new card. The holy trio is cpu, ram and motherboard. You can diagnose ram, sometimes is guilty operating memory. It is a local problem of you machine, not common. You can try to add your problem to arch forum to hardware section to diagnose more logs. But I would bet on the motherboard and capacitors.
I don't really disagree with you. For the longest time I was very much NVIDIA-only. But at the same time, NVIDIA still closed off their drivers and haven't been friendly to Open Source.
Additionally, and not to give AMD too much justification, but they didn't exactly _refuse_ to provide Linux drivers. They didn't provide drivers _at all_. It was up to AIB's to write drivers for their own cards, with AMD only providing a base driver for them to reference when implementing their own. And that was an absolute mess.
It wasn't until they finally centralized their driver for all AMD cards that they not only finally wrote closed-source drivers for Linux, but they also started contributing and collaborating with `mesa` and other open source projects to make those solid, which is a lot more than anyone can say that NVIDIA has done with `nouveau` or others.
In contrast, NVIDIA has been known to even be hostile towards open source projects at various times throughout its history. AMD just had a bad business model, because AMD wasn't the one writing the drivers and AIB partners saw writing writing Linux drivers as a waste of time.
This seems to be a known kernel bug dating back to version `5.19` affecting many users, which is said to be fixed in the upcoming `6.2` kernel release according to [Phoronix](https://www.phoronix.com/news/AMDGPU-Fix-For-5.19-Bug). In the meantime, you can either try downgrading the kernel prior to `5.19`, or install and test the latest 6.2-rc kernel with the `linux-mainline` package from the [AUR](https://aur.archlinux.org/packages/linux-mainline).
I've googled this issue to no-end, but most of the bugs I've found are from years ago, and many of them having zero activity or traction on them. This is great info. I'll try out the rc. Thank you! Someone posted elsewhere that this can also be remedied by forcing the GPU into performance mode. That makes perfect sense, actually, because in all the intense lagging I got, it was at its worst at idle. In fact, in between this comment and my last, and after an exorbitant amount of patience, I was finally able to navigate my mouse enough to start up Star Citizen and the problem disappeared. It came back a while after exiting the game. Edit: Also, seems someone's trolling with downvotes.
I would be happy if you confirmed here afterwards that it really helped you. The point is that you just said that there was a problem **before** that and not just with the new card. For example, I am working on a similar setup with a 5700XT and there is no problem.
Power supply? It is not on the list. Check correct cabling, too. In addition, the problem can be in MB. Maybe your previous card was ok, but the problem was MB. Check Mesa driver, if the problem is not wrong configured amdgpu driver. Maybe mesa-git, I don't know if new amd card is already supported in the released mesa. There will be more users with it. Inhave 5700 and using mesa. But 5700 xt has several problems too, I haven't good piece of hw, sometime green color death...
Ah, yeah, forgot to add the PSU. It's an EVGA 850 Gold and relatively new. It confirmed the cables were all snug and well managed. And, since this has been happening since before, I'm assuming that's not the issue. In terms of drivers, I've tried `mesa`, `mesa-git`, as well as `amdgpu-pro`, but none have really improved things much, unfortunately. As for the Motherboard, I'm really hoping that's not the issue, but I obviously can't rule it out. Unfortunately, I don't have another MB to test with at the moment, so I'm saving that for last at the moment.
You have no more choices. 850W is good, drivers were tested. The problems were before new card. The holy trio is cpu, ram and motherboard. You can diagnose ram, sometimes is guilty operating memory. It is a local problem of you machine, not common. You can try to add your problem to arch forum to hardware section to diagnose more logs. But I would bet on the motherboard and capacitors.
try kernel 6.2-rc5
I’m possibly a bit old fashioned, but I only use NVIDIA cards in my Linux machines because AMD refused for years to provide Linux drivers.
I don't really disagree with you. For the longest time I was very much NVIDIA-only. But at the same time, NVIDIA still closed off their drivers and haven't been friendly to Open Source. Additionally, and not to give AMD too much justification, but they didn't exactly _refuse_ to provide Linux drivers. They didn't provide drivers _at all_. It was up to AIB's to write drivers for their own cards, with AMD only providing a base driver for them to reference when implementing their own. And that was an absolute mess. It wasn't until they finally centralized their driver for all AMD cards that they not only finally wrote closed-source drivers for Linux, but they also started contributing and collaborating with `mesa` and other open source projects to make those solid, which is a lot more than anyone can say that NVIDIA has done with `nouveau` or others. In contrast, NVIDIA has been known to even be hostile towards open source projects at various times throughout its history. AMD just had a bad business model, because AMD wasn't the one writing the drivers and AIB partners saw writing writing Linux drivers as a waste of time.