Last Modified: Aug 25, 2026
Affected Product(s):
F5OS F5OS-A
Known Affected Versions:
F5OS-A 1.5.4, F5OS-A 1.8.3, F5OS-A 1.8.4, F5OS-A 1.8.4-HR1
Opened: Jun 09, 2026 Severity: 3-Major
On F5 r2k platforms, enabling an interface may fail to bring it up. This issue arises from a failure to allocate memory for the RX/TX buffers required by the interface. The insufficient memory occurs due to a memory leak within the nic manager. Here is what is logged in /var/log/messages when the failure to allocate memory occurs: 2026-03-24T09:26:06.146009+08:00 hostname kernel: nic_manager: page allocation failure: order:4, mode:0xd0 2026-03-24T09:26:06.146122+08:00 hostname kernel: CPU: 7 PID: 10291 Comm: nic_manager Kdump: loaded Tainted: G OE ------------ T 3.10.0-1160.119.1.f5.1.el7_8.x86_64 #1 2026-03-24T09:26:06.146164+08:00 hostname kernel: Hardware name: C130/OEM-0532-00 REV E , BIOS PGF: PGF-0303-xx BIOS: 1.00.154.1 ME: 5.0.3.204 07/27/2023 2026-03-24T09:26:06.146204+08:00 hostname kernel: Call Trace: 2026-03-24T09:26:06.146237+08:00 hostname kernel: [<ffffffff96dd46b0>] dump_stack+0x19/0x1f 2026-03-24T09:26:06.146268+08:00 hostname kernel: [<ffffffff967d9ad5>] warn_alloc_failed+0x115/0x190 2026-03-24T09:26:06.146297+08:00 hostname kernel: [<ffffffff967de5b7>] ? __alloc_pages_direct_compact+0x1b7/0x1c0 2026-03-24T09:26:06.146329+08:00 hostname kernel: [<ffffffff967dee96>] __alloc_pages_nodemask+0x8d6/0xa90 2026-03-24T09:26:06.146358+08:00 hostname kernel: [<ffffffff96832fe8>] alloc_pages_current+0x98/0x120 2026-03-24T09:26:06.146388+08:00 hostname kernel: [<ffffffff96c55b1d>] intel_alloc_coherent+0x5d/0x150 2026-03-24T09:26:06.146416+08:00 hostname kernel: [<ffffffff96b078b4>] dmam_alloc_coherent+0xb4/0x130 2026-03-24T09:26:06.146448+08:00 hostname kernel: [<ffffffffc085ded2>] ice_setup_rx_ring+0x72/0xe0 [ice] 2026-03-24T09:26:06.146476+08:00 hostname kernel: [<ffffffffc0833c93>] ice_vsi_setup_rx_rings+0x63/0xb0 [ice] 2026-03-24T09:26:06.146507+08:00 hostname kernel: [<ffffffffc0834fbc>] ice_vsi_open+0x3c/0x150 [ice] 2026-03-24T09:26:06.146536+08:00 hostname kernel: [<ffffffff96afaa2c>] ? devm_kfree+0x2c/0x50 2026-03-24T09:26:06.146565+08:00 hostname kernel: [<ffffffffc08356d1>] ice_open_internal+0xc1/0x210 [ice] 2026-03-24T09:26:06.146594+08:00 hostname kernel: [<ffffffffc0835850>] ice_open+0x30/0x60 [ice] 2026-03-24T09:26:06.146629+08:00 hostname kernel: [<ffffffff96ca6596>] __dev_open+0xd6/0x170 2026-03-24T09:26:06.146665+08:00 hostname kernel: [<ffffffff96ddbfee>] ? _raw_spin_unlock_bh+0x1e/0x30 2026-03-24T09:26:06.146694+08:00 hostname kernel: [<ffffffff96ca68e3>] __dev_change_flags+0xa3/0x190 2026-03-24T09:26:06.146727+08:00 hostname kernel: [<ffffffff96ca69f9>] dev_change_flags+0x29/0x70 2026-03-24T09:26:06.146754+08:00 hostname kernel: [<ffffffff96d2e9e1>] devinet_ioctl+0x671/0x790 2026-03-24T09:26:06.146782+08:00 hostname kernel: [<ffffffff96d2fe05>] inet_ioctl+0x85/0xc0 2026-03-24T09:26:06.146815+08:00 hostname kernel: [<ffffffff96c7e4eb>] sock_do_ioctl+0x2b/0x60 2026-03-24T09:26:06.146844+08:00 hostname kernel: [<ffffffff96c7e700>] sock_ioctl+0x1e0/0x2b0 2026-03-24T09:26:06.146872+08:00 hostname kernel: [<ffffffff96881daf>] do_vfs_ioctl+0x47f/0x5f0 2026-03-24T09:26:06.146903+08:00 hostname kernel: [<ffffffff96c7e395>] ? sock_alloc_file+0xa5/0x140 2026-03-24T09:26:06.146930+08:00 hostname kernel: [<ffffffff96881fa1>] SyS_ioctl+0x81/0xa0 2026-03-24T09:26:06.146959+08:00 hostname kernel: [<ffffffff9674d45c>] ? __audit_syscall_exit+0x20c/0x2b0 2026-03-24T09:26:06.146989+08:00 hostname kernel: [<ffffffff96de7cda>] system_call_fastpath+0x25/0x2a
Enabling an interface fails to bring the interface up.
The likelihood of an interface failing to come up increases as more interfaces are repeatedly enabled and disabled.
1. Stop the nic-manager container as well as the l2-agent docker stop system_L2 docker stop nic-manager 2. Ensure they are both stopped docker ps -a --filter "name=system_L2" docker ps -a --filter "name=nic-manager" ex. for l2-agent showing it as exited # docker ps -a --filter "name=system_L2" CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d3c670d3dd12 localhost:2504/l2_agent:9.7.0-f5os-a-1-8-5-candidate.2026-05-12-09-14-19.S9547e872 "/confd/scripts/agent" 4 days ago Exited (1) 6 seconds ago 3. Then (re)start them docker start nic-manager docker start system_L2 4. And finally check that they are running. docker ps -a --filter "name=system_L2" docker ps -a --filter "name=nic-manager" ex. for system_L2 # docker ps -a --filter "name=system_L2" CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES d3c670d3dd12 localhost:2504/l2_agent:9.7.0-f5os-a-1-8-5-candidate.2026-05-12-09-14-19.S9547e872 "/confd/scripts/agent" 4 days ago Up 7 seconds system_L2
None