XT9更新最新版固件后频繁断网

JueFerdinand

RT，XT9更新最新版固件(ASUS ZenWiFi XT9 固件版本 3.0.0.4.388.23285)后，频繁断网。表现为路由器下所有设备无法分配到IP地址，但是路由器本身正常亮白灯。查看系统记录，提示说无法分配请求的缓冲区，这个问题是更新5月15号最新的固件才出现的，之前一直稳如狗。下挂设备断网后，任何终端无法连接路由器后台，只能给路由器断电重启才能恢复正常。但是问题还会继续出现，快的时候在重启半个小时后就再次出现，或者几个小时都出现过，请问怎么解决？附上故障日志内容：
May 17 00:38:11 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (125:17236)^[[0m
May 17 00:38:16 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 0^[[0m
May 17 00:38:16 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 1^[[0m
May 17 00:38:16 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 2^[[0m
May 17 00:38:17 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 4^[[0m
May 17 00:38:17 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 8^[[0m
May 17 00:38:18 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 16^[[0m
May 17 00:38:19 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 32^[[0m
May 17 00:38:28 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (32:17236)^[[0m
May 17 00:38:39 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 64^[[0m
May 17 00:38:42 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 128^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (32:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:44 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:44 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:44 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:44 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:44 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:44 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:45 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:38:57 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 256^[[0m
May 17 00:39:06 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:39:10 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 512^[[0m
May 17 00:39:11 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:39:18 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:39:27 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:39:35 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 1024^[[0m
May 17 00:39:43 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:40:15 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m
May 17 00:40:33 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 2048^[[0m
May 17 00:40:59 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 32768^[[0m
May 17 00:40:59 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 65536^[[0m
May 17 00:40:59 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 131072^[[0m
May 17 00:41:00 kernel: ^[[0;34m[NTC bpm] bpm_alloc_mult_buf_ex: Failed to allocate 128 buffers; buf_fail_cnt = 1048576^[[0m
May 17 00:41:19 kernel: ^[[0;34m[NTC bpm] bpm_buf_expand: Could not allocate requested buffers (0:17236)^[[0m

微信扫一扫，阅读更方便^_^

JueFerdinand

Sprite 发表于 2023-5-17 11:04
恢复后正常点一次问题反馈并告知下邮箱,请官方看一下？

已经反馈了
1749468821@qq.com

JueFerdinand

paldier 发表于 2023-5-17 11:32
应该是内存爆了，目测有地方内存泄露

看系统状态RAM占用基本都是50左右

JueFerdinand

Sprite 发表于 2023-5-17 14:00
现在降级到前一版会正常吗?

还没有降级，最后一次断电重启到现在运行一天多了，我要再看看。再出现就先降级

JueFerdinand

paldier 发表于 2023-5-20 14:03
反编译看了下代码，内存确实已经满了，只不过不是你看到的那些，目前没发现非华硕有这问题，应该是华硕内 ...

应该是的，华硕官网出回应了，大规模宕机

JueFerdinand

pal**r 发表于 2023-5-21 10:58
和这个一点关系没有

IT之家 5 月 20 日消息，海内外多个用户反馈称， 5 月 16 日前后，华硕服务器推送了错误的固件更新导致华硕路由器系统内存溢出。这一问题极大程度上影响了 Wi-Fi 性能，甚至出现断网的情况。

具体来说，自5月16日以来，全球有大量用户反映自己的华硕路由器在运行过程中，会无缘无故、自动地断开网络连接(参阅图二)，而且这绝不是极个别的案例，吐槽类似问题的用户众多。

华硕方面在接到这些反馈后，态度比较谨慎，并未在第一时间回应这些问题，直到5月19日，华硕英文官方产品支持页面才对这个问题进行了正式回应(图三)：

“在日常安全维护期间，我们的技术团队在服务器(有关路由器的)设置文件的配置中发现了一个错误，这可能会导致部分路由器的网络连接中断。”并表示，目前已经“紧急解决了服务器问题”，之前受影响的路由器现在都应该完全恢复正常运行。

是不是这个，刷到好多媒体在说这个事情，和我的时间点也一样，现在我自从最后一次重启后，目前都是稳定的。