Description of problem: I put my PC into suspend and when I brought it back up it looked like this https://imgur.com/a/9dOCH3X Additional info: reporter: libreport-2.9.5 WARNING: CPU: 1 PID: 3531 at drivers/gpu/drm/radeon/radeon_object.c:84 radeon_ttm_bo_destroy+0xfd/0x110 [radeon] Modules linked in: fuse xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack devlink ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc squashfs zstd_decompress xxhash loop intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul eeepc_wmi iTCO_wdt asus_wmi sparse_keymap snd_hda_codec_realtek rfkill gpio_ich iTCO_vendor_support wmi_bmof mxm_wmi snd_hda_codec_generic ghash_clmulni_intel snd_hda_codec_hdmi intel_cstate intel_uncore intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm joydev snd_timer snd mei_me lpc_ich mei i2c_i801 soundcore shpchp ie31200_edac video wmi amdgpu chash gpu_sched radeon i2c_algo_bit drm_kms_helper ttm drm crc32c_intel r8169 mii CPU: 1 PID: 3531 Comm: steam Not tainted 4.17.3-200.fc28.x86_64 #1 Hardware name: System manufacturer System Product Name/P8Z77-M, BIOS 2105 09/10/2013 RIP: 0010:radeon_ttm_bo_destroy+0xfd/0x110 [radeon] RSP: 0018:ffffc0cf0b28bcd8 EFLAGS: 00010287 RAX: ffff9de7bcb70780 RBX: ffff9de7aa26a868 RCX: 0000000000000000 RDX: ffff9de7aa26aad0 RSI: ffff9de7aa26a800 RDI: ffff9de7cd4e9b80 RBP: ffffffffffffffff R08: ffff9de7a702ae40 R09: 000000018040003e R10: fffff859c79c0a80 R11: ffff9de7aa26aa00 R12: ffff9de7aa26a800 R13: 00000000000008a0 R14: ffff9de7cd4e8740 R15: ffff9de74e887800 FS: 0000000000000000(0000) GS:ffff9de7dec80000(0063) knlGS:00000000f7956700 CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033 CR2: 00000000e92c01c0 CR3: 00000001d8dae006 CR4: 00000000001606e0 Call Trace: ttm_bo_release_list+0x118/0x150 [ttm] ? drm_gem_handle_create+0x40/0x40 [drm] radeon_bo_unref+0x35/0x60 [radeon] radeon_gem_object_free+0x33/0x50 [radeon] drm_gem_object_release_handle+0x51/0x90 [drm] drm_gem_handle_delete+0x55/0x80 [drm] ? drm_gem_handle_create+0x40/0x40 [drm] drm_ioctl_kernel+0x5b/0xb0 [drm] drm_ioctl+0x1b3/0x370 [drm] ? drm_gem_handle_create+0x40/0x40 [drm] ? __vfs_write+0x5b/0x170 __ia32_compat_sys_ioctl+0x2de/0x11b0 ? ksys_write+0x9c/0xb0 do_fast_syscall_32+0xa7/0x254 entry_SYSENTER_compat+0x7f/0x91 Code: 80 02 00 00 74 0f 48 8b b3 b0 01 00 00 48 89 ef e8 e9 76 f5 ff 48 89 ef e8 a1 8d f4 ff 4c 89 e7 5b 5d 41 5c 41 5d e9 43 00 09 fc <0f> 0b eb c6 0f 1f 44 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f
Created attachment 1457225 [details] File: dmesg
This is a duplicate of bug #1575288.
(In reply to Christian Stadelmann from comment #2) > This is a duplicate of bug #1575288. Do you happen to know how I can fix it? It popped up saying problem reporter so I hit report bug, I clicked on that link but I don't see any fix.
(In reply to dzyn641 from comment #3) > (In reply to Christian Stadelmann from comment #2) > > This is a duplicate of bug #1575288. > > Do you happen to know how I can fix it? It popped up saying problem reporter > so I hit report bug, I clicked on that link but I don't see any fix. No, sorry.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.