Additional info: reporter: libreport-2.2.3 BUG: soft lockup - CPU#3 stuck for 23s! [gmain:3080] Modules linked in: rfcomm fuse ccm ipt_MASQUERADE iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack xt_CHECKSUM iptable_mangle tun bridge stp llc ip6table_filter ip6_tables ebtable_nat ebtables iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi bnep iTCO_wdt iTCO_vendor_support hp_wmi sparse_keymap ppdev snd_hda_codec_idt snd_hda_codec_generic snd_hda_codec_hdmi nls_utf8 isofs loop x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel arc4 ghash_clmulni_intel btusb bluetooth iwldvm mac80211 microcode uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev media serio_raw iwlwifi cfg80211 sdhci_pci sdhci rfkill mmc_core snd_hda_intel snd_hda_controller snd_hda_codec wmi snd_hwdep snd_seq snd_seq_device parport_pc snd_pcm parport lpc_ich video hp_accel lis3lv02d input_polldev snd_timer snd mfd_core e1000e soundcore mei_me ptp mei pps_core shpchp binfmt_misc btrfs xor radeon raid6_pq i2c_algo_bit drm_kms_helper ttm drm firewire_ohci firewire_core i2c_core crc_itu_t CPU: 3 PID: 3080 Comm: gmain Not tainted 3.15.8-200.fc20.x86_64 #1 Hardware name: Hewlett-Packard HP EliteBook 8560w (LG660EA)/1631, BIOS 68SVD Ver. F.22 01/05/2012 task: ffff8801b9564520 ti: ffff88019ae5c000 task.ti: ffff88019ae5c000 RIP: 0010:[<ffffffff816f6762>] [<ffffffff816f6762>] _raw_spin_lock+0x12/0x40 RSP: 0018:ffff88019ae5fba0 EFLAGS: 00000282 RAX: 000000009ce59ce5 RBX: ffffffff8122a6a6 RCX: 0000000180220005 RDX: ffff880204f90ca8 RSI: ffff8802311c1a00 RDI: ffff880204f90cc8 RBP: ffff88019ae5fba0 R08: ffff880204f90690 R09: 0000000180220005 R10: ffffffff8122aed8 R11: ffffea000813e400 R12: 0000000000008000 R13: ffffffff8122afef R14: ffff88019ae5fb58 R15: ffff880204f90690 FS: 00007fd86bfff700(0000) GS:ffff88023dcc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000033e82177d4 CR3: 0000000001c11000 CR4: 00000000000407e0 Stack: ffff88019ae5fbd0 ffffffff8122917b ffff880204f90ca8 ffff880204f90ca8 ffff8802311c1a00 00000000ffffffff ffff88019ae5fc10 ffffffff812295cf ffff8802311c1a70 ffff8802311c1a00 0000000000000010 ffff8802314ed6d0 Call Trace: [<ffffffff8122917b>] fsnotify_destroy_mark_locked+0x2b/0x150 [<ffffffff812295cf>] fsnotify_clear_marks_by_group_flags+0x7f/0xb0 [<ffffffff81229613>] fsnotify_clear_marks_by_group+0x13/0x20 [<ffffffff81228822>] fsnotify_destroy_group+0x12/0x50 [<ffffffff8122a872>] inotify_release+0x22/0x50 [<ffffffff811e83cc>] __fput+0xdc/0x1e0 [<ffffffff811e851e>] ____fput+0xe/0x10 [<ffffffff810a9314>] task_work_run+0xc4/0xe0 [<ffffffff8108b91c>] do_exit+0x2cc/0xa30 [<ffffffff811fa710>] ? poll_select_copy_remaining+0x150/0x150 [<ffffffff8108c0ff>] do_group_exit+0x3f/0xa0 [<ffffffff8109b31b>] get_signal_to_deliver+0x1cb/0x5c0 [<ffffffff810bca70>] ? wake_up_state+0x20/0x20 [<ffffffff81013417>] do_signal+0x57/0x630 [<ffffffff812281d8>] ? fsnotify+0x238/0x310 [<ffffffff81013a60>] do_notify_resume+0x70/0xa0 [<ffffffff816ffca2>] int_signal+0x12/0x17 Code: 66 66 90 f0 81 2f 00 00 10 00 74 05 e8 68 4a c6 ff 48 89 d0 5d c3 0f 1f 00 66 66 66 66 90 55 48 89 e5 b8 00 00 01 00 f0 0f c1 07 <89> c2 c1 ea 10 66 39 c2 75 02 5d c3 0f b7 07 89 d1 66 39 d0 74
Created attachment 928932 [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.
*********** MASS BUG UPDATE ************** This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 4 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.