kernel: unregister_netdevice: waiting for vboxnet1 to ...

Discussions related to using VirtualBox on Linux hosts.
macachuto
Posts: 21
Joined: 9. Nov 2011, 20:55
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Ubuntu, windows, FreeBSD

kernel: unregister_netdevice: waiting for vboxnet1 to ...

Post by macachuto »

Recently I started to get this message when shutdown my system:
kernel:[ 2157.199178] unregister_netdevice: waiting for vboxnet1 to become free. Usage count = -2

Also in dmesg there is: [ 903.121043] dev_remove_pack: ffff8802100c10d8 not found.

I think, it started after I updated kernel, but I am not sure.
Is this kernel problem or VirtualBox?

Linux = Fedora 16, kernel 3.3.7-1.fc16.x86_64 #1 SMP Tue May 22 13:59:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Virtual Box version = 4.1.16r78094

Problem is that it is impossible to shutdown system because netdevice does not become free.

Thanks.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by Perryg »

Version of VirtualBox, and where did you get the install?
macachuto
Posts: 21
Joined: 9. Nov 2011, 20:55
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Ubuntu, windows, FreeBSD

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by macachuto »

Virtual Box version = 4.1.16r78094

It was "all linux version", which installs itself in /opt. Downloaded from virtualbox web site.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by Perryg »

Hummm,

I build these things all the time and "normally" do not see kernel errors like this. Try to run vboxdrv setup and see if that changes the way it works or even re-compile it against the new kernel and see.
macachuto
Posts: 21
Joined: 9. Nov 2011, 20:55
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Ubuntu, windows, FreeBSD

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by macachuto »

The unpleasant thing is that since I notice that message for the first time Fedora changed 2 kernel version and I updated virtualbox.

And always I did /etc/init.d/vboxdrv setup.

I even open a bug in bugzilla.redhat.com and got the answer:
"Dave Jones 2012-05-29 10:11:43 EDT

you need to report vbox problems to the vbox people, as we don't ship that code."

So I decide to report here.

Thanks.
macachuto
Posts: 21
Joined: 9. Nov 2011, 20:55
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Ubuntu, windows, FreeBSD

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by macachuto »

I can tell more:

even if I type: /etc/init.d/vboxdrv stop in root console I still get this message.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by Perryg »

Like I said I don't see this issue and don't have 16 handy to test for you (been working with 17) but the place to really report this is bugtracker so the DEVs can look into it. It would be great if you post the link here for others that may have this issue so they can add to the ticket or see the resolve.
Nightshade
Posts: 10
Joined: 29. May 2012, 23:04

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by Nightshade »

Same problem here with Virtualbox 4.1.16 and a self compiled 3.2 kernel. The issue occured
after upgrade from kernel 3.2.17 to 3.2.18. In the patch I see a change in /net/core/dev.c that might cause this (?) but I am not a programmer.
macachuto
Posts: 21
Joined: 9. Nov 2011, 20:55
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Ubuntu, windows, FreeBSD

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by macachuto »

I opened new bug: https://www.virtualbox.org/ticket/10624

Add your comments there, please.


Thanks
frank
Oracle Corporation
Posts: 3362
Joined: 7. Jun 2007, 09:11
Primary OS: Debian Sid
VBox Version: PUEL
Guest OSses: Linux, Windows
Location: Dresden, Germany
Contact:

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by frank »

Nightshade wrote:Same problem here with Virtualbox 4.1.16 and a self compiled 3.2 kernel. The issue occured
after upgrade from kernel 3.2.17 to 3.2.18. In the patch I see a change in /net/core/dev.c that might cause this (?) but I am not a programmer.
That's a valuable information. Are you really sure that this did not happen with 3.2.17 vanilla but does happen with 3.2.18?
macachuto
Posts: 21
Joined: 9. Nov 2011, 20:55
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Ubuntu, windows, FreeBSD

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by macachuto »

I would like also add, that as I said before, I start to notice that problem with previous version Virtualbox, I think it was 4.1.12, and then I updated it to 4.1.6. I do not update Virtualbox often if it works fine, but I update Fedora. That is why I thought it is because I updated kernel through normal "yum update".
I am confused and do not want to confuse others.
Nightshade
Posts: 10
Joined: 29. May 2012, 23:04

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by Nightshade »

Frank Mehnert wrote: That's a valuable information. Are you really sure that this did not happen with 3.2.17 vanilla but does happen with 3.2.18?
I just tested it to be as sure as possible.

Styx:/home/nightshade # uname -a
Linux Styx 3.2.17 [...]

/var/log/kern.log after run and shutdown Virtualbox:

May 30 18:48:50 Styx kernel: warning: `VirtualBox' uses 32-bit capabilities (legac
y support in use)
May 30 18:48:52 Styx kernel: device eth0 entered promiscuous mode
May 30 18:49:26 Styx kernel: device eth0 left promiscuous mode
May 30 18:49:27 Styx kernel: vboxnetflt: dropped 0 out of 2 packets

Testing to remove eth0 by removing kernelmodul after shutting down eth0 etc.:
Styx:/var/log/system # rmmod r8168
No Problems.

After patching the kernel with patch-3.2.17-18.gz:

Styx:/var/log/system # uname -a
Linux Styx 3.2.18 #2 [...]

/var/log/kern.log after run and shutdown Virtualbox:

May 30 19:12:36 Styx kernel: warning: `VirtualBox' uses 32-bit capabilities (legac
y support in use)
May 30 19:12:37 Styx kernel: device eth0 entered promiscuous mode
May 30 19:13:01 Styx kernel: device eth0 left promiscuous mode
May 30 19:13:02 Styx kernel: vboxnetflt: dropped 0 out of 2 packets
May 30 19:13:02 Styx kernel: dev_remove_pack: f1090084 not found.

Testing to remove eth0 by removing kernelmodul after shutting down eth0 etc.:
Styx:/var/log/system # rmmod r8168
May 30 19:15:19 Styx kernel: unregister_netdevice: waiting for eth0 to
become free. Usage count = -1
May 30 19:15:29 Styx kernel: unregister_netdevice: waiting for eth0 to
become free. Usage count = -1

This is lasting forever-only reboot is possible to get eth0 again.


At last I tried a "3.2.18" Kernel where I removed in the upgradepatch only the lines
changing /net/core/dev.c. Working for me as good as a 3.2.17 with no problems.
(Again: I am NOT a programmer. I only see results.)
wkr
Posts: 1
Joined: 5. Jun 2012, 16:53

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by wkr »

Same problem in Ubuntu 12.04 with an upgrade to 3.2.0.25 Kernel version. Fixed with the use of previous kernel version.
macachuto
Posts: 21
Joined: 9. Nov 2011, 20:55
Primary OS: Ubuntu other
VBox Version: OSE other
Guest OSses: Ubuntu, windows, FreeBSD

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by macachuto »

Interesting!
For how long we have to wait new release, which will fix this critical bug?
Critical - because it is not possible to shutdown system properly.

Thanks.
4x5n
Posts: 4
Joined: 14. Jun 2012, 17:51

Re: kernel: unregister_netdevice: waiting for vboxnet1 to ..

Post by 4x5n »

Anyone remember which release of Vbox first had this bug? I'm running it on a laptop and need to be able to reboot my laptop multiple times a day. This is causing problems for me. My plan is to back out to the version prior to this bug and not upgrade until it's fixed.
Post Reply