Re: 2.6.29.1: unregister_netdevice problem
From: Alexander V. Lukyanov <hidden>
Date: 2009-05-15 07:20:17
Also in:
lkml
Possibly related (same subject, not in this thread)
- 2009-04-27 · Re: 2.6.29.1: unregister_netdevice problem · Alexander V. Lukyanov <hidden>
- 2009-04-24 · Re: 2.6.29.1: unregister_netdevice problem · Bruno Prémont <bonbons@linux-vserver.org>
- 2009-04-23 · Re: 2.6.29.1: unregister_netdevice problem · Eric W. Biederman <hidden>
On Sun, May 10, 2009 at 02:46:41PM +0200, Jarek Poplawski wrote:
On Sun, May 10, 2009 at 11:35:59AM +0400, Alexander V. Lukyanov wrote:quoted
On Fri, May 08, 2009 at 10:46:28AM +0000, Jarek Poplawski wrote:quoted
I can't see anything suspicious for now, except these UDP and TCP warnings. Did you see similar messages with 2.6.27? Btw., could thisYes. Such messages show up with any kernel version.quoted
eth0.987 be "connected" with any of this traffic? (IP# ?)No, eth0.987 is only used for traffic output. BTW, it seems that only actively used vlan interfaces have the problem (even when the traffic stops). Other vlan interfaces with little traffic can be removed with no problems.OK, I'll try to look around this, but how about trying 2.6.28.10 in the meantime? It could limit "a bit" the number of places/lines.
Looks like 2.6.28.10 does not have this refcnt problem. Also, after I have reversed net/ipv4/route.c changes from 2.6.29, the problem does not occur either. -- Alexander..