Description of problem: Logged in to a system that was in sleep mode Additional info: reporter: libreport-2.9.3 WARNING: CPU: 0 PID: 22492 at drivers/gpu/drm/nouveau/nvif/vmm.c:71 nvif_vmm_put+0x6a/0x80 [nouveau] 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 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 binfmt_misc sunrpc vfat fat intel_rapl snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass iTCO_wdt crct10dif_pclmul iTCO_vendor_support crc32_pclmul ghash_clmulni_intel intel_cstate snd_hda_codec_realtek intel_uncore snd_hda_codec_generic intel_rapl_perf snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer snd mei_me soundcore i2c_i801 lpc_ich mei shpchp pcc_cpufreq nouveau video i2c_algo_bit drm_kms_helper mxm_wmi ttm drm crc32c_intel e1000e wmi CPU: 0 PID: 22492 Comm: kworker/0:6 Not tainted 4.17.14-102.fc27.x86_64 #1 Hardware name: MSI MS-7885/X99A RAIDER (MS-7885), BIOS P.00 03/20/2015 Workqueue: events nouveau_cli_work [nouveau] RIP: 0010:nvif_vmm_put+0x6a/0x80 [nouveau] RSP: 0018:ffff9b5783f5fde8 EFLAGS: 00010282 RAX: 00000000fffffffe RBX: ffff9b5783f5fe10 RCX: 0000000000000000 RDX: 0000000000000010 RSI: ffff9b5783f5fd58 RDI: ffff9b5783f5fdf8 RBP: ffff9b5783f5fe40 R08: 000000000399a000 R09: 0000000000000000 R10: ffff9b5783f5fd80 R11: 0000000000000000 R12: ffff89685683f218 R13: ffff8963a95d5700 R14: dead000000000100 R15: ffff8965c1fdc2b0 FS: 0000000000000000(0000) GS:ffff89685f200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe5bf21a000 CR3: 000000021f20a005 CR4: 00000000001606f0 Call Trace: nouveau_vma_del+0x70/0xc0 [nouveau] nouveau_gem_object_delete_work+0x2d/0x50 [nouveau] nouveau_cli_work+0xe0/0x110 [nouveau] process_one_work+0x175/0x360 worker_thread+0x2e/0x380 ? process_one_work+0x360/0x360 kthread+0x113/0x130 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 Code: 00 00 00 48 89 e2 be 02 00 00 00 48 c7 04 24 00 00 00 00 48 89 44 24 08 e8 74 eb ff ff 85 c0 75 0a 48 c7 43 08 00 00 00 00 eb b7 <0f> 0b eb f2 e8 2d c8 d5 c3 0f 1f 00 66 2e 0f 1f 84 00 00 00 00
Created attachment 1477713 [details] File: dmesg
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.