mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>
Cc: rjw@sisk.pl, linux-main <linux-kernel@vger.kernel.org>
Subject: Re: Suspend/Resume/Hibernation - bisecting or bug-logs?
Date: Wed, 21 Nov 2007 17:26:47 +0000	[thread overview]
Message-ID: <20071121172646.GA3888@ucw.cz> (raw)
In-Reply-To: <20071116161420.e2c57ff6.Kristoffer.Ericson@Gmail.com>

On Fri 2007-11-16 16:14:20, Kristoffer Ericson wrote:
> Greetings,
> 
> Ive been following your discussion and documentation efforts concerning pm in the kernel. This has in the past been a gray area which was hard to find information about so kudos.
> 
> I maintain 2 handheld platforms that would benefit greatly from implementing proper pm (mainly suspend) but Im having problems bugtracking it. Currently the system tries to suspend but fails somewhere and then tries to resume (which fails). The end result however is that Im unable to see anything (bugmessages...) since the video driver gets deactivated by pm.
> 
> My question is this: Is bisecting (turning off device support in kernel until it works) the best approach when bugtracking pm suspend? Or is there any other logging system that I can use?

Bisecting is not bad. Or you can port store-progress-into-rtc hacks
from pc...

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2007-11-25 17:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-17  0:14 Kristoffer Ericson
2007-11-16 18:00 ` Andrey Borzenkov
2007-11-16 21:38   ` Rafael J. Wysocki
2007-11-16 21:51 ` Rafael J. Wysocki
2007-11-21 17:26 ` Pavel Machek [this message]

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=20071121172646.GA3888@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®