From: poma <pomidorabelisima@gmail.com>
To: Olaf Hering <olaf@aepfle.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: linux-pm@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667
Date: Fri, 10 Jan 2014 04:00:57 +0100 [thread overview]
Message-ID: <52CF6269.8030105@gmail.com> (raw)
In-Reply-To: <20131017093854.GA19052@aepfle.de>
On 17.10.2013 11:38, Olaf Hering wrote:
>> Waking up from system sleep state S3:
>
>> ------------[ cut here ]------------
>> WARNING: CPU: 2 PID: 0 at kernel/time/tick-broadcast.c:667
>> tick_broadcast_oneshot_control+0x181/0x190()
>
>
> Thomas,
>
> this WARN_ON_ONCE happens on resume on my HP ProBook 6555b.
> Is it still needed to be verbose in such case? It was introduced with
> commit 26517f3e99248668315aee9460dcea21628cdd7f ("tick: Avoid
> programming the local cpu timer if broadcast pending").
3.10.2 - 3.13.0-0.rc7:
------------[ cut here ]------------
WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:668
tick_broadcast_oneshot_control+0x17d/0x190()
CPU: 1 PID: 0 Comm: swapper/1 Not tainted 3.13.0-0.rc7.git2.2.fc21.x86_64 #1
Call Trace:
[<ffffffff81680a6a>] dump_stack+0x45/0x56
[<ffffffff8106841d>] warn_slowpath_common+0x7d/0xa0
[<ffffffff810684fa>] warn_slowpath_null+0x1a/0x20
[<ffffffff810cf16d>] tick_broadcast_oneshot_control+0x17d/0x190
[<ffffffff810cdcb8>] clockevents_notify+0x178/0x1a0
[<ffffffff8101c17b>] amd_e400_idle+0x7b/0x100
[<ffffffff8101c916>] arch_cpu_idle+0x26/0x30
[<ffffffff810bb425>] cpu_startup_entry+0xc5/0x290
[<ffffffff81040bab>] start_secondary+0x22b/0x2e0
---[ end trace a6717546b328eaba ]---
poma
prev parent reply other threads:[~2014-01-10 3:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 2:55 WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667 poma
2013-10-17 9:38 ` Olaf Hering
2014-01-10 3:00 ` poma [this message]
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=52CF6269.8030105@gmail.com \
--to=pomidorabelisima@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=olaf@aepfle.de \
--cc=tglx@linutronix.de \
/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).