Description of problem: problem occurring at system boot Additional info: reporter: libreport-2.1.9 WARNING: CPU: 0 PID: 0 at kernel/time/tick-broadcast.c:667 tick_broadcast_oneshot_control+0x180/0x190() Modules linked in: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.11.7-100.fc18.x86_64 #1 Hardware name: HP ProLiant MicroServer, BIOS O41 04/02/2011 0000000000000009 ffffffff81c01d98 ffffffff816665e6 00000000000000da 0000000000000000 ffffffff81c01dd8 ffffffff810695ec ffffffff81c01e08 0000000000000000 0000000000000004 ffff880077c0dc80 0000000000000002 Call Trace: [<ffffffff816665e6>] dump_stack+0x46/0x58 [<ffffffff810695ec>] warn_slowpath_common+0x8c/0xc0 [<ffffffff8106963a>] warn_slowpath_null+0x1a/0x20 [<ffffffff810c3270>] tick_broadcast_oneshot_control+0x180/0x190 [<ffffffff810c19c8>] clockevents_notify+0x188/0x1b0 [<ffffffff8101bfe5>] amd_e400_idle+0x75/0x100 [<ffffffff8101c776>] arch_cpu_idle+0x26/0x30 [<ffffffff810b9510>] cpu_startup_entry+0xd0/0x260 [<ffffffff8165c797>] rest_init+0x77/0x80 [<ffffffff81d0ef02>] start_kernel+0x40a/0x417 [<ffffffff81d0e8f7>] ? repair_env_string+0x5e/0x5e [<ffffffff81d0e5de>] x86_64_start_reservations+0x2a/0x2c [<ffffffff81d0e6e3>] x86_64_start_kernel+0x103/0x112 Potential duplicate: bug 1025045
Created attachment 827429 [details] File: dmesg
Hi Francesco, looking at the different BZ's on this, it seems a regression from a previous kernel. Can you identify the exact kernel version where this issue appeared first? If we can identify the exact commit, I'll try and bring it up upstream. Thanks, Michele
Sorry for answering so late. The bug was observed first with kernel 3.10.12-100.fc18.x86_64. After upgrade to kernel 3.11.4-101.fc18.x86_64 the issue was resolved. See Bug 996973
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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.
Thanks for the confirmation. I'll go ahead and close this then. regards, Michele