Fedora Account System
Red Hat Associate
Red Hat Customer
I started seeing this in fedora 32 and onward (not sure if related to the solved f34 gnome wakeup bug or not), but at least my gnome session is no longer terminated. kernel-5.11.21-300.fc34, mesa-21.0.3-2.fc34, gnome-shell-40.1-1.fc34.x86_64 kernel-5.12.5-300.fc34, mesa-21.1.1-1.fc34, gnome-shell-40.1-1.fc34.x86_64 How reproducible: always. Steps to reproduce: 1. log out or lock your computer. 2. wait for your monitor to go black. 3. press a random key or move your mouse to wake it up. 4. now sign back in, check dmesg for errors. [ 1.810714] [drm] amdgpu kernel modesetting enabled. [ 1.810811] amdgpu: Topology: Add CPU node [ 1.810849] fb0: switching to amdgpudrmfb from EFI VGA [ 1.810940] amdgpu 0000:01:00.0: vgaarb: deactivate vga console [ 1.811045] amdgpu 0000:01:00.0: amdgpu: Trusted Memory Zone (TMZ) feature not supported [ 1.811244] amdgpu 0000:01:00.0: No more image in the PCI ROM [ 1.811255] amdgpu 0000:01:00.0: amdgpu: Fetched VBIOS from ROM BAR [ 1.811256] amdgpu: ATOM BIOS: MS-V34113-F1 [ 1.812367] amdgpu 0000:01:00.0: amdgpu: VRAM: 8192M 0x000000F400000000 - 0x000000F5FFFFFFFF (8192M used) [ 1.812369] amdgpu 0000:01:00.0: amdgpu: GART: 256M 0x000000FF00000000 - 0x000000FF0FFFFFFF [ 1.812463] [drm] amdgpu: 8192M of VRAM memory ready [ 1.812465] [drm] amdgpu: 8192M of GTT memory ready. [ 1.822339] amdgpu: hwmgr_sw_init smu backed is polaris10_smu [ 2.139932] amdgpu: Topology: Add dGPU node [0x67df:0x1002] [ 2.139935] amdgpu 0000:01:00.0: amdgpu: SE 4, SH per SE 1, CU per SH 9, active_cu_number 36 [ 2.141884] fbcon: amdgpudrmfb (fb0) is primary device [ 2.141886] amdgpu 0000:01:00.0: [drm] fb0: amdgpudrmfb frame buffer device [ 2.153730] amdgpu 0000:01:00.0: amdgpu: Using BOCO for runtime pm [ 2.153998] [drm] Initialized amdgpu 3.40.0 20150101 for 0000:01:00.0 on minor 0 [ 19.307852] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) [ 913.385800] [drm:retrieve_link_cap [amdgpu]] *ERROR* retrieve_link_cap: Read dpcd data failed. [ 1047.704126] [drm:retrieve_link_cap [amdgpu]] *ERROR* retrieve_link_cap: Read dpcd data failed. [ 3642.104139] [drm:retrieve_link_cap [amdgpu]] *ERROR* retrieve_link_cap: Read dpcd data failed. 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3417 Kernel driver in use: amdgpu Kernel modules: amdgpu
I see these [drm:retrieve_link_cap [amdgpu]] *ERROR* retrieve_link_cap: Read dpcd data failed. messages as well, when I wake my System from Standby (S3) The side effect is, that my primary screen an AsusROG Strix XG27WQ does not wake up or takes ages to. Also I see random black screens while working. I also have a similar Videocard: 0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev c7) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device 22df Flags: bus master, fast devsel, latency 0, IRQ 106, IOMMU group 2 Memory at 7c00000000 (64-bit, prefetchable) [size=8G] Memory at 7e00000000 (64-bit, prefetchable) [size=2M] I/O ports at f000 [size=256] Memory at fce00000 (32-bit, non-prefetchable) [size=256K] Expansion ROM at fce40000 [disabled] [size=128K] Capabilities: [48] Vendor Specific Information: Len=08 <?> Capabilities: [50] Power Management version 3 Capabilities: [58] Express Legacy Endpoint, MSI 00 Capabilities: [a0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [100] Vendor Specific Information: ID=0001 Rev=1 Len=010 <?> Capabilities: [150] Advanced Error Reporting Capabilities: [200] Physical Resizable BAR Capabilities: [270] Secondary PCI Express Capabilities: [2b0] Address Translation Service (ATS) Capabilities: [2c0] Page Request Interface (PRI) Capabilities: [2d0] Process Address Space ID (PASID) Capabilities: [320] Latency Tolerance Reporting Capabilities: [328] Alternative Routing-ID Interpretation (ARI) Capabilities: [370] L1 PM Substates Kernel driver in use: amdgpu Kernel modules: amdgpu
@itrymybest80 How are your screens connected? I observe this error when I have two screens connected to two DP-Ports. If I connect one Screen to HDMI and one to DP, I do not observe this behaviour. I think it is really an amdgpu issue, that got reported many times on different bugzillas.
I've got a single ASUS MG248QR 1080p/144hz/freesync monitor connected through DP. I've also tried using the other DP port, but get the same result.
I had a picture (.jpeg) open in fullscreen, locked my computer, screen went black, logged back on and my session was terminated. [31441.628994] [drm:retrieve_link_cap [amdgpu]] *ERROR* retrieve_link_cap: Read dpcd data failed. [31468.482611] show_signal_msg: 95 callbacks suppressed [31468.482614] gnome-shell[2288]: segfault at ffffffff0000009a ip 00007f57f17f2775 sp 00007fff8f2e5e00 error 5 in libmutter-8.so.0.0.0[7f57f171c000+12f000] gnome-shell-40.3-1.fc34.x86_64 mutter-40.3-1.fc34.x86_64 kernel-5.13.6-200.fc34.x86_64 mesa 21.1.5-1 x86_64
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.