Bugzilla – Bug 1223548
Renoir/Cezanne Crashing on 3D Game/Project Usage Randomly but Frequently - NOT PRESENT ON OTHER OS
Last modified: 2024-05-04 13:30:54 UTC
Created attachment 874573 [details] PDF from post on Freedesktop Renoir/Cezanne Crashing on 3D Game/Project Usage Randomly but Frequently - NOT PRESENT ON OTHER OS I posted this to AMD Issues on Freedesktop: https://gitlab.freedesktop.org/drm/amd/-/issues/3335 The issue was closed but I thought it a good idea to post it here. Major issues using Tumbleweed with this APU. Games/3D crashes (hard crashes) every few minutes. Can only obtain crash data via SSH unfortunately I'm not well versed in that. I have been using OpenSUSE Tumbleweed for about 10 years. Hoping to raise awareness by posting this. Essentially, all issues went away when I switched to POP OS as a test. I believe they use an LTS kernel? ------------- I use OpenSUSE Tumebleweed (Plasma). I have tried numerous Kernel Parameters, Wayland vs Xorg, power profiles, CoreCTRL. I can't produce the issue at will it just happens rather regularly. Essentially, any game sometimes after a few minutes sometimes within an hour will lock up and I am forced to reboot. I have never reported a bug here so I apologize if I'm missing something or not doing something correctly. I just don't know else to do, I'm at a loss. Operating System: openSUSE Tumbleweed 20240419 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-1-default (64-bit) Graphics Platform: X11 Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 15.0 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 81YM System Version: IdeaPad 5 14ARE05 I wiped the laptop and installed Windows 10 from my Lenovo recovery. I had to do this to update my bios. I updated my bios. Installed OpenSUSE Tumbleweed alongside Windows and the issue persists. Running the following command allows me to at least kill the game running before it locks up the laptop: amdgpu.runpm=0 POP OS DOES NOT HAVE THIS ISSUE. SWITCHING AND I HAVE HAD ZERO CRASHES.
If PopOS kernel works, you can compare the difference -- either the difference of the kernel base version (where Tumbleweed is always newer), some downstream patches, firmware issue, or depending on Mesa or whatever. Without those data points, we can't help much, unfortunately. If you're willing to chase the bugs yet on Tumbleweed, we can continue, e.g. I can build a test kernel Mario suggested in the upstream bug tracker. If not interested, we have to close this bug entry, as there is no point to go further.
I'm willing to get to the bottom of this as best I can with the knowledge set that I have. I'm happy to chase these as I feel it will help others later and hopefully identify some potentially related longer standing bugs with AMD gpus. Happy to help. Please let me know how to proceed. -Padre
OK, a test kernel based on 6.8.8 with a potential crash fix patch for Tumbleweed is being built in OBS home:tiwai:bsc1223548 repo. Once after the build finishes (takes an hour or so), it'll appear at http://download.opensuse.org/repositories/home:/tiwai:/bsc1223548/standard/ Please give it a try later.
(In reply to Takashi Iwai from comment #3) > OK, a test kernel based on 6.8.8 with a potential crash fix patch for > Tumbleweed is being built in OBS home:tiwai:bsc1223548 repo. Once after the > build finishes (takes an hour or so), it'll appear at > http://download.opensuse.org/repositories/home:/tiwai:/bsc1223548/standard/ > Please give it a try later. Very strange. I wiped the drive, reinstalled OpenSUSE, and I can't duplicate the issue. Perhaps I had a bad update or bad install. I'm not quite sure.
OK, then I close as FIXED for now. It could be a firmware issue or an intermittent breakage. Feel free to reopen if you encounter the problem again. Also, it'd appreciated if you can update the description in the upstream gitlab issue, too.
(In reply to Takashi Iwai from comment #5) > OK, then I close as FIXED for now. It could be a firmware issue or an > intermittent breakage. > > Feel free to reopen if you encounter the problem again. Also, it'd > appreciated if you can update the description in the upstream gitlab issue, > too. Thank you I will! Enjoy your weekend!