Bug 205589

Summary: Green screen crash with 3400G
Product: Drivers Reporter: pkk
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: NEW ---    
Severity: normal CC: alexdeucher
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 5.x Subsystem:
Regression: No Bisected commit-id:

Description pkk 2019-11-20 12:56:24 UTC
When I log into XFCE with a 5.x kernel on  my AMD Ryzen 5 3400G-based system, the screen turns solid dark green; it stays that way until reboot.

I see this issue on Debian GNU/Linux:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944420

Three others see the same issue on Manjaro:

https://forum.manjaro.org/t/manjaro-with-ryzen-3-3200g-vega-8-any-experience/110497/23
https://forum.manjaro.org/t/kernel-question-amd-ryzen-5-2400g-with-radeon-vega-graphics/106683/5


Philipp
Comment 1 Alex Deucher 2019-11-20 15:39:55 UTC
Is this a regression?  If so, can you bisect?  Please attach your xorg log (if using X) and dmesg output.
Comment 2 pkk 2019-11-20 17:27:28 UTC
Out of the three Manjaro reports, only one is about the 3400G, the other two are about the 2400G, but the symptoms seem to be the same.

My dmesg output is at:

http://www.colecovision.eu/stuff/dmesg-log

In 5.2, I get the green screen crash about 60% of the time when I try to log into XFCE. In 5.3 I get it nearly always.

I used an AGESA 1.0.0.3 ABBA BIOS.

I'll get the Xorg log and will check with an AGESA 1.0.0.4 B BIOS tonight or tomorrow.
Comment 4 pkk 2019-11-21 13:43:43 UTC
Today, I've also installed a 5.1.21 kernel from Ubuntu on my Debian GNU/Linux testing system, and logged into XFCE thrice. I did not see the green screen crash with that kernel, though one I got a crash (system frozen, only mouse pointer still moveable) a few minutes after logging in.
Comment 5 pkk 2019-12-04 09:58:32 UTC
Looks like someone has a very similar problem (green screen crash on 5.3 and 5.4 kernels on Ryzen Vega APU) with Civ 6:

https://gitlab.freedesktop.org/drm/amd/issues/983
Comment 6 pkk 2020-04-10 07:05:04 UTC
I cannot reproduce the issue using kernel 5.5.