[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d62a5110710130824w5aa663b0l7aac9df5480f21a0@mail.gmail.com>
Date: Sat, 13 Oct 2007 17:24:09 +0200
From: "Moni Shoua" <monisonlists@...il.com>
To: "Roland Dreier" <rdreier@...co.com>
Cc: "Moni Shoua" <monis@...taire.com>,
"Jay Vosburgh" <fubar@...ibm.com>, jeff@...zik.org,
"David Miller" <davem@...emloft.net>, ogerlitz@...taire.com,
netdev@...r.kernel.org, "Moni Levy" <monil@...taire.com>
Subject: Re: [PATCH] IB/ipoib: Bound the net device to the ipoib_neigh structue
I will be near my lab only tomorrow...
I will check this and let you know.
On 10/11/07, Roland Dreier <rdreier@...co.com> wrote:
> > It happens only when ib interfaces are slaves of a bonding device.
> > I thought before that the stuck is in napi_disable() but it's almost right.
> > I put prints before and after call to napi_disable and see that it is called twice.
> > I'll try to investigate in this direction.
> >
> > ib0: stopping interface
> > ib0: before napi_disable
> > ib0: after napi_disable
> > ib0: downing ib_dev
> > ib0: All sends and receives done.
> > ib0: stopping interface
> > ib0: before napi_disable
>
> Yes, two napi_disable()s in a row without a matching napi_enable()
> will deadlock. I guess the question is why the ipoib interface is
> being stopped twice.
>
> If you just take the net-2.6.24 tree (without bonding patches), does
> bonding for ethernet interfaces work OK, or is there a similar problem
> with double napi_disable()? How about bonding of ethernet after this
> batch of bonding patches?
>
> - R.
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists