On 12/12/2014 07:38 PM, treaki wrote: > $ dmesg | tail > [91012.980054] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91023.096067] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91033.232076] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91043.364077] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91053.512060] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91063.636053] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91073.796085] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91083.940230] unregister_netdevice: waiting for vboxnet0 to become free. > Usage count = 1 > [91089.083913] device vboxnet0 left promiscuous mode > [91089.088161] vboxnetflt: 3 out of 284 packets were not sent (directed to > host)
This usually happens when you have reference count to the corresponding module > 0. In this case, I believe it is the vboxnet module. You should only see the message, if you have active guest VMs, and you try to do a virtualbox service restart. Are you doing anything of that sort ? If yes, why ? As for network manager, I have no clue if that can interfere. I don't use network manager. But I don't see any reason why it should. -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
