You are not logged in.
Pages: 1
Topic closed
Hello, I am not sure who to report to but I have a serious problem for almost 5 months now regarding on Linux Kernel, and Vulkan Mesa.
My Laptop specs:
CPU: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx (8) @ 2.000GHz
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series
My laptop crashes every hour. Or whenever I play games, it crashes within few minutes. I did found a solution. A simple line in grub.cfg.
rcu_nocbs=0-3 idle=nomwait
It never crashes. Only up to 5.1.14 linux Kernel version. Any version after that, it crashes every hour. I no longer update linux kernel, and headers.
There is a major update regarding on LLVM 9.0. I decided to update everything including the Kernel. It crashes every 30 minutes or so. It is much worse than before. For some reason, the rcu_nocb=0-3 no longer works after this. That command line is what stops the cpu/gpu from crashing. Now it just crashes.
On top of that, updating Linux Kernel to the latest version produces Graphic Screen Tearing.
I roll LLVM and Kernel back to see if it stop crashing. It still crash. I forgot to roll back CLANG, so I did that. It doesn't crash. But gaming performance is horrible. I don't know how to roll back the AUR "mesa-aco-git." Before all of this update, everything including gaming was smooth like a butter..
There is some weird funky stuff going on between Linux5.1.14< and Mesa.
If I have some time, I might give Linux-zen or Linux-CX a shot. If those doesn't work, I have to force myself to use Linux-LTS since this day and forward until they fix this issue.
I am curious if anybody else with Ryzen Mobile Chips has an issue with this. Thanks.
Edited:
Alright. I did more testing. I decided to re-update the LLVM, and Vulkan again. SO far so good. No strange behaviors going on. I am lead to believe it has nothing to do with vulkan, and mesa. Linux kernel is the culprit.
Last edited by FooisOP (2019-10-27 02:55:25)
Offline
I have the laptop with the same specs of Ryzen Modile 2500U, Huawei Matebook D 14 (AMD version), and ArchLinux runs great. It is fully updated with latest kernel, mesa, GNOME and Wayland. I explicitly opted for AMD version for Vega graphics instead or Intel/MX150. It also dual-boot with Windows 10, but I am getting less and less into Windows 10.
Last edited by liewkj (2019-10-28 05:53:07)
Offline
Hey, same here.
I am wondering if the firmware might be an issue. I have not updated bios / cpu firmware since beginning of this year. There are few firmware that are updated. However, I need windows to update it. That's the downfall.
is your firmware up to date as well? I noticed you do use windows 10.
Offline
Yes, my firmware is up to date, date marked 2019-05-28 version 1.22 from Huawei support website. I also have the latest AMD microcode update on ArchLinux.
local/amd-ucode 20191022.2b016af-1
Microcode update files for AMD CPUs
Offline
I switch to Windows to update all of the hardware firmware. Everything is up to date. I switch back to Linux. I updated everything including the Linux Kernel to the latest. amd-ucode is updated, and it is in grub.cfg.
I still get graphic tearing, and kernel crashes when I play games.
Offline
Well, that is hard to say then. At my age, I don't play contemporary games. Occasionally, I enjoyed flash-back style of gaming through DOSBox, emulation or source ports, mostly old stuffs. I run Chromium-vaapi for YouTube videos. So far, all those are fine on ArchLinux. I don't play contemporary games on Windows, too. Basically, it is almost the same stuffs on Windows and ArchLinux.
Offline
I decided to re-install the entire system from scratch, hoping it would clear up issues. Nope. I still get graphic tearing. Especially on firefox and youtube, the graphic tearing is horrible. I did disable the hardware acceleration and layer acceleration and nothing. I also put no tearing in xorg/20-amdgpu.conf. It did help to greater degree. However I still get graphic tearing every once awhile.
It also doesn't play well with bspwm. It lags pretty bad.
5.1.14 or less, I don't even have graphic tearing. 5.3 versions are terrible. I hope 5.4 will fix the issue.
I even gave linux-ck a shot. I still got the exact same issue.
I can't even downgrade to 5.1.14 anymore. Now I am getting this error.
linux: /boot/vmlinuz-linux exists in filesystem
Last edited by FooisOP (2019-11-04 23:31:06)
Offline
I decided to re-install the entire system from scratch, hoping it would clear up issues. Nope. I still get graphic tearing. Especially on firefox and youtube, the graphic tearing is horrible. I did disable the hardware acceleration and layer acceleration and nothing. I also put no tearing in xorg/20-amdgpu.conf. It did help to greater degree. However I still get graphic tearing every once awhile.
It also doesn't play well with bspwm. It lags pretty bad.
5.1.14 or less, I don't even have graphic tearing. 5.3 versions are terrible. I hope 5.4 will fix the issue.
I even gave linux-ck a shot. I still got the exact same issue.
I can't even downgrade to 5.1.14 anymore. Now I am getting this error.
linux: /boot/vmlinuz-linux exists in filesystem
I have seen this issue on my RX580 since around that same build....I've noticed if I turn off the 2nd monitor WHILE the game is playing, the tearing stops and is gone until I reboot.
Offline
Try adding iommu=pt as kernel parameter, this fixed hangs and graphical glitches for me on 2500u
Offline
I been waiting for 5.4 update. It finally arrived few days ago. I gave a shot. I hoped that it'll fix the issue. Again, the issue between 5.14 to 5.3 has major graphic glitches, and kernel crashes. After the upgrade, I added "iommu=pt". No more graphic glitches. No more kernel freezes. I decided to play few stress test games and it has not crashed yet.
5.4 and immu=pt fixed the problem. Thanks!
Offline
The immu=pt seems to fix hanging on my 2500u, too, on 5.4.1 kernel, thanks!
Offline
The correct value is: iommu=pt
See Preycon at 2019-11-10 08:11:33
The last two submits missed the "o"!
Offline
I'm sure whatever typo was seen will have been found after 7 years. Don't necrobump old topics.
Closing.
Offline
Pages: 1
Topic closed