Bug 1375548

Summary: [abrt] WARNING: CPU: 0 PID: 11 at kernel/time/tick-broadcast.c:642 tick_handle_oneshot_broadcast+0x1e8/0x200
Product: [Fedora] Fedora Reporter: Oliver Henshaw <oliver.henshaw>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/fdee969334568be94a14e80fe8d49e5387b20a12
Whiteboard: abrt_hash:4b8866233f78d57f9f3b1becbc922f4531e5eb5a;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 21:32:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: dmesg none

Description Oliver Henshaw 2016-09-13 11:13:13 UTC
Description of problem:
Oops during suspend (while stopping CPUs?).

Additional info:
reporter:       libreport-2.6.4
WARNING: CPU: 0 PID: 11 at kernel/time/tick-broadcast.c:642 tick_handle_oneshot_broadcast+0x1e8/0x200
Modules linked in: vfat fat uas usb_storage fuse rfcomm ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_mangle ip6table_security ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_raw iptable_mangle iptable_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables bnep it87 hwmon_vid ppdev btusb btrtl btbcm btintel bluetooth kvm_amd kvm irqbypass rfkill snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel snd_hda_codec k10temp snd_hda_core snd_hwdep snd_seq snd_seq_device snd_pcm parport_pc parport sp5100_tco i2c_piix4 snd_timer snd soundcore wmi shpchp acpi_cpufreq tpm_tis tpm binfmt_misc
 ata_generic pata_acpi amdkfd amd_iommu_v2 radeon serio_raw firewire_ohci pata_jmicron i2c_algo_bit firewire_core drm_kms_helper crc_itu_t ttm drm r8169 mii fjes
CPU: 0 PID: 11 Comm: migration/0 Not tainted 4.7.2-101.fc23.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. GA-890GPA-UD3H/GA-890GPA-UD3H, BIOS FF 11/24/2010
 0000000000000086 00000000990f1faf ffff88040fc03cd0 ffffffff813d5b5e
 0000000000000000 0000000000000000 ffff88040fc03d10 ffffffff8109fa2b
 000002820fc03cf0 7fffffffffffffff 0000000000011560 0000cb2d06fcf204
Call Trace:
 <IRQ>  [<ffffffff813d5b5e>] dump_stack+0x63/0x85
 [<ffffffff8109fa2b>] __warn+0xcb/0xf0
 [<ffffffff8109fb5d>] warn_slowpath_null+0x1d/0x20
 [<ffffffff8111caf8>] tick_handle_oneshot_broadcast+0x1e8/0x200
 [<ffffffff81029385>] timer_interrupt+0x15/0x20
 [<ffffffff810fae8f>] handle_irq_event_percpu+0x7f/0x1c0
 [<ffffffff810faffc>] handle_irq_event+0x2c/0x50
 [<ffffffff810fe60f>] handle_edge_irq+0x6f/0x130
 [<ffffffff81028c93>] handle_irq+0x73/0x120
 [<ffffffff8119172c>] ? irq_work_run+0x2c/0x40
 [<ffffffff81123833>] ? flush_smp_call_function_queue+0xe3/0x150
 [<ffffffff817e6d4b>] do_IRQ+0x4b/0xd0
 [<ffffffff817e4c0c>] common_interrupt+0x8c/0x8c
 [<ffffffff817e6f7b>] ? __do_softirq+0x7b/0x2c2
 [<ffffffff810a5665>] irq_exit+0x105/0x110
 [<ffffffff817e6e12>] smp_apic_timer_interrupt+0x42/0x50
 [<ffffffff817e4f5c>] apic_timer_interrupt+0x8c/0xa0
 <EOI>  [<ffffffff81140628>] ? multi_cpu_stop+0x78/0xe0
 [<ffffffff811405b0>] ? cpu_stop_queue_work+0x90/0x90
 [<ffffffff811407f5>] cpu_stopper_thread+0x85/0x100
 [<ffffffff810c2675>] smpboot_thread_fn+0x105/0x160
 [<ffffffff810c2570>] ? sort_range+0x30/0x30
 [<ffffffff810bf2a8>] kthread+0xd8/0xf0
 [<ffffffff817e44bf>] ret_from_fork+0x1f/0x40
 [<ffffffff810bf1d0>] ? kthread_worker_fn+0x170/0x170

Comment 1 Oliver Henshaw 2016-09-13 11:13:24 UTC
Created attachment 1200470 [details]
File: dmesg

Comment 2 Fedora End Of Life 2016-11-25 09:34:52 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2016-12-20 21:32:41 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.