Should I worry about "Freed UMA kegs" and "lost pages?"

[RoadHazard]

I get log messages similar to this one almost every night. Is this something I should be trying to fix?

Code:

freenas.local kernel log messages:
> arp: 192.168.1.89 moved from 02:68:f6:00:0d:0a to 00:02:b3:a2:d7:dd on
> epair6b
> epair2a: link state changed to DOWN
> epair2b: link state changed to DOWN
> epair2a: Ethernet address: 02:d2:35:00:09:0a
> epair2b: Ethernet address: 02:d2:35:00:11:0b
> epair2a: link state changed to UP
> epair2b: link state changed to UP
> epair2a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair2b
> ifa_del_loopback_route: deletion failed Freed UMA keg (udp_inpcb) was
> not empty (80 items).  Lost 8 pages of memory.
> Freed UMA keg (udpcb) was not empty (1008 items).  Lost 6 pages of memory.
> Freed UMA keg (tcptw) was not empty (400 items).  Lost 8 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (90 items).  Lost 9 pages of memory.
> Freed UMA keg (tcpcb) was not empty (44 items).  Lost 11 pages of memory.
> Freed UMA keg (ripcb) was not empty (70 items).  Lost 7 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> epair0a: link state changed to DOWN
> epair0b: link state changed to DOWN
> epair0a: Ethernet address: 02:70:d7:00:07:0a
> epair0b: Ethernet address: 02:70:d7:00:11:0b
> epair0a: link state changed to UP
> epair0b: link state changed to UP
> epair0a: promiscuous mode enabled
> ng_ether_ifnet_arrival_event: can't re-name node epair0b
> arp: 192.168.1.89 moved from 02:96:99:00:0c:0a to 00:02:b3:a2:d7:dd on
> epair5b
> arp: 192.168.1.89 moved from 02:d2:35:00:09:0a to 00:02:b3:a2:d7:dd on
> epair2b
> arp: 192.168.1.89 moved from 02:68:f6:00:0d:0a to 00:02:b3:a2:d7:dd on
> epair6b
> ifa_del_loopback_route: deletion failed Freed UMA keg (udp_inpcb) was
> not empty (80 items).  Lost 8 pages of memory.
> Freed UMA keg (udpcb) was not empty (1008 items).  Lost 6 pages of memory.
> Freed UMA keg (tcptw) was not empty (2350 items).  Lost 47 pages of memory.
> Freed UMA keg (tcp_inpcb) was not empty (2200 items).  Lost 220 pages of memory.
> Freed UMA keg (sackhole) was not empty (606 items).  Lost 6 pages of memory.
> Freed UMA keg (tcpcb) was not empty (76 items).  Lost 19 pages of memory.
> Freed UMA keg (ripcb) was not empty (60 items).  Lost 6 pages of memory.
> hhook_vnet_uninit: hhook_head type=1, id=1 cleanup required
> hhook_vnet_uninit: hhook_head type=1, id=0 cleanup required
> arp: 192.168.1.89 moved from 02:d2:35:00:09:0a to 00:02:b3:a2:d7:dd on
> epair2b
> arp: 192.168.1.89 moved from 00:02:b3:a2:d7:dd to 02:68:f6:00:0d:0a on
> epair6b

-- End of security output --

 

[mattbbpl]

It appears to not be anything to worry about: https://forums.freenas.org/index.php?threads/freed-uma-keg-was-not-empty-lost-pages-of-memory.8281/

 

[Jailer]

Do you have Virtualbox installed? Looks like you have a VM in Virtualbox crashing.

 

[mjt5282]

i believe those are benign kernel warning messages when you stop a Jail, and then possibly restart it.