Description of problem: Reboot after several updates (kernel + progs) Additional info: reporter: libreport-2.2.3 general protection fault: 0000 [#1] SMP Modules linked in: rfcomm xt_multiport nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_nat_proto_gre nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ip6t_ipv6header ipt_MASQUERADE ip6t_rpfilter ip6t_REJECT cfg80211 xt_conntrack ebtable_nat ebtable_broute bridge stp llc 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 btrfs raid6_pq xor snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_controller snd_hda_codec iTCO_wdt btusb iTCO_vendor_support snd_hwdep bluetooth mxm_wmi eeepc_wmi asus_wmi sparse_keymap video x86_pkg_temp_thermal shpchp rfkill coretemp snd_seq snd_seq_device snd_pcm serio_raw kvm i2c_i801 wmi crct10dif_pclmul crc32_pclmul crc32c_intel snd_timer snd soundcore lpc_ich mei_me mei mfd_core ghash_clmulni_intel microcode nfsd auth_rpcgss nfs_acl lockd sunrpc radeon i2c_algo_bit drm_kms_helper r8169 ttm mii firewire_ohci drm e1000e firewire_core crc_itu_t ptp i2c_core pps_core CPU: 2 PID: 12272 Comm: QProcessManager Not tainted 3.15.10-200.fc20.x86_64 #1 Hardware name: System manufacturer System Product Name/P8P67 DELUXE, BIOS 1502 03/02/2011 task: ffff880428f189e0 ti: ffff8803d9790000 task.ti: ffff8803d9790000 RIP: 0010:[<ffffffff811013d6>] [<ffffffff811013d6>] module_put+0x16/0x70 RSP: 0018:ffff8803d9793ca0 EFLAGS: 00010286 RAX: ffffffff81c7d981 RBX: ffff88037682cc00 RCX: ffff88038eed5100 RDX: 0000000000000001 RSI: ffff8803945c7200 RDI: a000000000000000 RBP: ffff8803d9793cb8 R08: ffff8803944ed0b8 R09: 0000000180160014 R10: ffffffff811a4103 R11: ffffea000e513b40 R12: a000000000000000 R13: ffff88037682cc60 R14: ffff880398027480 R15: ffff880428f189e0 FS: 00007f5eed7be700(0000) GS:ffff88043f480000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f3edc002bb6 CR3: 0000000001c11000 CR4: 00000000000407e0 Stack: ffff88037682cc00 ffff88037682cc80 ffff88037682cc60 ffff8803d9793cd8 ffffffff810863f7 ffff880428f190b0 ffff88037682cc00 ffff8803d9793d68 ffffffff8108b8b0 0000000000100100 dead000000200200 ffff8803b55c86e8 Call Trace: [<ffffffff810863f7>] mmput+0xa7/0xf0 [<ffffffff8108b8b0>] do_exit+0x280/0xa30 [<ffffffff810bca62>] ? default_wake_function+0x12/0x20 [<ffffffff811fa773>] ? pollwake+0x73/0x90 [<ffffffff8108c0df>] do_group_exit+0x3f/0xa0 [<ffffffff8109b2fb>] get_signal_to_deliver+0x1cb/0x5c0 [<ffffffff81013417>] do_signal+0x57/0x630 [<ffffffff810c14f8>] ? __enqueue_entity+0x78/0x80 [<ffffffff810c754b>] ? put_prev_entity+0x5b/0x3b0 [<ffffffff810c3c59>] ? pick_next_entity+0xa9/0x190 [<ffffffff810ca6f3>] ? pick_next_task_fair+0x5f3/0x810 [<ffffffff810125e9>] ? __switch_to+0x169/0x4c0 [<ffffffff81013a60>] do_notify_resume+0x70/0xa0 [<ffffffff816ffda2>] int_signal+0x12/0x17 Code: 83 c4 38 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 0f 1f 44 00 00 66 66 66 66 90 55 48 85 ff 48 89 e5 41 55 41 54 49 89 fc 53 74 15 <48> 8b 87 58 02 00 00 65 48 ff 40 08 4c 8b 6d 08 66 66 66 66 90 RIP [<ffffffff811013d6>] module_put+0x16/0x70 RSP <ffff8803d9793ca0>
Created attachment 931863 [details] File: dmesg
*********** MASS BUG UPDATE ************** 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 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. 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 21, and are still experiencing this issue, please change the version to Fedora 21. 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 over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.