From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from www.tglx.de (www.tglx.de [62.245.132.106]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id CBDBADDD1C for ; Mon, 9 Feb 2009 23:09:39 +1100 (EST) Date: Mon, 9 Feb 2009 13:03:53 +0100 (CET) From: Thomas Gleixner To: "Rafael J. Wysocki" Subject: Re: Badness at kernel/time/timekeeping.c:98 in pmud (timekeeping_suspended) In-Reply-To: <200902081439.31548.rjw@sisk.pl> Message-ID: References: <87prihcepl.fsf@burly.wgtn.ondioline.org> <87k58nda87.fsf@burly.wgtn.ondioline.org> <874oz5pmvd.fsf@burly.wgtn.ondioline.org> <200902081439.31548.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: linuxppc-dev@ozlabs.org, Ingo Molnar , Paul Collins , linux-kernel@vger.kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Sun, 8 Feb 2009, Rafael J. Wysocki wrote: > On Sunday 08 February 2009, Paul Collins wrote: > > Paul Collins writes: > > > > > "Rafael J. Wysocki" writes: > > > > > >> On Wednesday 21 January 2009, Paul Collins wrote: > > >>> Got a couple of these on a PowerBook running 2.6.29-rc2 either during > > >>> suspend or resume -- it's hard to tell. (The suspend message is > > >>> timestamped in syslog with the time I resumed, so I guess it was > > >>> buffered along with the subsequent "Badness" messages.) > > >> > > >> Please check if the patch from http://lkml.org/lkml/2009/1/13/144 fixes the > > >> problem for you. > > > > > > It does not fix the problem. > > > > I'm also getting this warning since 2.6.28.1, which incorporated commit > > 1c5745aa380efb6417b5681104b007c8612fb496 ("sched_clock: prevent > > scd->clock from moving backwards, take #2") as commit > > e268dcdd404f4558cdd24c8ecede3e064df8fa33, this being the patch that > > introduced the WARN_ON(timekeeping_suspended) check. > > Hm, I thought the timekeeping suspend problem was fixed in this commit. Ingo? The commit fixed the problem with sched_clock, but it does not fix problems where other parts of the kernel call timekeeping functions _AFTER_ timekeeping has been suspended. Thanks, tglx