Backtrace: WARNING: CPU: 0 PID: 1656 at drivers/gpu/drm/i915/intel_display.c:1332 assert_plane.constprop.88+0x74/0xb0 [i915]() plane A assertion failure (expected on, current off) Modules linked in: uas usb_storage rfcomm fuse cmac xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun nf_conntrack_netbios_ns nf_conntrack_broadcast ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ebtable_nat ebtable_broute bridge ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw bnep dm_crypt arc4 iwlmvm mac80211 intel_rapl iosf_mbi x86_pkg_temp_thermal coretemp kvm_intel kvm iwlwifi iTCO_wdt iTCO_vendor_support crct10dif_pclmul crc32_pclmul crc32c_intel snd_soc_rt5640 uvcvideo ghash_clmulni_intel snd_soc_rl6231 btusb btbcm snd_hda_codec_realtek btintel cfg80211 snd_soc_core snd_hda_codec_generic snd_hda_codec_hdmi vfat videobuf2_vmalloc snd_usb_audio videobuf2_core bluetooth fat videobuf2_memops v4l2_common snd_hda_intel serio_raw videodev snd_hda_controller snd_hda_codec i2c_i801 lpc_ich mfd_core snd_usbmidi_lib snd_hda_core snd_rawmidi media snd_compress snd_hwdep snd_pcm_dmaengine snd_seq mei_me snd_seq_device mei shpchp tpm_tis snd_pcm rfkill tpm snd_timer dw_dmac dw_dmac_core snd_soc_sst_acpi snd i2c_hid regmap_i2c acpi_pad i2c_designware_platform soundcore i2c_designware_core nfsd auth_rpcgss nfs_acl lockd grace sunrpc 8021q garp stp llc mrp i915 i2c_algo_bit drm_kms_helper drm e1000e ptp pps_core sdhci_acpi sdhci mmc_core video CPU: 0 PID: 1656 Comm: Xorg Not tainted 4.1.0-1mst.fc22.x86_64 #1 Hardware name: /NUC5i5RYB, BIOS RYBDWi35.86A.0249.2015.0529.1640 05/29/2015 0000000000000000 0000000010d0af70 ffff8800d8c3b5f8 ffffffff8179a95d 0000000000000000 ffff8800d8c3b650 ffff8800d8c3b638 ffffffff810a163a 0000000100000000 0000000000000000 ffff88003f840000 ffff88003fd2d800 Call Trace: [<ffffffff8179a95d>] dump_stack+0x45/0x57 [<ffffffff810a163a>] warn_slowpath_common+0x8a/0xc0 [<ffffffff810a16c5>] warn_slowpath_fmt+0x55/0x70 [<ffffffffa01a06c4>] assert_plane.constprop.88+0x74/0xb0 [i915] [<ffffffffa01a8bd3>] hsw_disable_ips+0x43/0x1a0 [i915] [<ffffffffa01a8fb1>] intel_crtc_disable_planes+0x41/0x170 [i915] [<ffffffffa01a9da7>] haswell_crtc_disable+0x47/0x3c0 [i915] [<ffffffffa01aae9a>] __intel_set_mode+0xbaa/0xce0 [i915] [<ffffffffa01d4d1c>] ? intel_dp_mst_compute_config+0x17c/0x1c0 [i915] [<ffffffffa00cb44e>] ? drm_atomic_get_crtc_state+0x1e/0xc0 [drm] [<ffffffffa01b25ff>] intel_crtc_set_config+0xd3f/0x1080 [i915] [<ffffffffa00cb3fc>] ? drm_atomic_state_free+0x2c/0x60 [drm] [<ffffffffa00bb526>] drm_mode_set_config_internal+0x66/0x100 [drm] [<ffffffffa011fe58>] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [<ffffffffa0121eb9>] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper] [<ffffffffa0121f32>] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper] [<ffffffffa01c182a>] intel_fbdev_set_par+0x1a/0x60 [i915] [<ffffffff81429df6>] fb_set_var+0x236/0x480 [<ffffffff8120b3df>] ? __slab_free+0xbf/0x260 [<ffffffff81241c4c>] ? do_sys_poll+0x14c/0x600 [<ffffffff8141f8cc>] fbcon_blank+0x34c/0x390 [<ffffffff814a7c2a>] do_unblank_screen+0xda/0x1d0 [<ffffffff8149c96b>] vt_ioctl+0x56b/0x1420 [<ffffffff81336ae7>] ? avc_alloc_node+0x27/0x130 [<ffffffff8148f4c1>] tty_ioctl+0x3f1/0xc30 [<ffffffff813372d8>] ? avc_has_perm+0x128/0x1a0 [<ffffffff8123fc66>] do_vfs_ioctl+0x2c6/0x4d0 [<ffffffff8123fef1>] SyS_ioctl+0x81/0xa0 [<ffffffff81068eff>] ? do_page_fault+0x2f/0x80 [<ffffffff817a0f2e>] system_call_fastpath+0x12/0x71
Please try with current drm-intel-nightly from [1] and attach dmesg with drm.debug=14 module parameter if the problem persists. [1] http://cgit.freedesktop.org/drm-intel
I guess it's fixed.
I believe this was a duplicate of https://bugs.freedesktop.org/show_bug.cgi?id=85583
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.