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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Oct 2013 11:38:54 +0200
From:	Olaf Hering <olaf@...fle.de>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	poma <pomidorabelisima@...il.com>, 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

> 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").


Olaf
--
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/