Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753805Ab3JQJjA (ORCPT ); Thu, 17 Oct 2013 05:39:00 -0400 Received: from mo-p00-ob.rzone.de ([81.169.146.160]:46459 "EHLO mo-p00-ob.rzone.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752847Ab3JQJi6 (ORCPT ); Thu, 17 Oct 2013 05:38:58 -0400 X-RZG-AUTH: :P2EQZWCpfu+qG7CngxMFH1J+yackYocTD1iAi8x+OWtqVVmrDIxjkrnugnnwVg== X-RZG-CLASS-ID: mo00 Date: Thu, 17 Oct 2013 11:38:54 +0200 From: Olaf Hering To: Thomas Gleixner Cc: poma , linux-pm@vger.kernel.org, Ingo Molnar , Linux Kernel list Subject: Re: WARNING: CPU: 1 PID: 0 at kernel/time/tick-broadcast.c:667 Message-ID: <20131017093854.GA19052@aepfle.de> References: <52157D88.3070701@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <52157D88.3070701@gmail.com> User-Agent: Mutt/1.5.21.rev5641 (2013-02-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 699 Lines: 21 > 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/