Description of problem: I updated to F24 Beta and my laptop now just has a black screen after the plymouth screen disappears when booting. I had to boot into an older F23 kernel to get the system usable. Additional info: reporter: libreport-2.7.0 kernel BUG at include/linux/page-flags.h:272! invalid opcode: 0000 [#1] SMP Modules linked in: ccm fuse ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_filter ebtable_nat ebtable_broute bridge stp llc ebtables ip6table_security ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_filter ip6_tables iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_raw bnep arc4 iwl3945 iwlegacy coretemp kvm_intel mac80211 kvm iTCO_wdt iTCO_vendor_support ppdev btusb irqbypass btrtl btbcm btintel bluetooth cfg80211 snd_hda_codec_analog snd_hda_codec_generic joydev snd_hda_intel i2c_i801 snd_hda_codec snd_hda_core snd_hwdep lpc_ich snd_seq snd_seq_device acpi_cpufreq snd_pcm thinkpad_acpi rfkill nsc_ircc irda parport_pc snd_timer snd parport crc_ccitt shpchp soundcore tpm_tis tpm nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_crypt i915 e1000e serio_raw i2c_algo_bit drm_kms_helper drm ata_generic pata_acpi yenta_socket ptp pps_core fjes video CPU: 1 PID: 2201 Comm: Xorg Not tainted 4.5.2-302.fc24.x86_64 #1 Hardware name: LENOVO 6369Y11/6369Y11, BIOS 7IET38WW (1.19 ) 03/22/2011 task: ffff880079210000 ti: ffff88007a6dc000 task.ti: ffff88007a6dc000 RIP: 0010:[<ffffffffa004647b>] [<ffffffffa004647b>] drm_pci_alloc+0x12b/0x1b0 [drm] RSP: 0018:ffff88007a6df998 EFLAGS: 00010246 RAX: 000000000000003c RBX: 0000000000004000 RCX: 0000000000000006 RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88007f50dfb0 RBP: ffff88007a6df9c8 R08: 0000000000000005 R09: 00000000000003b2 R10: ffffffff81a80d21 R11: ffffffff81f400cd R12: ffff880079a07fe0 R13: ffffffff81c19f20 R14: 0000000000000000 R15: ffff8800762503c0 FS: 00007f2008459a40(0000) GS:ffff88007f500000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2008527008 CR3: 000000007a63f000 CR4: 00000000000006e0 Stack: 024040c4762503c0 ffff88007c26b098 000000005a4dac53 0000000000000100 ffff880035d50d80 ffff880035d50d80 ffff88007a6df9f8 ffffffffa0154386 ffff8800762503c0 ffff880035d77800 ffff880076250300 ffff880035d50d80 Call Trace: [<ffffffffa0154386>] i915_gem_object_attach_phys+0x116/0x1c0 [i915] [<ffffffffa019bd14>] intel_prepare_plane_fb+0x1c4/0x300 [i915] [<ffffffffa00b7786>] drm_atomic_helper_prepare_planes+0x56/0xd0 [drm_kms_helper] [<ffffffffa019300c>] intel_atomic_commit+0x2ac/0x1880 [i915] [<ffffffffa005b492>] ? drm_atomic_check_only+0x182/0x600 [drm] [<ffffffffa005ac30>] ? drm_atomic_get_crtc_state+0x70/0xd0 [drm] [<ffffffffa005b94a>] drm_atomic_commit+0x3a/0x60 [drm] [<ffffffffa00b816c>] drm_atomic_helper_update_plane+0xec/0x130 [drm_kms_helper] [<ffffffffa004b076>] __setplane_internal+0x206/0x250 [drm] [<ffffffffa004b1f4>] drm_mode_cursor_universal+0x134/0x220 [drm] [<ffffffffa004b35e>] drm_mode_cursor_common+0x7e/0x180 [drm] [<ffffffffa004f5b0>] drm_mode_cursor_ioctl+0x50/0x70 [drm] [<ffffffffa0040712>] drm_ioctl+0x152/0x540 [drm] [<ffffffffa004f560>] ? drm_mode_setcrtc+0x520/0x520 [drm] [<ffffffff811eae27>] ? handle_mm_fault+0x317/0x1bd0 [<ffffffff812567b3>] do_vfs_ioctl+0xa3/0x5d0 [<ffffffff81256d59>] SyS_ioctl+0x79/0x90 [<ffffffff817d076e>] entry_SYSCALL_64_fastpath+0x12/0x6d Code: 0f 82 8d 00 00 00 4c 89 c1 48 01 cf 48 c1 ef 0c 48 c1 e7 06 48 01 f7 48 8b 0f 80 e5 40 74 0e 48 c7 c6 50 2d 07 a0 e8 65 d2 19 e1 <0f> 0b 48 8b 4f 20 83 e1 01 75 e9 f0 80 4f 01 04 48 81 c2 00 10 RIP [<ffffffffa004647b>] drm_pci_alloc+0x12b/0x1b0 [drm] RSP <ffff88007a6df998>
Created attachment 1155397 [details] File: dmesg
This problem went away after updating to kernel-4.5.5-300.fc24.x86_64