public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Len Brown <lenb@kernel.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: s2r badness
Date: Tue, 21 Jul 2009 01:02:31 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0907210101110.2813@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.2.00.0907201700010.14242@gandalf.stny.rr.com>

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

  reply	other threads:[~2009-07-20 23:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18 20:03 s2r badness Peter Zijlstra
2009-07-18 20:33 ` Thomas Gleixner
2009-07-20 18:20   ` K.Prasad
2009-07-20 18:50     ` Peter Zijlstra
2009-07-20 21:00   ` Steven Rostedt
2009-07-20 23:02     ` Thomas Gleixner [this message]
2009-07-20 23:51       ` Steven Rostedt
2009-07-21  6:38         ` Thomas Gleixner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.00.0907210101110.2813@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=gregkh@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rjw@sisk.pl \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox