Re: Regression in bonding between 2.6.26.8 and 2.6.27.6 - bisected

[Jesper Krogh]

Jay Vosburgh wrote:
> Jesper Krogh <jesper@xxxxxxxx> wrote:
>
> > Jay Vosburgh wrote:
> > > Jesper Krogh <jesper@xxxxxxxx> wrote:
> > > [...]
> > > > The offending commit seems to be:
> > > >
> > > > A test with a fresh 2.6.29-rc6 revealed that the problem has been fixed
> > > > subsequently.. but still exists in 2.6.27-newest.  (havent tested
> > > > 2.6.28-newest yet).
> > > >
> > > > Any ideas of what the "fixing" commit is .. or should that also be
> > > > bisected?
> > > 	I went back and looked at your earlier mail.  Since you're using
> > > 802.3ad mode, my first guess would be this commit:
> > >
> > > commit fd989c83325cb34795bc4d4aa6b13c06f90eac99
>
> 	I'll compile 2.6.28.7 here and see if it works for me.

I appreciate that you spend time on it, but my feeling is that it 
definately isn't reproducible in all environments (otherwise we would
probably have seen a large cry by now).

I'm trying to bisect the "fix" down and hope that'll tell us something 
more.

If you do the test, remember, that it is not like "bonding isn't 
working". It just fails to initialize correctly at bootup and doesnt get 
 the link state by itself. Subsequently doing a /etc/init.d/networking 
restart brigs it correct up.

--
Jesper
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/