[amdgpu] wayland black screen with white flashes, display corruption, kernel 5.13

[Eugene Savelov]

After upgrade from ubuntu 21.04 to ubuntu 21.10 I am seeing black screen in wayland session and screen corruption in Xorg session

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 16 15:49:45 2021
DistUpgraded: 2021-10-16 08:19:20,349 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: impish
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1b70]
InstallationDate: Installed on 2020-11-20 (329 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: ASUSTeK COMPUTER INC. X505BA
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro iommu=soft quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
dmi.bios.date: 04/02/2020
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X505BA.317
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X505BA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X505BA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: eugene 2026 F.... pulseaudio
 /dev/snd/controlC0: eugene 2026 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
InstallationDate: Installed on 2020-11-20 (329 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: ASUSTeK COMPUTER INC. X505BA
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=40f47434-863f-48cf-9af2-41e67323cb0c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
RelatedPackageVersions:
 linux-restricted-modules-5.13.0-19-generic N/A
 linux-backports-modules-5.13.0-19-generic N/A
 linux-firmware 1.201
Tags: impish wayland-session
Uname: Linux 5.13.0-19-generic x86_64
UpgradeStatus: Upgraded to impish on 2021-10-16 (0 days ago)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/02/2020
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X505BA.317
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X505BA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX505BA.317:bd04/02/2020:br5.12:svnASUSTeKCOMPUTERINC.:pnX505BA:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnX505BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X505BA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[alex14641 (alex14641-linux-kernel-bugs)]

If I close my laptop lid and reopen it, the screen stays blank. Reverting the following commit fixes the issue:

commit 9127daa0a8d88a6e6452eb8b7c9be4c3f42a867e
Author: Stylon Wang <email address hidden>
Date: Tue Mar 2 19:25:56 2021 +0800

    drm/amd/display: Guard ASSR with internal display flag

    [Why]
    ASSR enabling only considers capability declared in DPCD.
    We also need to check whether the connector is internal.

    [How]
    ASSR enabling need to check both DPCD capability and internal display
    flag.

    Signed-off-by: Stylon Wang <email address hidden>
    Reviewed-by: Harry Wentland <email address hidden>
    Acked-by: Anson Jacob <email address hidden>
    Tested-by: Dan Wheeler <email address hidden>
    Signed-off-by: Alex Deucher <email address hidden>

[alex14641 (alex14641-linux-kernel-bugs)]

The graphics card is a RX580.

[alexdeucher (alexdeucher-linux-kernel-bugs)]

Can you try the patch here:
https://gitlab.freedesktop.org/drm/amd/-/issues/1620

[alex14641 (alex14641-linux-kernel-bugs)]

That patch works.

[alexdeucher (alexdeucher-linux-kernel-bugs)]

Fix is in 5.14 and should land in stable shortly:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6be50f5d83adc9541de3d5be26e968182b5ac150

[Eugene Savelov (savelov)]

Issue seems related to amggpu changes, and similar to this fedora bug - https://bugzilla.redhat.com/show_bug.cgi?id=1984686.
Workaround - running old 5.11 kernel in ubuntu 21.10

[Eugene Savelov (savelov)]

workaround is to use amdgpu.dc=0 boot kernel option

[Eugene Savelov (savelov)]

resolved by removing iommu=soft option which was preserved from workaround of bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921995
now kernel boots fine and wayland session and amdgpu works fine

[Eugene Savelov (savelov)]

issue can be reproduced when notebook is returning from sleep - black screen with white flashes.
was able to press Ctrl-Alt-F2 + Ctrl+Alt-Del - it restarted successfully, however no errors seen in kernel logs - besides below:

ERROR: apport (pid 16076) Sat Oct 16 17:46:05 2021: host pid 3575 crashed in a separate mount namespace, ignoring
ERROR: apport (pid 16078) Sat Oct 16 17:46:05 2021: host pid 4345 crashed in a separate mount namespace, ignoring
ERROR: apport (pid 16077) Sat Oct 16 17:46:05 2021: host pid 3467 crashed in a separate mount namespace, ignoring
ERROR: apport (pid 16079) Sat Oct 16 17:46:05 2021: host pid 3876 crashed in a separate mount namespace, ignoring
ERROR: apport (pid 16085) Sat Oct 16 17:46:06 2021: host pid 12222 crashed in a separate mount namespace, ignoring

(crashes from firefox) -
ct 16 17:46:04 eugene-X505BA kernel: [ 5029.860472] WebExtensions[3575]: segfault at 0 ip 00007fe5c63d7e24 sp 00007fff52c6fb08 error 6 in lib
xkbcommon.so.0.0.0[7fe5c63c1000+1c000]
Oct 16 17:46:04 eugene-X505BA kernel: [ 5029.860491] Code: 45 48 48 8b 04 d8 48 83 c4 08 5b 5d c3 66 0f 1f 84 00 00 00 00 00 48 83 c4 08 31 c0
 5b 5d c3 0f 1f 80 00 00 00 00 f3 0f 1e fa <83> 07 01 48 89 f8 c3 0f 1f 44 00 00 f3 0f 1e fa 48 85 ff 74 37 55
Oct 16 17:46:05 eugene-X505BA kernel: [ 5029.933516] audit: type=1400 audit(1634395565.034:99): apparmor="DENIED" operation="open" profile="sn
ap.firefox.firefox" name="/proc/3467/environ" pid=2642 comm=427265616B70616420536572766572 requested_mask="r" denied_mask="r" fsuid=1000 ouid=
1000

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Eugene Savelov (savelov)]

apport information

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[Eugene Savelov (savelov)]

reproduced again with fresh notebook boot, dm prompt display fine, but after choosing login and session type(wayland) and password, display goes black with white flashes (either horizontal or vertical).
after booting old 5.11 kernel, which works fine in wayland session, restart with 5.13 kernel, also works fine. Apparently some display initialization is missing

[Eugene Savelov (savelov)]

issue affects only main integrated display of notebook, external HDMI display worked fine

[Eugene Savelov (savelov)]

linux kernel log with drm.debug=14 log_buf_len=16M added to cmd line

issue is with eDP display, which should be 1366*768

[drm:drm_helper_probe_single_connector_modes [drm_kms_helper]] [CONNECTOR:49:eDP-1] probed modes :
[drm:drm_mode_debug_printmodeline [drm]] Modeline "1366x768": 60 76300 1366 1414 1446 1592 768 771 777 798 0x48 0x9

[Eugene Savelov (savelov)]

https://gitlab.freedesktop.org/drm/amd/-/issues/1644

[Eugene Savelov (savelov)]

I could not apply patches from freedesktop bugtracker as kernel revision in ubuntu is quite different from mainline

resolved after I disabled secure boot and installed latest 5.14 mainline builds - https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.14.12/

also bug with brightness is gone in this build

[Eugene Savelov (savelov)]

issue still reproduced with latest proposed kernel update (5.13.0-20.20)

[Eugene Savelov (savelov)]

still reproduced with latest proposed kernel (5.13.0-21-generic)
test case:
turn secure boot on
cold boot ubuntu
authenticate and launch wayland session
result - display goes black

[Eugene Savelov (savelov)]

still not resolved with latest proposed kernel - 5.13.0.22.33.
to reproduce need to cold boot the PC - I had to wait overnight to reproduce it

[Eugene Savelov (savelov)]

seems to be resolved with 5.13.0-28-generic release

[Eugene Savelov (savelov)]

assuming fixed by this patchset -https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1955180

[Abylay (sandbernar)]

i have same issue: amd cpu + nvidia gpu on nvidia 495 driver. since kernel 5.13 and still on kernel 5.13.0-28 laptop screen is black with white flickering but the monitor attached via hdmi works fine. Could you explain workaraound if exists?

[Eugene Savelov (savelov)]

a workaround could be updating to mainline kernel