Additional info: reporter: libreport-2.1.12 WARNING: CPU: 0 PID: 9 at kernel/time/tick-broadcast.c:604 tick_handle_oneshot_broadcast+0x1c0/0x1f0() Modules linked in: xt_CHECKSUM tun nf_conntrack_netbios_ns nf_conntrack_broadcast ipt_MASQUERADE bnep bluetooth ip6t_REJECT rfkill 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_hdmi snd_usb_audio snd_usbmidi_lib snd_rawmidi snd_hda_codec_realtek snd_hda_intel kvm_amd snd_hda_codec snd_hwdep snd_seq kvm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core videodev snd_seq_device snd_pcm media r8169 joydev mii snd_page_alloc snd_timer snd soundcore sp5100_tco i2c_piix4 edac_core shpchp k10temp microcode serio_raw wmi edac_mce_amd asus_atk0110 acpi_cpufreq uinput binfmt_misc ata_generic pata_acpi radeon i2c_algo_bit drm_kms_helper pata_atiixp ttm firewire_ohci drm firewire_core crc_itu_t pata_jmicron i2c_core usb_storage CPU: 0 PID: 9 Comm: migration/0 Not tainted 3.13.5-101.fc19.x86_64 #1 Hardware name: System manufacturer System Product Name/M4A89TD PRO USB3, BIOS 3029 09/07/2012 0000000000000009 ffff880237c03d10 ffffffff81680664 0000000000000000 ffff880237c03d48 ffffffff8106d35d 7fffffffffffffff 00000d5afbc65b9e 000000000000eea0 0000000000000000 ffffffff81c24700 ffff880237c03d58 Call Trace: <IRQ> [<ffffffff81680664>] dump_stack+0x45/0x56 [<ffffffff8106d35d>] warn_slowpath_common+0x7d/0xa0 [<ffffffff8106d43a>] warn_slowpath_null+0x1a/0x20 [<ffffffff810d3c60>] tick_handle_oneshot_broadcast+0x1c0/0x1f0 [<ffffffff81015d15>] timer_interrupt+0x15/0x20 [<ffffffff810c0fae>] handle_irq_event_percpu+0x3e/0x1d0 [<ffffffff810c1177>] handle_irq_event+0x37/0x60 [<ffffffff810c3b1f>] handle_edge_irq+0x6f/0x120 [<ffffffff8101560f>] handle_irq+0xbf/0x150 [<ffffffff810727d7>] ? irq_enter+0x47/0x80 [<ffffffff8169184d>] do_IRQ+0x4d/0xc0 [<ffffffff8168752d>] common_interrupt+0x6d/0x6d [<ffffffff810723d0>] ? __do_softirq+0x90/0x280 [<ffffffff810f3f30>] ? cpu_stop_should_run+0x50/0x50 [<ffffffff810728cd>] irq_exit+0xbd/0xd0 [<ffffffff81691905>] smp_apic_timer_interrupt+0x45/0x60 [<ffffffff8169029d>] apic_timer_interrupt+0x6d/0x80 <EOI> [<ffffffff810f3fdb>] ? multi_cpu_stop+0xab/0xf0 [<ffffffff810f41a3>] cpu_stopper_thread+0x73/0x120 [<ffffffff81683bb2>] ? __schedule+0x2e2/0x740 [<ffffffff810960cf>] smpboot_thread_fn+0xff/0x1b0 [<ffffffff81095fd0>] ? SyS_setgroups+0x1a0/0x1a0 [<ffffffff8108f102>] kthread+0xd2/0xf0 [<ffffffff8108f030>] ? insert_kthread_work+0x40/0x40 [<ffffffff8168f57c>] ret_from_fork+0x7c/0xb0 [<ffffffff8108f030>] ? insert_kthread_work+0x40/0x40
Created attachment 872345 [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 19 kernel bugs. Fedora 19 has now been rebased to 3.13.5-100.fc19. Please test this kernel update 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.
Got the same error today with 3.13.7-100.fc19.x86_64
*********** 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 19 kernel bugs. Fedora 19 has now been rebased to 3.14.4-100.fc19. 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 20, and are still experiencing this issue, please change the version to Fedora 20. 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 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.