Additional info: reporter: libreport-2.2.1 BUG: soft lockup - CPU#0 stuck for 22s! [gnome-shell:1681] Modules linked in: fuse ipt_MASQUERADE xt_CHECKSUM tun ip6t_rpfilter ccm bnep bluetooth ip6t_REJECT 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 snd_hda_codec_conexant snd_hda_codec_hdmi snd_hda_intel snd_hda_codec snd_hwdep amd_freq_sensitivity snd_seq arc4 snd_seq_device snd_pcm snd_page_alloc kvm rtl8188ee snd_timer rtl_pci toshiba_acpi crct10dif_pclmul rtlwifi mac80211 crc32_pclmul snd crc32c_intel cfg80211 soundcore sparse_keymap ghash_clmulni_intel microcode shpchp edac_core joydev rfkill i2c_piix4 serio_raw edac_mce_amd fam15h_power k10temp wmi acpi_cpufreq video binfmt_misc radeon i2c_algo_bit drm_kms_helper ttm alx drm mdio i2c_core irq event stamp: 2817479 hardirqs last enabled at (2817478): [<ffffffff817730c6>] _raw_spin_unlock_irqrestore+0x36/0x70 hardirqs last disabled at (2817479): [<ffffffff8177dd6d>] apic_timer_interrupt+0x6d/0x80 softirqs last enabled at (1452374): [<ffffffff8107f178>] __do_softirq+0x198/0x430 softirqs last disabled at (1452395): [<ffffffff8107f7fd>] irq_exit+0xcd/0xe0 CPU: 0 PID: 1681 Comm: gnome-shell Not tainted 3.13.9-200.fc20.x86_64+debug #1 Hardware name: TOSHIBA Satellite L75D-A/Larne, BIOS 1.40 09/12/2013 task: ffff8800a52acbe0 ti: ffff88016bede000 task.ti: ffff88016bede000 RIP: 0010:[<ffffffff817730cb>] [<ffffffff817730cb>] _raw_spin_unlock_irqrestore+0x3b/0x70 RSP: 0018:ffff880198603918 EFLAGS: 00000282 RAX: ffff8800a52acbe0 RBX: ffff8800a52acbe0 RCX: 0000000000000000 RDX: 0000000000000190 RSI: ffff8800a52ad578 RDI: 0000000000000282 RBP: ffff880198603928 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000000 R12: ffff880198603888 R13: ffffffff8177dd72 R14: ffff880198603928 R15: 0000000000000282 FS: 00007f70e97bf700(0000) GS:ffff880198600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000032b5906a90 CR3: 0000000094a24000 CR4: 00000000000407f0 Stack: ffff8800902e7180 ffffea000240b900 ffff8801986039c8 ffffffff81767b65 ffff880198603958 0000000000000292 ffff8800902e7240 ffff8800902e7180 0000000000000282 ffffffff813a3d1e 0000000300000002 ffff8800a52acbe0 Call Trace:
Created attachment 884419 [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.14.4-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 experience different issues, please open a new bug report for those.
not sure. they only happen intermitantly. saw a few cpu stuck errors last week but cant figure out where and the newest one i find in logs were from last month. started using kernel-3.14.4-200.fc20.x86_64 about 2014-05-16 so those from last week might have been either before/after kernel-3.14.4-200.fc20.x86_64 was installed. could probably close this one for insufficient_information/works_for_me and i can reopen when/if find it in the logs again.
*********** 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.