linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: poma <pomidorabelisima@gmail.com>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: 3.10.2: WARNING: at kernel/time/tick-broadcast.c:585
Date: Tue, 23 Jul 2013 03:10:30 +0200	[thread overview]
Message-ID: <51EDD806.70507@gmail.com> (raw)

Hi,

Resume from S3 generates WARNING:
…
ACPI: Low-level resume complete
PM: Restoring platform NVS memory
PCI-DMA: Resuming GART IOMMU
PCI-DMA: Restoring GART aperture settings
Enabling non-boot CPUs ...
smpboot: Booting Node 0 Processor 1 APIC 0x1
[Firmware Bug]: cpu 1, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #1
process: Switch to broadcast mode on CPU1
CPU1 is up
smpboot: Booting Node 0 Processor 2 APIC 0x2
------------[ cut here ]------------
3.10.2: WARNING: at kernel/time/tick-broadcast.c:585
tick_broadcast_oneshot_control+0x170/0x180()
Modules linked in: raid1 nouveau video mxm_wmi i2c_algo_bit
drm_kms_helper ttm drm i2c_core wmi
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.10.2-301.fc19.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. M720-US3/M720-US3, BIOS F7n
09/07/2010
 0000000000000009 ffff880129b2fd68 ffffffff81642886 ffff880129b2fda0
 ffffffff8105c211 0000000000000001 0000000000000004 ffff88012fc4dbc0
 0000000000000002 ffffffff81c21c40 ffff880129b2fdb0 ffffffff8105c2ea
Call Trace:
 [<ffffffff81642886>] dump_stack+0x19/0x1b
 [<ffffffff8105c211>] warn_slowpath_common+0x61/0x80
 [<ffffffff8105c2ea>] warn_slowpath_null+0x1a/0x20
 [<ffffffff810b34e0>] tick_broadcast_oneshot_control+0x170/0x180
 [<ffffffff810b29dd>] tick_notify+0x2fd/0x440
 [<ffffffff8164c84c>] notifier_call_chain+0x4c/0x70
 [<ffffffff81086246>] raw_notifier_call_chain+0x16/0x20
 [<ffffffff810b1f29>] clockevents_notify+0x39/0x140
 [<ffffffff81019675>] amd_e400_idle+0x75/0x100
 [<ffffffff81019e36>] arch_cpu_idle+0x26/0x30
 [<ffffffff810aa3be>] cpu_startup_entry+0xce/0x280
 [<ffffffff810b20e5>] ? clockevents_register_device+0xb5/0x120
 [<ffffffff8163794e>] start_secondary+0x24e/0x250
---[ end trace b32aec91b6f72d81 ]---
[Firmware Bug]: cpu 2, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #2
process: Switch to broadcast mode on CPU2
CPU2 is up
smpboot: Booting Node 0 Processor 3 APIC 0x3
[Firmware Bug]: cpu 3, try to use APIC500 (LVT offset 0) for vector
0x400, but the register is already in use for vector 0xf9 on another cpu
perf: IBS APIC setup failed on cpu #3
process: Switch to broadcast mode on CPU3
CPU3 is up
ACPI: Waking up from system sleep state S3
…

With an additional four patches[1] WARNING persists.

CONF.
http://kojipkgs.fedoraproject.org//packages/kernel/3.10.2/301.fc19/data/logs/x86_64/build.log


poma


[1]
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/kernel/time/tick-broadcast.c
- tick: Make oneshot broadcast robust vs. CPU offlining
- tick: Prevent uncontrolled switch to oneshot mode
- tick: Sanitize broadcast control logic
- tick: broadcast: Check broadcast mode on CPU hotplug


             reply	other threads:[~2013-07-23  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23  1:10 poma [this message]
2013-07-23  3:08 ` [Re:] 3.11-rc2: WARNING: at kernel/time/tick-broadcast.c:667 poma

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51EDD806.70507@gmail.com \
    --to=pomidorabelisima@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).