Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754255AbZGTXEB (ORCPT ); Mon, 20 Jul 2009 19:04:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752418AbZGTXEA (ORCPT ); Mon, 20 Jul 2009 19:04:00 -0400 Received: from www.tglx.de ([62.245.132.106]:40533 "EHLO www.tglx.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751193AbZGTXD7 (ORCPT ); Mon, 20 Jul 2009 19:03:59 -0400 Date: Tue, 21 Jul 2009 01:02:31 +0200 (CEST) From: Thomas Gleixner To: Steven Rostedt cc: Peter Zijlstra , "Rafael J. Wysocki" , Len Brown , Greg Kroah-Hartman , lkml Subject: Re: s2r badness In-Reply-To: Message-ID: References: <1247947383.4872.3.camel@laptop> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 936 Lines: 25 On Mon, 20 Jul 2009, Steven Rostedt wrote: > > > > Just to make the list more complete. If tracing is enabled across > > suspend/resume you'll hit that one as well: > > > > WARNING: at /home/tglx/work/kernel/git/linux-2.6/kernel/trace/ring_buffer.c:1392 rb_reserve_next_event+0x133/0x27c() > > > > Negative timestamp delta which is probably due to sched_clock not yet > > adjusted to the TSC which got reset. > > Perhaps we need to prevent tracing during a "blackout period" of suspend > to ram? Perhaps we need to figure out why this is happening and how we best deal with it. Disabling functionality just because we can not deal with it right now is not a solution. Thanks, tglx -- 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/