public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Steven Rostedt <srostedt@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-pm@lists.linux-foundation.org
Subject: Re: resume from s2ram regression (bisected to ftrace...)
Date: Sun, 10 Aug 2008 21:24:49 +0200	[thread overview]
Message-ID: <20080810192444.GA5296@joi> (raw)
In-Reply-To: <200808101940.13753.rjw@sisk.pl>

On Sun, Aug 10, 2008 at 07:40:12PM +0200, Rafael J. Wysocki wrote:
> On Sunday, 10 of August 2008, Marcin Slusarz wrote:
> > Hi
> > 
> > Few days ago I discovered that resume from suspend to ram does not work anymore
> > on my 2.6.27-rc2 (actually 796aadeb1b2db9b5d463946766c5bbfd7717158c) gentoo box.
> > My computer just boots on resume. Today I had enough time to bisect it and found
> > (after 1 panic and 1 build breakage) out "the reason":
> > 
> > $ git bisect good
> > d05cdb25d80f06f77aa6bddb53cd1390d4d91a0b is first bad commit
> > commit d05cdb25d80f06f77aa6bddb53cd1390d4d91a0b
> > Author: Steven Rostedt <rostedt@goodmis.org>
> > Date:   Mon May 12 21:20:54 2008 +0200
> > 
> >     ftrace: fix dynamic ftrace selftest
> 
> Does it still happen if:
> - CONFIG_FTRACE is unset

no

> - CONFIG_FTRACE is set, but CONFIG_FTRACE_STARTUP_TEST is unset?

yes

Marcin

  reply	other threads:[~2008-08-10 19:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-10 17:08 resume from s2ram regression (bisected to ftrace...) Marcin Slusarz
2008-08-10 17:40 ` Rafael J. Wysocki
2008-08-10 19:24   ` Marcin Slusarz [this message]
2008-08-10 19:48     ` Rafael J. Wysocki
2008-08-11 18:27       ` Steven Rostedt
2008-08-12 16:37         ` Marcin Slusarz

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=20080810192444.GA5296@joi \
    --to=marcin.slusarz@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=srostedt@redhat.com \
    --cc=tglx@linutronix.de \
    /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