Description of problem: Monitor was asleep. Moved the mouse and hit the "Enter" key to wake up the display. SDDM unlock screen was shown, and then mouse/keyboard become 100% unresponsive. **rant about NULL dereference and AMD removed** Additional info: reporter: libreport-2.9.5 BUG: unable to handle kernel NULL pointer dereference at 0000000000000208 PGD c22384067 P4D c22384067 PUD c24a11067 PMD 0 Oops: 0000 [#1] SMP NOPTI Modules linked in: fuse ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack 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 iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables sunrpc btrfs amd64_edac_mod xor edac_mce_amd zstd_compress kvm_amd ccp kvm raid6_pq irqbypass libcrc32c crct10dif_pclmul zstd_decompress crc32_pclmul xxhash ghash_clmulni_intel joydev snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hda_core ipmi_si snd_hwdep ipmi_devintf snd_seq ipmi_msghandler snd_seq_device k10temp fam15h_power snd_pcm sp5100_tco snd_timer i2c_piix4 snd soundcore shpchp acpi_cpufreq raid1 amdkfd amd_iommu_v2 amdgpu hid_logitech_hidpp chash i2c_algo_bit gpu_sched drm_kms_helper ttm ata_generic pata_acpi drm crc32c_intel mpt3sas serio_raw e1000e pata_atiixp hid_logitech_dj raid_class scsi_transport_sas CPU: 18 PID: 1807 Comm: Xorg Not tainted 4.17.6-200.fc28.x86_64 #1 Hardware name: ASUSTeK Computer INC. KGP(M)E-D16/KGP(M)E-D16, BIOS 3201 02/19/2013 RIP: 0010:create_stream_for_sink+0x2cd/0x650 [amdgpu] RSP: 0018:ffffb21347ddb9d0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff9f3224308400 RCX: 0000000000000000 RDX: 0000000000000013 RSI: ffffffffc0686430 RDI: ffff9f32243084ac RBP: ffffb21347ddbb10 R08: 0000000000000f00 R09: 0000000000000870 R10: ffff9f3224308400 R11: 0000000000000f00 R12: ffff9f261f97b000 R13: 0000000000000000 R14: ffff9f2a101fe380 R15: ffff9f31ce9a8000 FS: 00007f4b28177ac0(0000) GS:ffff9f3236c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000208 CR3: 0000000c22b0a000 CR4: 00000000000406e0 Call Trace: dm_update_crtcs_state+0x26c/0x4d0 [amdgpu] amdgpu_dm_atomic_check+0x1b1/0x3b0 [amdgpu] drm_atomic_check_only+0x360/0x4f0 [drm] drm_atomic_commit+0x13/0x50 [drm] drm_atomic_connector_commit_dpms+0xdb/0x100 [drm] drm_mode_obj_set_property_ioctl+0x178/0x280 [drm] ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm] drm_mode_connector_property_set_ioctl+0x39/0x60 [drm] drm_ioctl_kernel+0x5b/0xb0 [drm] drm_ioctl+0x1b3/0x370 [drm] ? drm_mode_connector_set_obj_prop+0x80/0x80 [drm] amdgpu_drm_ioctl+0x49/0x80 [amdgpu] do_vfs_ioctl+0xa4/0x610 ksys_ioctl+0x60/0x90 __x64_sys_ioctl+0x16/0x20 do_syscall_64+0x5b/0x160 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f4b253a8ec7 RSP: 002b:00007ffda2d7cbf8 EFLAGS: 00003246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f4b253a8ec7 RDX: 00007ffda2d7cc30 RSI: 00000000c01064ab RDI: 0000000000000018 RBP: 00007ffda2d7cc30 R08: 00000000016cbe60 R09: 00000000017bdf50 R10: 0000000000000018 R11: 0000000000003246 R12: 00000000c01064ab R13: 0000000000000018 R14: 00000000017bdf50 R15: 0000000001679fb0 Code: 49 c7 87 28 60 00 00 00 00 00 00 4c 89 bb 98 01 00 00 e8 c7 f9 ff ff 4d 8b ac 24 50 04 00 00 ba 13 00 00 00 48 8d bb ac 00 00 00 <41> 0f b7 85 08 02 00 00 49 8d b5 12 02 00 00 89 83 c0 00 00 00 RIP: create_stream_for_sink+0x2cd/0x650 [amdgpu] RSP: ffffb21347ddb9d0 CR2: 0000000000000208
Created attachment 1460260 [details] File: dmesg
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and let us know if the bug is still present on the latest kernel. (Please note: sometimes bugs get mistakenly closed during our mass closing. If you think your bug was closed in error please reopen)