Messages in this thread | | | Date | Thu, 26 Aug 2004 18:46:10 +0200 | From | Jurriaan <> | Subject | Re: 2.6.8-rc4-bk1 problem: unregister_netdevice: waiting for ppp0 to become free. Usage count = 1 |
| |
From: David S. Miller <davem@redhat.com> Date: Sun, Aug 22, 2004 at 09:47:46PM -0700 > On Sun, 22 Aug 2004 14:39:57 +0200 > Patrick McHardy <kaber@trash.net> wrote: > > > Herbert Xu wrote: > > > > >Nuno Silva <nuno.silva@vgertech.com> wrote: > > > > > >OK, this appears to be due to the changeset titled > > > > > >[PKT_SCHED]: Refcount qdisc->dev for __qdisc_destroy rcu-callback > > > > > >It adds a reference to dev. > > > > > >I don't see any code that cleans up that reference when the dev goes > > >down. So someone needs to add that similar to the code in net/core/dst.c. > > > > > >Patrick, could you please have a look at this? > > > > > The reference is dropped in __qdisc_destroy. The problem lies in the CBQ > > qdisc, it doesn't destroy the root-class and leaks the inner qdisc. These > > two patches for 2.4 and 2.6 fix the problem. > > Awesome, good detective work guys. > > Patch applied, thanks.
I get the same error with 2.6.9-rc1-mm1, but now for my ipv6-over-ipv4 tunnel.
unregister_netdevice: waiting for xs6all to become free
etc. when trying to reboot or shutdown. Usage count = 1
I'm pretty sure I didn't see this in 2.6.8.1 nor in 2.6.8.1-mm1.
This is a plain ipv6-over-ipv4 tunnel like this:
/etc/network/interfaces: auto xs6all iface xs6all inet6 v4tunnel endpoint xxx.xxx.xxx.xxx up ip route add 2000::0/3 via xxx:xxx:xxx:xxx:xxx:xxx address xxx:xxx:xxx:xxx:xxx:xxx netmask 64 up ip tunnel change xs6all ttl 64
I'm running Debian Unstable with all the latest updates as of today.
Thanks for any hints, Jurriaan -- "At least she's on our side," said Lindholm. Corbie looked at him. "Investigators aren't on anybody's side." Simon R Green - Hellworld Debian (Unstable) GNU/Linux 2.6.9-rc1 2x6078 bogomips load 0.46 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |