[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200711162238.29709.rjw@sisk.pl>
Date: Fri, 16 Nov 2007 22:38:29 +0100
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Andrey Borzenkov <arvidjaar@...l.ru>
Cc: Kristoffer Ericson <kristoffer.ericson@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: Suspend/Resume/Hibernation - bisecting or bug-logs?
On Friday, 16 of November 2007, Andrey Borzenkov wrote:
> 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).
If I understand the original post correctly, Kristoffer didn't mean searching
for a bad patch using bisection. :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists