Re: Linux 2.6.28-rc7

From: Alejandro Riveira FernÃndez
Date: Tue Dec 02 2008 - 14:45:32 EST

El Tue, 2 Dec 2008 11:23:42 -0800 (PST)
Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> escribiÃ:

> On Tue, 2 Dec 2008, Alejandro Riveira FernÃndez wrote:
> >
> > Here you go
> >
> > [alex@varda:kernel/linux-2.6]$ git bisect bad
> > 31168481c32c8a485e1003af9433124dede57f8d is first bad commit
> Excellent. One last step - can you verify that just reverting this commit
> makes your problems go away?
> IOW, just do
> git bisect reset
> to get out of bisect mode, and then do
> git revert 31168481c32c8a485e1003af9433124dede57f8d

Well i already sent the result of the revert on another mail;
it did not help :(

I tried again with what i thought was my "good" commit and the
bug is there too :/

could it be that something changed in userspace[1] between the
day i installed the 2.6.28-rc6-00007-ged31348 and today that
make this bug trigger? i dunno

Next step is try to find an "actually good" kernel and bisect
again sigh... seems to work ok

> and check that the end result is all good?
> That's just to double-check that the revert is sufficient, but also
> because "git bisect" is very sensitive to false information (ie if it
> happens that a bug sometimes is not entirely repeatable, then a single
> wrong "git bisect bad/good" will result in the pinpointed commit being
> possibly totally the wrong one).
> And Al - can you double-check that commit?
> Linus

[1] distro updates

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at