On Wed, Apr 17, 2013 at 09:24:01AM +0800, Cong Wang wrote:
> On Tue, 2013-04-16 at 13:20 +0200, Thomas Voegtle wrote:
> > Hello,
> >
> > since kernel 3.0.72 I can trigger below Oops when I execute something
> > like:
> >
> > vconfig rem bond0.13
> >
> > Problem did not exist in 3.0.71 and lowe
On Tue, 2013-04-16 at 13:20 +0200, Thomas Voegtle wrote:
> Hello,
>
> since kernel 3.0.72 I can trigger below Oops when I execute something
> like:
>
> vconfig rem bond0.13
>
> Problem did not exist in 3.0.71 and lower, and a quick check showed
> it does not exist in 3.2.43 or 3.8.7. So it see
Hello,
since kernel 3.0.72 I can trigger below Oops when I execute something
like:
vconfig rem bond0.13
Problem did not exist in 3.0.71 and lower, and a quick check showed
it does not exist in 3.2.43 or 3.8.7. So it seems to be a 3.0.x only
problem.
Reverting this commit, which is in 3.0.