Roland,
Recently (e.g now with 2.6.34-rc2) I came across this warning from
ipoib_start_xmit.
I wasn't sure if it suggests that there's some real problem or not. It happens
few times and then vanishes, for some reason the type is always 0002
(ETH_P_AX25)
ib0: Unicast, no dst: type 0002,
On Mon, Mar 22, 2010 at 11:55:18AM +0200, Or Gerlitz wrote:
>
> Recently (e.g now with 2.6.34-rc2) I came across this warning from
> ipoib_start_xmit.
> I wasn't sure if it suggests that there's some real problem or not. It happens
> few times and then vanishes, for some reason the type is always
> Why did we get this? It could happen since the IPoIB neighbour that
> the specific instance of IPoIB CM is pointing to might have SKBs in
> its queue. When REP arrives for this connection, it will re-queue all
> the queued SKBs again but there may be no dst for them anymore.
>
Do you mean that
On Mon, Mar 22, 2010 at 06:13:08PM +0200, Moni Shoua wrote:
>
> Do you mean that it ("no dst for them anymore.") happened due to aging of the
> neigh?
Yes, the networking stack could do that while we were wating for a
REP.
> My intuition tells me that it should be a very rare scenario, if I gues
