Re: [Bug 10797] Battery is drained after poweroff

["Rafael J. Wysocki" <rjw@sisk.pl>]

On Wednesday, 8 of October 2008, Renato S. Yamane wrote:
> Kok, Auke wrote:
> > Pavel Machek wrote:
> >> Renato S. Yamane wrote:
> >>> Pavel Machek wrote:
> >>> Renato S. Yamane wrote:
> >>>>> Can someone help us with this bug?
> >>>>> <http://bugzilla.kernel.org/show_bug.cgi?id=10797>
> >>>>>
> >>>>> Same problem is reported in Ubuntu:
> >>>>> <https://bugs.launchpad.net/ubuntu/+source/linux/+bug/110784>
> >>>>>
> >>>>> This is not a hardware problem, because if the same laptop is poweroff
> >>>>> by Windows, battery charge don't change.
> >>>>
> >>>> ...and it is not linux problem because it works okay on my thinkpad. See?
> >>>
> >>> Yes, this is a Linux problem (at least in release >= 2.6.22)
> >>> This happening *only* in Linux (Kernel >=2.6.22).
> >>
> >> Wow, now that's useful info.
> 
> I don´t comment this before because we already said this in bug reports
> (links above).
> 
> >> I guess you _could_ do git bisect? ;-).
> 
> So sorry, but I really don´t now how can I do this.
> I´m an user, not developer. Can you send me a "how-to" about git bisect?

Seriously, this may be the fastest way to find out where the problem is.

It follows from your reports that the problem is present in 2.6.22, although
it wasn't present in 2.6.21.  If that's correct, you can do the following:
1) Clone the Linus' -git repository (if you have a copy already, you can use it)
2) Go to the directory containing your copy of the Linus' repo and do
	# git bisect start
	# git bisect good v2.6.21
	# git bisect bad v2.6.22
3) Wait for git to select a commit to test, build the kernel and test it.
   If it works correctly, do
	# git bisect good
   Otherwise, do
	# git bisect bad
4) Repeat 3) until you end up with single commit.

[Unfortunately this procedure may not converge for you (eg. you may encounter
a kernel version that won't compile etc.), but hopefully it will.  Then, you
will know which particular commit caused the problem to appear.]

5) When you're done, do
	# git bisect reset

Thanks,
Rafael