mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Kristoffer Ericson <kristoffer.ericson@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Suspend/Resume/Hibernation - bisecting or bug-logs?
Date: Fri, 16 Nov 2007 21:00:02 +0300	[thread overview]
Message-ID: <20071116180006.0029C87EE9C@smtp06.mtu.ru> (raw)
In-Reply-To: <20071116161420.e2c57ff6.Kristoffer.Ericson@Gmail.com>

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?
> 

Good question. I could use advice too :)

Bisecting is good only if you have known good and known bad versions. From
your description it sounds like it has never worked - so bisecting won't
help. Also sometimes bisecting hits way too large commit (this happened to
me when ACPI replaced mutex with spinlock).


  reply	other threads:[~2007-11-16 18:00 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 [this message]
2007-11-16 21:38   ` Rafael J. Wysocki
2007-11-16 21:51 ` Rafael J. Wysocki
2007-11-21 17:26 ` Pavel Machek

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=20071116180006.0029C87EE9C@smtp06.mtu.ru \
    --to=arvidjaar@mail.ru \
    --cc=kristoffer.ericson@gmail.com \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®