linux-kernel - Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 10 Jan 2014 04:00:57 +0100
From:	poma <pomidorabelisima@...il.com>
To:	Olaf Hering <olaf@...fle.de>, Thomas Gleixner <tglx@...utronix.de>
CC:	linux-pm@...r.kernel.org, Ingo Molnar <mingo@...nel.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667

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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/