Aerial cuPHY reports UL channel wait timeout after O-RU becomes DuConnected Ready

Accelerated Computing Aerial Forum
,
1

Hi NVIDIA Aerial team,

We are running Aerial/OAI with a commercial O-RU. After updating the O-RU configuration, the O-RU is now synchronized and reports DuConnected : Ready.

Current O-RU configuration:

Band Width = 100000000
Center Frequency = 3750000000
Compression Bit = 9
Control and User Plane vlan = 2
M Plane vlan = 100
default gateway = 10.101.131.254
dpd mode : Enable
DU MAC Address = 4cbb472ff26b
phase compensation mode : Enable
RX gain = 14
TX power = 24
subcarrier spacing = 1
rj45_vlan_ip = 10.101.131.61
SFP_vlan_ip = 10.101.131.62
SFP_non_vlan_static_ip = 192.168.1.100
prach eAxC-id port 0, 1, 2, 3 = 0x0004, 0x0005, 0x0006, 0x0007
slotid = 0x00000001
jumboframe = 0x00000001
sync source : PTP

O-RU status:

Sync State  : SYNCHRONIZED
RF State    : Ready
DPD         : Ready
DuConnected : Ready

However, during UE access / UL processing, we still see the following Aerial cuPHY error:

08:59:24.600005 CON timer_thread 0 [SCF.PHY] Cell  0 | DL    0.04 Mbps   50 Slots | UL    0.00 Mbps    0 Slots CRC   0 (     0) | Tick 9600000
08:59:25.600005 CON timer_thread 0 [SCF.PHY] Cell  0 | DL    0.04 Mbps   50 Slots | UL    0.00 Mbps    0 Slots CRC   0 (     0) | Tick 9602000
08:59:26.027411 ERR UlPhyDriver06 0 [AERIAL_CUPHYDRV_API_EVENT] [DRV.MAP_UL] Wait UL channel threads for Map 396 is taking more than 8000000 ns
08:59:26.027412 ERR UlPhyDriver06 0 [AERIAL_CUPHYDRV_API_EVENT] [DRV.FUNC_UL] waitChannelEndTask returned error for Slot Map 396 num_ul_tasks=6 num_ulc_tasks=2 num_ul_tasks_to_wait=1
08:59:26.028843 WRN UlPhyDriver05 0 [DRV.PERF_METRICS] PercentileTracker::addValue :: Value 9342811 above maximum, clamping to 2999999
08:59:26.600005 CON timer_thread 0 [SCF.PHY] Cell  0 | DL    0.04 Mbps   51 Slots | UL    0.00 Mbps    0 Slots CRC   0 (     0) | Tick 9604000
08:59:27.600005 CON timer_thread 0 [SCF.PHY] Cell  0 | DL    0.04 Mbps   50 Slots | UL    0.00 Mbps    0 Slots CRC   0 (     0) | Tick 9606000

Could you please help clarify what this error means and what the recommended debugging steps are for:

[DRV.MAP_UL] Wait UL channel threads for Map 396 is taking more than 8000000 ns
[DRV.FUNC_UL] waitChannelEndTask returned error for Slot Map 396

In particular, should this be interpreted as an UL timing / real-time scheduling issue, or as an indication that the expected UL U-plane data for the scheduled UL slot was not received or could not be matched by cuPHY?

Thanks.

2

Hi @xudong.zhao ,

Can you share complete phy log and your yaml files?

From the limited logs above, it does not seem to be caused by issues in UL packet reception since there are no warning/error messages from the order kernel.

Thank you.