Luckfox Pico Pi A W 在使用wifi访问rtsp系统会卡死

2026-01-11 3:36

通过rtsp访问视频，在运行一会之后就会出现系统卡死，必须通过重启才成正常访问，下面是日志

[video.c][rkipc_ivs_get_results]:MD: md_area is 503808, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 503808, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 503808, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 505856, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 505856, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 516096, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 509952, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 510976, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 505856, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 516096, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 516096, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 460800, md_area_threshold is 155520
[video.c][rkipc_ivs_get_results]:MD: md_area is 358400, md_area_threshold is 155520
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[WARN  rtsp_demo.c:1624:rtsp_tx_video] client 192.168.31.222 will lost video packet
[DEBUG rtsp_demo.c:1158:rtsp_recv_msg] peer closed
[INFO  rtsp_demo.c:427:rtsp_del_client_connection] delete client 78 from 192.168.31.222

2026-01-12 1:39

您好，从日志上看是网络连接的问题，有可能是 WiFi 信号强度太弱或者码流过大导致

2026-01-12 10:10

这个开发板wifi的参数那里有？而且sc3336摄像头的码流也很一般吧？再一个这个卡死是不是不太合理？

2026-01-12 10:14

Crocodile wrote: ↑2026-01-12 1:39 您好，从日志上看是网络连接的问题，有可能是 WiFi 信号强度太弱或者码流过大导致

这个开发板wifi的参数那里有？设备离路由器只有3，4米，使用的sc3336摄像头，这俩都不应该吧？

2026-01-13 1:40

信号强度主要看实际网络环境，可以在连接WiFi 后用wpa_cli result_scan来确定信号强度多少，天线摆放位置不对有障碍物或者天线连接不稳定都会导致信号强度变弱或者不稳定，信号时强时弱或者一直很弱的情况下sc3336默认的3M@30fps 的H265 码流算比较大的，默认rkipc只会识别网络连接状态来确定是否推流，在信号强度差的时候强行推流会一直触发报错，这个时候有可能会导致内存错误导致系统卡死。

2026-01-24 8:07

Crocodile wrote: ↑2026-01-13 1:40 信号强度主要看实际网络环境，可以在连接WiFi 后用wpa_cli result_scan来确定信号强度多少，天线摆放位置不对有障碍物或者天线连接不稳定都会导致信号强度变弱或者不稳定，信号时强时弱或者一直很弱的情况下sc3336默认的3M@30fps 的H265 码流算比较大的，默认rkipc只会识别网络连接状态来确定是否推流，在信号强度差的时候强行推流会一直触发报错，这个时候有可能会导致内存错误导致系统卡死。

我确认的wifi的强度没有问题，在-20 dBm 到 -50 dBm之间，但是我发现wlan会连接两个IP ，图片中43的ip无法正常访问到设备，删除 43的ip后，设备移动位置rtsp没有断开，设备没有卡死，为什么设备会连接两个ip？

2026-01-26 1:59

出现这种情况一般是设置了静态IP的同时又从DHCP 服务器申请IP, 局域网内客户端有两个IP一般是没问题的，但是运行RTSP的时候是作为服务器给其他客户端推流，有可能是IP发包冲突导致的，具体您可以用wireshark等网络分析工具确定一下

2026-02-28 4:28

Crocodile wrote: ↑2026-01-26 1:59 出现这种情况一般是设置了静态IP的同时又从DHCP 服务器申请IP, 局域网内客户端有两个IP一般是没问题的，但是运行RTSP的时候是作为服务器给其他客户端推流，有可能是IP发包冲突导致的，具体您可以用wireshark等网络分析工具确定一下

IPf发包冲突确实是有问题，我定位到了根本问题，确定由于信号强度波动导致设备卡死的，并且设备离路由器并不远，导致卡死的原因是rkipc的rstp阻塞导致的，这个有什么解决办法吗？我尝试过降低分辨率，1280x720测试仍然会有问题，

2026-02-28 5:53

rkipc 的 rtsp 库是 rockchip 基于 live555 开发的，本身没有开源，可以获取live555二次开发替换丢包处理方式