项目

一般

简介

错误 #4875

[3.0产品测试] 干扰规避测试中，干扰规避或者干扰恢复后，终端有时搜不到小区

由 黄 毅 在 19 天 之前添加. 更新于 19 天 之前.

状态:
新建
优先级:
一般
指派给:
李 明新
开始日期:
2026-02-06
计划完成日期:
% 完成:

0%

预期时间:
问题归属:
CU, DRV
发现问题版本:
Rel_3.1.4
目标解决问题版本:
Rel_3.1.4

描述

测试版本：Rel3.1.4_Pre1T4版本
测试设备：军特整机192.168.8.234，网管：192.168.8.170
测试用例：干扰规避测试（前半段调跳频）
基站配置：7D2U
测试终端：星创CPE
测试场景：基站启动正常，终端接入做下行业务。打开信号源干扰前半段，触发干扰规避，取消干扰，小区恢复。
反复3组，在第3次干扰恢复后，终端无法搜到小区。前2组都正常。

文件

0206.rar (2.41 MB) 0206.rar 黄 毅, 2026-02-06 14:46
0206_du打印.txt (85.7 KB) 0206_du打印.txt 黄 毅, 2026-02-06 14:46
du_0206干扰规避.log (1.08 MB) du_0206干扰规避.log 惠 帅帅, 2026-02-07 09:14
gnb.pcap (328 KB) gnb.pcap 惠 帅帅, 2026-02-07 09:16
gnb_du_20260130T010827_20260206091024_306.yzb.log (9.37 MB) gnb_du_20260130T010827_20260206091024_306.yzb.log 惠 帅帅, 2026-02-07 09:16

历史记录

#1

由 惠 帅帅 更新于 19 天 之前

#3

由 惠 帅帅 更新于 19 天 之前

结合du_0206干扰规避.log和gnb_du_xxx.log分析，存在2个问题。

问题1：射频频点生效失败
两次触发间隔5分钟，第一次没有adidriver异常打印，频点修改正常；第二次有异常打印，频点修改异常。
第一次频点修改正常log截取
Feb 06 09:05:43 driver run.sh838: cmdStatusByte=0x0,eventCheck=5
Feb 06 09:05:43 driver run.sh838: The freq of TDD mode is : 5892420000
Feb 06 09:05:43 driver run.sh838: [06/02/2026 09:05:43.544][INF][t: 535132367728][MAC_COMM] Fapi_SetPRUFreq success

第二次频点修改异常log截取
Feb 06 09:10:46 driver run.sh838: cmdStatusByte=0x1,eventCheck=5
Feb 06 09:10:46 driver run.sh838: commonDev abort
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_cpu.c 1152 adi_adrv9025_CpuCmdStatusWait
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_hal.c 562 adi_adrv9025_SpiByteRead
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_cpu.c 971 adi_adrv9025_CpuCmdStatusOpcodeGet
Feb 06 09:10:46 driver run.sh838: ERR RETURN: private/src/adrv9025_bf_core.c 46 adrv9025_CoreArmCommandBusyBfGet
Feb 06 09:10:46 driver run.sh838: commonDev abort
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_cpu.c 1205 adi_adrv9025_CpuMailboxBusyGet
Feb 06 09:10:46 driver run.sh838: commonDev abort
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_cpu.c 1284 adi_adrv9025_CpuCmdWrite
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_radioctrl.c 2594 adi_adrv9025_PllFrequencyGet
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_radioctrl.c 805 adi_adrv9025_RadioCtrlCfgSet
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_hal.c 562 adi_adrv9025_SpiByteRead
Feb 06 09:10:46 driver run.sh838: ERR RETURN: public/src/adi_adrv9025_cals.c 446 adi_adrv9025_TrackingCalsEnableSet
Feb 06 09:10:46 driver run.sh838: The freq of TDD mode is : 5879460000
Feb 06 09:10:46 driver run.sh838: [06/02/2026 09:10:46.017][INF][t: 535132367728][MAC_COMM] Fapi_SetPRUFreq success

问题2：业务小区建立成功时，调用API_PA_DynamicParaGet获取的动态功放通道状态都为-1(无效值)。
第一次获取的动态功放通道状态log截取
Feb 06 09:05:47 driver run.sh838: powerAmplifierInfo:staticType=1465445185,staticChannel=15,dynamicChannel=-1
Feb 06 09:05:47 driver run.sh838: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PA_RTX_TYPE = 4
Feb 06 09:05:47 driver run.sh838: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PA_CHANNEL = 4369
Feb 06 09:05:47 driver run.sh838: PA SET CHANNEL SAME
Feb 06 09:05:47 driver run.sh838: CELL1 is UP!!!

第二次获取的动态功放通道状态log截取
Feb 06 09:10:49 driver run.sh838: powerAmplifierInfo:staticType=1465445185,staticChannel=15,dynamicChannel=-1
Feb 06 09:10:49 driver run.sh838: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PA_RTX_TYPE = 4
Feb 06 09:10:49 driver run.sh838: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PA_CHANNEL = 4369
Feb 06 09:10:49 driver run.sh838: PA SET CHANNEL SAME
Feb 06 09:10:49 driver run.sh838: CELL1 is UP!!!

备注：第一次业务正常而动态通道获取输出为-1无效值，说明可能只是API_PA_DynamicParaGet接口内部逻辑有问题，而实际生效的通道状态应该是正常的。

上述两个问题，需要明新这边定位一下~

#4

由 惠 帅帅 更新于 19 天 之前

  • 指派给 从 惠 帅帅 变更为 李 明新

导出 Atom PDF