AMD

AMD RADEON VEGA stops working after upgrade 19.04 => 19.10

Bug #1849936 reported by Pierre-Yves
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
AMD
Confirmed
Undecided
Unassigned
linux (Ubuntu)
Confirmed
Undecided
Unassigned
linux-firmware (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hello, after upgrading Xubuntu 19.04 => 19.10, I have a display problem. Large color pixels appear around the mouse cursor, it flickers and blinks.
I have the problem starting with the kernel 5.3.0-19-generic. I re-did a clean install, it's the same (except for a black screen at the 1st reboot, then after starting in debug mode, return to the situation above).

I have no problem with the 5.0.0-32 generic kernel (last Kernel supplied with the 19.04. However, I would like to use next kernels...)

My processor is an AMD Ryzen 3 and my graphics card (integrated) AMD RADEON VEGA. I thought of a video driver problem (but AMD does not provide it yet for Ubuntu 19.10 and I did not need it with 19.04).

Thanks for your help.

PS: I would have stayed on 18.04 LTS but I also had a display problem, set from 18.10 ...
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: pierre-yves 1711 F.... pulseaudio
 /dev/snd/controlC0: pierre-yves 1711 F.... pulseaudio
CurrentDesktop: XFCE
Dependencies:

DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-10-22 (23 days ago)
InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2)
MachineType: Micro-Star International Co., Ltd MS-7B38
Package: linux-firmware 1.183.1
PackageArchitecture: all
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=UUID=ff999487-0645-497b-af2a-b0ed3ea8169d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-32-generic N/A
 linux-backports-modules-5.0.0-32-generic N/A
 linux-firmware 1.183.1
Tags: eoan
Uname: Linux 5.0.0-32-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-22 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/15/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.80
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A320M PRO-VD PLUS (MS-7B38)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.80:bd03/15/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7B38:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnA320MPRO-VDPLUS(MS-7B38):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7B38
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd

information type: Proprietary → Public
description: updated
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1849936

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: eoan
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

What's the full model number of the cpu?

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : AlsaInfo.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : CRDA.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : IwConfig.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : Lspci.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : Lsusb.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : ProcEnviron.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : ProcModules.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : PulseList.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : RfKill.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : UdevDb.txt

apport information

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote : WifiSyslog.txt

apport information

Changed in amd:
status: New → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux-firmware (Ubuntu):
status: New → Confirmed
Revision history for this message
Pierre-Yves (pierreyves-legal) wrote :

model name : AMD Ryzen 3 2200G with Radeon Vega Graphics

Do you want the full "cat /proc/cpuinfo" ?

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote :

I have the same bug with last kernel 5.3.0-22-generic.

Revision history for this message
Pierre-Yves (pierreyves-legal) wrote :

Last news : in recovery mode with kernel last kernel 5.3.0-22-generic, the display is normal. In standard mode, it is buggy.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.