| View previous topic :: View next topic |
| Author |
Message |
pa4wdh
l33t
Joined: 16 Dec 2005
Posts: 920
|
 Posted: Sun Mar 27, 2022 3:03 pm Post subject: unregister_netdevice: waiting for lo to become free |
 |
|
Hi All,
On my server i'm using lxc to start/stop some containers. One of them is tor and it's needless to say that one makes heavy use of networking  . Whenever i stop the tor container i see this message in dmesg:
| Code: |
[616006.832674] unregister_netdevice: waiting for lo to become free. Usage count = 2
|
This message repeats every 10 seconds.
I've done some searching but only found some references from years ago with kernel bugs that are already solved for years.
Does anyone have any idea what i can do to get rid of this? The only way i know now to get rid of the message is to reboot ...
I did find CONFIG_PCPU_DEV_REFCNT in the kernel config which seems related, but it's set to y now and doesn't help.
_________________
The gentoo way of bringing peace to the world:
USE="-war" emerge --newuse @world
My shared code repository: https://code.pa4wdh.nl.eu.org
Music, Free as in Freedom: https://www.jamendo.com |
|
| Back to top |
|
 |
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Mar 27, 2022 6:04 pm Post subject: |
|
|
Other than that does you container network work?
If yes try maybe to forcefully shut it down
| Code: |
lxc stop <bad-container> -f
|
_________________
|
|
| Back to top |
|
|
pa4wdh
l33t
Joined: 16 Dec 2005
Posts: 920
|
| Posted: Sun Mar 27, 2022 6:31 pm Post subject: |
|
|
The container works perfectly (it sends/receives a lot of data), it also shuts down cleanly (except for the dmesg message) and can also be started again after that.
Which version of lxc are you using? I'm using app-containers/lxc-4.0.11_p1-r1, the lxc-start command (notice the - between lxc and start) doesn't have the -f option.
_________________
The gentoo way of bringing peace to the world:
USE="-war" emerge --newuse @world
My shared code repository: https://code.pa4wdh.nl.eu.org
Music, Free as in Freedom: https://www.jamendo.com |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3961
|
| Posted: Sun Mar 27, 2022 9:23 pm Post subject: |
|
|
I am using lxd.
So the different syntax.
It seems this is a kernel problem.Try using another kernel.
What would happen if you issued
| Code: |
rc-service net.lo restart
|
?
_________________
|
|
| Back to top |
|
|
pa4wdh
l33t
Joined: 16 Dec 2005
Posts: 920
|
| Posted: Mon Mar 28, 2022 5:29 am Post subject: |
|
|
I agree it looks like a kernel bug.
As said i'm seeing this problem for quite a long time now and have gone through several kernel and lxc updates but the problem remains. It's now using kernel is 5.15.26.
I'm not sure if i can restart the lo device on the host without affecting all running services.
_________________
The gentoo way of bringing peace to the world:
USE="-war" emerge --newuse @world
My shared code repository: https://code.pa4wdh.nl.eu.org
Music, Free as in Freedom: https://www.jamendo.com |
|
| Back to top |
|
|
pa4wdh
l33t
Joined: 16 Dec 2005
Posts: 920
|
| Posted: Tue Mar 29, 2022 5:33 am Post subject: |
|
|
I've just tried to bring down the lo interface and bring it up again and that doesn't help.
My impression is that the log message is about the lo interface in a container (which may not exist anymore?) and not in the host system itself.
_________________
The gentoo way of bringing peace to the world:
USE="-war" emerge --newuse @world
My shared code repository: https://code.pa4wdh.nl.eu.org
Music, Free as in Freedom: https://www.jamendo.com |
|
| Back to top |
|
|
|
Kernel & Hardware
