Re: Linux 2.6.28-rc7

["Alejandro Riveira Fernández" <ariveira@gmail.com>]

El Tue, 2 Dec 2008 19:49:07 +0100
Alejandro Riveira Fernández <ariveira@gmail.com> escribió:

> El Tue, 2 Dec 2008 08:13:47 -0800 (PST)
> Linus Torvalds <torvalds@linux-foundation.org> escribió:
> 
> > 
> > 
> > On Tue, 2 Dec 2008, Alejandro Riveira Fernández wrote:
> 
> [ ... ]
> > 
> > Since you are apparently a git user, and 2.6.28-rc6-00007-ged31348 was 
> > fine, there's really only 270 commits in between that and 2.6.28-rc7. Can 
> > I ask you to bisect for a couple of runs, which would cut it down to a 
> > handful? (Ie you don't even need to do a full bisect, although that should 
> > really only require about 8 reboots).
> > 
> > Just do
> > 
> > 	git bisect start
> > 	git bisect bad v2.6.27
>                        v2.6.28-rc7 <<< 
> > 	git bisect good v2.6.28-rc6-00007-ged31348
> > 
> > and off you go. That would help enormously.
> > 
> > There are very few console-related changes in that range, and the most 
> > notably one is actually radeon-specific so it shouldn't be an issue for 
> > you. I'd _suspect_ bca404afdc5206c3bb30168315ee8a98a579ec65 ("fbdev: fix 
> > FB console blanking"), but quite frankly, it could be something random 
> > that just interacted badly. A bisection would narrow things down.
> 
>  Here you go 
> 
>  [alex@varda:kernel/linux-2.6]$ git bisect bad                                   
> 31168481c32c8a485e1003af9433124dede57f8d is first bad commit
> commit 31168481c32c8a485e1003af9433124dede57f8d
> Author: Al Viro <viro@ftp.linux.org.uk>
> Date:   Sat Nov 22 17:33:24 2008 +0000
> 
[ ... ]


> 
> 
>  That's what i got after the bisection dunno if that helps...


 Well i can tell that reverting this commit did not help :(
I'm building my "good" kernel again to test it... 

> 
> 
> > 
> > 			Linus