项目

一般

简介

错误 #4875 » 0206_du打印.txt

黄 毅, 2026-02-06 14:46

 
1
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 7 subscribers).
2
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 134 priority 0 (remaining 7 subscribers).
3
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 6 subscribers).
4
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 134 priority 0 (remaining 6 subscribers).
5
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 5 subscribers).
6
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 134 priority 0 (remaining 5 subscribers).
7
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 4 subscribers).
8
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 134 priority 0 (remaining 4 subscribers).
9
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 3 subscribers).
10
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 134 priority 0 (remaining 3 subscribers).
11
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 2 subscribers).
12
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 134 priority 0 (remaining 2 subscribers).
13
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 1 subscribers).
14
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 134 priority 0 (remaining 1 subscribers).
15
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 134 priority 0 (remaining 0 subscribers).
16
Feb 06 02:30:24 driver run.sh[896]: [INF]: Session 2259 (user "root", CID 10) created.
17
Feb 06 02:30:24 driver run.sh[896]: CONFIG/INTERFERENCE_MEASUREMENT_ENABLED =1
18
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_PERIOD =500
19
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_TX_ANTNUMBER =4
20
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_ANTNUMBER =4
21
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_AMPLIFER_SWITCH =0
22
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/INTER_CELL_INTERFERENCE_COORDINATION_CFG/ICIC_PATHLOSS_THRESTHOLD =90
23
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PUSCH_RSRP_SMOOTH_FACTOR =80
24
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_SMOOTH_FACTOR =80
25
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_BOOSTING_SWITCH =0
26
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_THRESHOID =50
27
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_THRESHOID =60
28
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_FACTOR =7
29
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_FACTOR =6
30
Feb 06 02:30:24 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_BAD_POINT_FACTOR =5
31
Feb 06 02:30:24 driver run.sh[896]: [06/02/2026 02:30:24.025][ERR][t: 535075744624][MAC_COMM] Fapi_SetPruFreq:The txLo must be same with rxLo in case of tdd mode file: ys_fapi_task.c, line: 1493
32
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 17 subscribers).
33
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 16 subscribers).
34
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 16 subscribers).
35
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 15 subscribers).
36
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 15 subscribers).
37
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 14 subscribers).
38
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 14 subscribers).
39
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 13 subscribers).
40
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 13 subscribers).
41
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 12 subscribers).
42
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 12 subscribers).
43
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 11 subscribers).
44
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 11 subscribers).
45
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 10 subscribers).
46
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 10 subscribers).
47
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 9 subscribers).
48
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 9 subscribers).
49
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 8 subscribers).
50
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 8 subscribers).
51
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 7 subscribers).
52
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 7 subscribers).
53
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 6 subscribers).
54
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 6 subscribers).
55
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 5 subscribers).
56
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 5 subscribers).
57
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 4 subscribers).
58
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 4 subscribers).
59
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 3 subscribers).
60
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 3 subscribers).
61
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 2 subscribers).
62
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 2 subscribers).
63
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 1 subscribers).
64
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 135 priority 0 (remaining 1 subscribers).
65
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 135 priority 0 (remaining 0 subscribers).
66
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 17 subscribers).
67
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 16 subscribers).
68
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 16 subscribers).
69
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 15 subscribers).
70
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 15 subscribers).
71
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 14 subscribers).
72
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 14 subscribers).
73
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 13 subscribers).
74
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 13 subscribers).
75
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 12 subscribers).
76
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 12 subscribers).
77
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 11 subscribers).
78
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 11 subscribers).
79
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 10 subscribers).
80
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 10 subscribers).
81
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 9 subscribers).
82
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 9 subscribers).
83
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 8 subscribers).
84
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 8 subscribers).
85
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 7 subscribers).
86
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 7 subscribers).
87
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 6 subscribers).
88
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 6 subscribers).
89
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 5 subscribers).
90
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 5 subscribers).
91
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 4 subscribers).
92
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 4 subscribers).
93
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 3 subscribers).
94
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 3 subscribers).
95
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 2 subscribers).
96
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 2 subscribers).
97
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 1 subscribers).
98
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 135 priority 0 (remaining 1 subscribers).
99
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 135 priority 0 (remaining 0 subscribers).
100
Feb 06 02:30:24 driver run.sh[896]: [INF]: Session 2261 (user "root", CID 10) created.
101
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 17 subscribers).
102
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 16 subscribers).
103
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 16 subscribers).
104
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 15 subscribers).
105
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 15 subscribers).
106
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 14 subscribers).
107
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 14 subscribers).
108
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 13 subscribers).
109
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 13 subscribers).
110
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 12 subscribers).
111
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 12 subscribers).
112
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 11 subscribers).
113
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 11 subscribers).
114
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 10 subscribers).
115
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 10 subscribers).
116
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 9 subscribers).
117
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 9 subscribers).
118
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 8 subscribers).
119
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 8 subscribers).
120
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 7 subscribers).
121
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 7 subscribers).
122
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 6 subscribers).
123
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 6 subscribers).
124
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 5 subscribers).
125
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 5 subscribers).
126
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 4 subscribers).
127
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 4 subscribers).
128
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 3 subscribers).
129
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 3 subscribers).
130
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 2 subscribers).
131
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 2 subscribers).
132
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 1 subscribers).
133
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 136 priority 0 (remaining 1 subscribers).
134
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 136 priority 0 (remaining 0 subscribers).
135
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 17 subscribers).
136
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 16 subscribers).
137
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 16 subscribers).
138
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 15 subscribers).
139
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 15 subscribers).
140
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 14 subscribers).
141
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 14 subscribers).
142
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 13 subscribers).
143
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 13 subscribers).
144
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 12 subscribers).
145
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 12 subscribers).
146
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 11 subscribers).
147
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 11 subscribers).
148
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 10 subscribers).
149
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 10 subscribers).
150
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 9 subscribers).
151
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 9 subscribers).
152
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 8 subscribers).
153
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 8 subscribers).
154
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 7 subscribers).
155
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 7 subscribers).
156
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 6 subscribers).
157
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 6 subscribers).
158
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 5 subscribers).
159
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 5 subscribers).
160
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 4 subscribers).
161
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 4 subscribers).
162
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 3 subscribers).
163
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 3 subscribers).
164
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 2 subscribers).
165
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 2 subscribers).
166
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 1 subscribers).
167
Feb 06 02:30:24 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 136 priority 0 (remaining 1 subscribers).
168
Feb 06 02:30:24 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 136 priority 0 (remaining 0 subscribers).
169
Feb 06 02:30:26 driver run.sh[896]: cell_pru_cfg_change_cb:trig event will be ignored!event=1!
170
Feb 06 02:30:26 driver run.sh[896]: SR_OP_MODIFIED_old_value:/du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_FREQ=5892420!
171
Feb 06 02:30:26 driver run.sh[896]: SR_OP_MODIFIED_new_value:/du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_FREQ=5879460!
172
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_ENABLED =1
173
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_PERIOD =500
174
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_TX_ANTNUMBER =4
175
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_ANTNUMBER =4
176
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_AMPLIFER_SWITCH =0
177
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/INTER_CELL_INTERFERENCE_COORDINATION_CFG/ICIC_PATHLOSS_THRESTHOLD =90
178
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PUSCH_RSRP_SMOOTH_FACTOR =80
179
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_SMOOTH_FACTOR =80
180
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_BOOSTING_SWITCH =0
181
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_THRESHOID =50
182
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_THRESHOID =60
183
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_FACTOR =7
184
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_FACTOR =6
185
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_BAD_POINT_FACTOR =5
186
Feb 06 02:30:26 driver run.sh[896]: API_RFIC_CellCenterFreqSet,tx Freq=5879460000Hz,rx Freq=5879460000Hz
187
Feb 06 02:30:26 driver run.sh[896]: UCP_API_TRANSCEIVER_Freq_Set,tx Freq=5879460000Hz,rx Freq=5879460000Hz
188
Feb 06 02:30:26 driver run.sh[896]: adi_adrv9025_PllFrequencySet start,freq=5879460000,TrackingCals=0xf0000!
189
Feb 06 02:30:26 driver run.sh[896]: Enter adi_adrv9025_PllFrequencySet,5879460000
190
Feb 06 02:30:26 driver run.sh[896]: Executing the SET PLL Freq command
191
Feb 06 02:30:26 driver run.sh[896]: in adi_adrv9025_PllFrequencySet,result=0
192
Feb 06 02:30:26 driver run.sh[896]: cmdStatusByte=0x1,eventCheck=0
193
Feb 06 02:30:26 driver run.sh[896]: cell_base_para_change_cb:trig event will be ignored!event=1!
194
Feb 06 02:30:26 driver run.sh[896]: SR_OP_MODIFIED_old_value:/du-cell:DU-CELL/BASE/CELL_REBUILD_SWITCH=0!
195
Feb 06 02:30:26 driver run.sh[896]: SR_OP_MODIFIED_new_value:/du-cell:DU-CELL/BASE/CELL_REBUILD_SWITCH=1!
196
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_ENABLED =1
197
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_PERIOD =500
198
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_TX_ANTNUMBER =4
199
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_ANTNUMBER =4
200
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_AMPLIFER_SWITCH =0
201
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/INTER_CELL_INTERFERENCE_COORDINATION_CFG/ICIC_PATHLOSS_THRESTHOLD =90
202
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PUSCH_RSRP_SMOOTH_FACTOR =80
203
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_SMOOTH_FACTOR =80
204
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_BOOSTING_SWITCH =0
205
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_THRESHOID =50
206
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_THRESHOID =60
207
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_FACTOR =7
208
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_FACTOR =6
209
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_BAD_POINT_FACTOR =5
210
Feb 06 02:30:26 driver run.sh[896]: recv_trig_cell_reset msg!
211
Feb 06 02:30:26 driver run.sh[896]: push_opr success:opr_type=1,opr_cause=7,cell_num=1,cell_id[0]=1!
212
Feb 06 02:30:26 driver run.sh[896]: gnb_du_cell::build_mib:cell_id=1,is_cell_barred=1!
213
Feb 06 02:30:26 driver run.sh[896]: gnb_du_cell::build_mib:Successfully encoded MIB cellid[1],mibLen[3],bcchLen[3]!
214
Feb 06 02:30:26 driver run.sh[896]: all module recfg complete!
215
Feb 06 02:30:26 driver run.sh[896]: upt_cell_run_info:update cell run info success,cell_id=1,run_state=2!
216
Feb 06 02:30:26 driver run.sh[896]: cmdStatusByte=0x1,eventCheck=0
217
Feb 06 02:30:26 driver run.sh[896]: opr_admit:cell current run info,cell_id=1,run_state=2!
218
Feb 06 02:30:26 driver run.sh[896]: opr_admit:opr admit success!opr_type=1,opr_cause=7!
219
Feb 06 02:30:26 driver run.sh[896]: upt_cell_run_info:update [INF]: Session 2305 (user "root", CID 10) created.
220
Feb 06 02:30:26 driver run.sh[896]: [INF]: Published event "change" "du-cell" with ID 137 priority 0 for 17 subscribers.
221
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 17 subscribers).
222
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 16 subscribers).
223
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 16 subscribers).
224
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 15 subscribers).
225
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 15 subscribers).
226
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 14 subscribers).
227
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 14 subscribers).
228
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 13 subscribers).
229
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 13 subscribers).
230
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 12 subscribers).
231
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 12 subscribers).
232
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 11 subscribers).
233
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 11 subscribers).
234
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 10 subscribers).
235
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 10 subscribers).
236
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 9 subscribers).
237
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 9 subscribers).
238
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 8 subscribers).
239
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 8 subscribers).
240
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 7 subscribers).
241
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 7 subscribers).
242
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 6 subscribers).
243
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 6 subscribers).
244
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 5 subscribers).
245
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 5 subscribers).
246
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 4 subscribers).
247
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 4 subscribers).
248
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 3 subscribers).
249
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 3 subscribers).
250
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 2 subscribers).
251
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 2 subscribers).
252
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 1 subscribers).
253
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 137 priority 0 (remaining 1 subscribers).
254
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 137 priority 0 (remaining 0 subscribers).
255
Feb 06 02:30:26 driver run.sh[896]: [INF]: Event "change" with ID 137 priority 0 succeeded.
256
Feb 06 02:30:26 driver run.sh[896]: [INF]: Published event "done" "du-cell" with ID 137 priority 0 for 17 subscribers.
257
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 17 subscribers).
258
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 16 subscribers).
259
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 16 subscribers).
260
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 15 subscribers).
261
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 15 subscribers).
262
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 14 subscribers).
263
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 14 subscribers).
264
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 13 subscribers).
265
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 13 subscribers).
266
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 12 subscribers).
267
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 12 subscribers).
268
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 11 subscribers).
269
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 11 subscribers).
270
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 10 subscribers).
271
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 10 subscribers).
272
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 9 subscribers).
273
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 9 subscribers).
274
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 8 subscribers).
275
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 8 subscribers).
276
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 7 subscribers).
277
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 7 subscribers).
278
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 6 subscribers).
279
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 6 subscribers).
280
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 5 subscribers).
281
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 5 subscribers).
282
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 4 subscribers).
283
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 4 subscribers).
284
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 3 subscribers).
285
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 3 subscribers).
286
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 2 subscribers).
287
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 2 subscribers).
288
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 1 subscribers).
289
Feb 06 02:30:26 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 137 priority 0 (remaining 1 subscribers).
290
Feb 06 02:30:26 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 137 priority 0 (remaining 0 subscribers).
291
Feb 06 02:30:26 driver run.sh[896]: cell run info success,cell_id=1,run_state=3!
292
Feb 06 02:30:26 driver run.sh[896]: del trans commit_to_du_mgr(F1_LINK_OK):restart CU process trigger F1_ASSOC_DOWN notify to delete cell!
293
Feb 06 02:30:26 driver run.sh[896]: send_msg_to_server_succ!ip_addr=127.0.0.1,port=9091,msg_len=16!
294
Feb 06 02:30:26 driver run.sh[896]: recv handle_oam_set_cell_status_info msg!
295
Feb 06 02:30:26 driver run.sh[896]: handle_oam_set_cell_status_info:prepare set cell[1] status[0]!
296
Feb 06 02:30:26 driver run.sh[896]: oam_agent_sr_set_item_valUI8:call sr_set_item set value success!
297
Feb 06 02:30:26 driver run.sh[896]: cell_base_para_change_cb:trig event will be ignored!event=1!
298
Feb 06 02:30:26 driver run.sh[896]: SR_OP_MODIFIED_old_value:/du-cell:DU-CELL/BASE/NR_CELL_STATUS=1!
299
Feb 06 02:30:26 driver run.sh[896]: SR_OP_MODIFIED_new_value:/du-cell:DU-CELL/BASE/NR_CELL_STATUS=0!
300
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_ENABLED =1
301
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_PERIOD =500
302
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_TX_ANTNUMBER =4
303
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_ANTNUMBER =4
304
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_AMPLIFER_SWITCH =0
305
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/INTER_CELL_INTERFERENCE_COORDINATION_CFG/ICIC_PATHLOSS_THRESTHOLD =90
306
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PUSCH_RSRP_SMOOTH_FACTOR =80
307
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_SMOOTH_FACTOR =80
308
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_BOOSTING_SWITCH =0
309
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_THRESHOID =50
310
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_THRESHOID =60
311
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_FACTOR =7
312
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_FACTOR =6
313
Feb 06 02:30:26 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_BAD_POINT_FACTOR =5
314
Feb 06 02:30:26 driver run.sh[896]: oam_agent_sr_set_item:call sr_apply_changes apply value success!
315
Feb 06 02:30:26 driver run.sh[896]: handle_oam_set_cell_status_info:set cell[1] status[0] success!
316
Feb 06 02:30:26 driver run.sh[896]: recv f1 assoc down msg!
317
Feb 06 02:30:26 driver run.sh[896]:         ### EGTP recved notify to init SHM ###
318
Feb 06 02:30:26 driver run.sh[896]: gnb_du_udp_rx: DL scene, dyn_slot_format: 7
319
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196637, oriKey: 1100
320
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196638, oriKey: 1101
321
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196639, oriKey: 1102
322
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196640, oriKey: 1103
323
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196641, oriKey: 1104
324
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196642, oriKey: 1105
325
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196643, oriKey: 1106
326
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196644, oriKey: 1107
327
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196645, oriKey: 1108
328
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196646, oriKey: 1109
329
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196647, oriKey: 1110
330
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196648, oriKey: 1111
331
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196649, oriKey: 1112
332
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196650, oriKey: 1113
333
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196651, oriKey: 1114
334
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196652, oriKey: 1115
335
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196653, oriKey: 1116
336
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196654, oriKey: 1117
337
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196655, oriKey: 1118
338
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196656, oriKey: 1119
339
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196657, oriKey: 1120
340
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196658, oriKey: 1121
341
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196659, oriKey: 1122
342
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196660, oriKey: 1123
343
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196661, oriKey: 1124
344
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196662, oriKey: 1125
345
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196663, oriKey: 1126
346
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196664, oriKey: 1127
347
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196665, oriKey: 1128
348
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196666, oriKey: 1129
349
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196667, oriKey: 1130
350
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196668, oriKey: 1131
351
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196669, oriKey: 1132
352
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196670, oriKey: 1133
353
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196671, oriKey: 1134
354
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196672, oriKey: 1135
355
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196673, oriKey: 1136
356
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196674, oriKey: 1137
357
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196675, oriKey: 1138
358
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196676, oriKey: 1139
359
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196677, oriKey: 1140
360
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196678, oriKey: 1141
361
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196679, oriKey: 1142
362
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196680, oriKey: 1143
363
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196681, oriKey: 1144
364
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196682, oriKey: 1145
365
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196683, oriKey: 1146
366
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196684, oriKey: 1147
367
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196685, oriKey: 1148
368
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196686, oriKey: 1149
369
Feb 06 02:30:26 driver run.sh[896]: InitSem: open sem Success!
370
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196687, oriKey: 1000
371
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196688, oriKey: 1001
372
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196689, oriKey: 1002
373
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196690, oriKey: 1003
374
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196691, oriKey: 1004
375
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196692, oriKey: 1005
376
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196693, oriKey: 1006
377
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196694, oriKey: 1007
378
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196695, oriKey: 1008
379
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196696, oriKey: 1009
380
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196697, oriKey: 1010
381
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196698, oriKey: 1011
382
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196699, oriKey: 1012
383
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196700, oriKey: 1013
384
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196701, oriKey: 1014
385
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196702, oriKey: 1015
386
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196703, oriKey: 1016
387
Feb 06 02:30:26 driver run.sh[896]: InitSem: open sem Success!
388
Feb 06 02:30:26 driver run.sh[896]: Succeeded to open shm id:196704, oriKey: 1200
389
Feb 06 02:30:27 driver run.sh[896]: InitSem: open sem Success!
390
Feb 06 02:30:27 driver run.sh[896]: process_lcl_cell_del_request:cell[1] inst is exist!
391
Feb 06 02:30:27 driver run.sh[896]: upt_cell_run_info:update cell run info success,cell_id=1,run_state=3!
392
Feb 06 02:30:27 driver run.sh[896]: ysSm_Fapi_StIdleEvtSTOP6:send stop succ
393
Feb 06 02:30:27 driver run.sh[896]: FAPI_MSG_TYPE_PHY_STOP_IND7:STOP_IND succ
394
Feb 06 02:30:27 driver run.sh[896]: cmdStatusByte=0x1,eventCheck=5
395
Feb 06 02:30:27 driver run.sh[896]: DU Cell Free Start!!!
396
Feb 06 02:30:27 driver run.sh[896]: DU Cell Free End!!!
397
Feb 06 02:30:27 driver run.sh[896]: f1 assoc down delete cell finish!
398
Feb 06 02:30:27 driver run.sh[896]: del trans commit_to_du_mgr:F1_ASSOC_DOWN(delete cell has been finished) or DU_INIT/DU_F1_SCTP_UP_IN_PROGRESS try to setup success!du_state=4!
399
Feb 06 02:30:27 driver run.sh[896]: upt_cell_run_info:update cell run info success,cell_id=1,run_state=0!
400
Feb 06 02:30:27 driver run.sh[896]: push_opr success:opr_type=0,opr_cause=5,cell_num=1,cell_id[0]=1!
401
Feb 06 02:30:27 driver run.sh[896]: commonDev abort
402
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_cpu.c 1152 adi_adrv9025_CpuCmdStatusWait
403
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_hal.c 562 adi_adrv9025_SpiByteRead
404
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_cpu.c 971 adi_adrv9025_CpuCmdStatusOpcodeGet
405
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: private/src/adrv9025_bf_core.c 46 adrv9025_CoreArmCommandBusyBfGet
406
Feb 06 02:30:27 driver run.sh[896]: commonDev abort
407
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_cpu.c 1205 adi_adrv9025_CpuMailboxBusyGet
408
Feb 06 02:30:27 driver run.sh[896]: commonDev abort
409
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_cpu.c 1284 adi_adrv9025_CpuCmdWrite
410
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_radioctrl.c 2594 adi_adrv9025_PllFrequencyGet
411
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_radioctrl.c 805 adi_adrv9025_RadioCtrlCfgSet
412
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_hal.c 562 adi_adrv9025_SpiByteRead
413
Feb 06 02:30:27 driver run.sh[896]: ERR RETURN: public/src/adi_adrv9025_cals.c 446 adi_adrv9025_TrackingCalsEnableSet
414
Feb 06 02:30:27 driver run.sh[896]:  The freq of TDD mode is : 5879460000
415
Feb 06 02:30:27 driver run.sh[896]: [06/02/2026 02:30:27.893][INF][t: 535075744624][MAC_COMM] Fapi_SetPRUFreq success:cell_id[%d],txcellFreq_Hz[%d],rxcellFreq_Hz[%d] file: ys_fapi_task.c, line: 1499
416
Feb 06 02:30:29 driver run.sh[896]: opr_admit:cell current run info,cell_id=1,run_state=0!
417
Feb 06 02:30:29 driver run.sh[896]: opr_admit:opr admit success!opr_type=0,opr_cause=5!
418
Feb 06 02:30:29 driver run.sh[896]: upt_cell_run_info:update cell run info success,cell_id=1,run_state=1!
419
Feb 06 02:30:29 driver run.sh[896]: process_create_cell_request:cell_num=1,opr_cause=5,du state=0!
420
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
421
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
422
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
423
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
424
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
425
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
426
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
427
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
428
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
429
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
430
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
431
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
432
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
433
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
434
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
435
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
436
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
437
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
438
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
439
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
440
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
441
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
442
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
443
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
444
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
445
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
446
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
447
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
448
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc down msg!
449
Feb 06 02:30:29 driver run.sh[896]: DU_INIT state don't handle f1 assoc down msg!
450
Feb 06 02:30:29 driver run.sh[896]: recv f1 assoc up msg!
451
Feb 06 02:30:29 driver run.sh[896]:         ### Triggering F1 Setup Request message...
452
Feb 06 02:30:29 driver run.sh[896]: recv f1 setup rsp!set DU_F1_SETUP_DONE state!
453
Feb 06 02:30:29 driver run.sh[896]: set_slot_cmn_cfg_info dlUlTxPrdcty = 6 nr_mu = 1 dyn_slot_format = 7
454
Feb 06 02:30:29 driver run.sh[896]: abs_freq_ssb=3678240 abs_freq_point_a=3670320 scs_sspdch=30 scs_nssb_crb=15
455
Feb 06 02:30:29 driver run.sh[896]: offset_to_point_a = 24 ssb Subcarrier offset 0
456
Feb 06 02:30:29 driver run.sh[896]: ********************************************************************
457
Feb 06 02:30:29 driver run.sh[896]: CONFIGURING RRM RESOURCE FOR CELL ID [1]
458
Feb 06 02:30:29 driver run.sh[896]: ********************************************************************
459
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 4 Number of RB 1 Start Symbol 13 Number of Symbols 1
460
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 5 Number of RB 1 Start Symbol 13 Number of Symbols 1
461
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 6 Number of RB 1 Start Symbol 13 Number of Symbols 1
462
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 7 Number of RB 1 Start Symbol 13 Number of Symbols 1
463
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 8 Number of RB 1 Start Symbol 13 Number of Symbols 1
464
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 9 Number of RB 1 Start Symbol 13 Number of Symbols 1
465
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 10 Number of RB 1 Start Symbol 13 Number of Symbols 1
466
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 11 Number of RB 1 Start Symbol 13 Number of Symbols 1
467
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 12 Number of RB 1 Start Symbol 13 Number of Symbols 1
468
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 13 Number of RB 1 Start Symbol 13 Number of Symbols 1
469
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 14 Number of RB 1 Start Symbol 13 Number of Symbols 1
470
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 15 Number of RB 1 Start Symbol 13 Number of Symbols 1
471
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 16 Number of RB 1 Start Symbol 13 Number of Symbols 1
472
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 17 Number of RB 1 Start Symbol 13 Number of Symbols 1
473
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 18 Number of RB 1 Start Symbol 13 Number of Symbols 1
474
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 19 Number of RB 1 Start Symbol 13 Number of Symbols 1
475
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 20 Number of RB 1 Start Symbol 13 Number of Symbols 1
476
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 21 Number of RB 1 Start Symbol 13 Number of Symbols 1
477
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 22 Number of RB 1 Start Symbol 13 Number of Symbols 1
478
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 23 Number of RB 1 Start Symbol 13 Number of Symbols 1
479
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 24 Number of RB 1 Start Symbol 13 Number of Symbols 1
480
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 25 Number of RB 1 Start Symbol 13 Number of Symbols 1
481
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 26 Number of RB 1 Start Symbol 13 Number of Symbols 1
482
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 27 Number of RB 1 Start Symbol 13 Number of Symbols 1
483
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 28 Number of RB 1 Start Symbol 13 Number of Symbols 1
484
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 29 Number of RB 1 Start Symbol 13 Number of Symbols 1
485
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 30 Number of RB 1 Start Symbol 13 Number of Symbols 1
486
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 31 Number of RB 1 Start Symbol 13 Number of Symbols 1
487
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 32 Number of RB 1 Start Symbol 13 Number of Symbols 1
488
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 33 Number of RB 1 Start Symbol 13 Number of Symbols 1
489
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 34 Number of RB 1 Start Symbol 13 Number of Symbols 1
490
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 35 Number of RB 1 Start Symbol 13 Number of Symbols 1
491
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 36 Number of RB 2 Start Symbol 13 Number of Symbols 1
492
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 38 Number of RB 2 Start Symbol 13 Number of Symbols 1
493
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 40 Number of RB 2 Start Symbol 13 Number of Symbols 1
494
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 42 Number of RB 2 Start Symbol 13 Number of Symbols 1
495
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 44 Number of RB 2 Start Symbol 13 Number of Symbols 1
496
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 46 Number of RB 2 Start Symbol 13 Number of Symbols 1
497
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 48 Number of RB 2 Start Symbol 13 Number of Symbols 1
498
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 50 Number of RB 2 Start Symbol 13 Number of Symbols 1
499
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 52 Number of RB 2 Start Symbol 13 Number of Symbols 1
500
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 54 Number of RB 2 Start Symbol 13 Number of Symbols 1
501
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 56 Number of RB 2 Start Symbol 13 Number of Symbols 1
502
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 58 Number of RB 2 Start Symbol 13 Number of Symbols 1
503
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 60 Number of RB 2 Start Symbol 13 Number of Symbols 1
504
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 62 Number of RB 2 Start Symbol 13 Number of Symbols 1
505
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 64 Number of RB 2 Start Symbol 13 Number of Symbols 1
506
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 66 Number of RB 2 Start Symbol 13 Number of Symbols 1
507
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 68 Number of RB 5 Start Symbol 13 Number of Symbols 1
508
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 73 Number of RB 5 Start Symbol 13 Number of Symbols 1
509
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 78 Number of RB 5 Start Symbol 13 Number of Symbols 1
510
Feb 06 02:30:29 driver run.sh[896]: Allocated PUCCH ded physical resource : StartRb 83 Number of RB 5 Start Symbol 13 Number of Symbols 1
511
Feb 06 02:30:32 driver run.sh[896]: [INF]: Session 2318 (user "root", CID 10) created.
512
Feb 06 02:30:32 driver run.sh[896]: [INF]: Published event "change" "du-cell" with ID 138 priority 0 for 17 subscribers.
513
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 17 subscribers).
514
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 16 subscribers).
515
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 16 subscribers).
516
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 15 subscribers).
517
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 15 subscribers).
518
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 14 subscribers).
519
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 14 subscribers).
520
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 13 subscribers).
521
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 13 subscribers).
522
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 12 subscribers).
523
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 12 subscribers).
524
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 11 subscribers).
525
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 11 subscribers).
526
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 10 subscribers).
527
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 10 subscribers).
528
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 9 subscribers).
529
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 9 subscribers).
530
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 8 subscribers).
531
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 8 subscribers).
532
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 7 subscribers).
533
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 7 subscribers).
534
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 6 subscribers).
535
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 6 subscribers).
536
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 5 subscribers).
537
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 5 subscribers).
538
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 4 subscribers).
539
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 4 subscribers).
540
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 3 subscribers).
541
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 3 subscribers).
542
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 2 subscribers).
543
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 2 subscribers).
544
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 1 subscribers).
545
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 138 priority 0 (remaining 1 subscribers).
546
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 138 priority 0 (remaining 0 subscribers).
547
Feb 06 02:30:32 driver run.sh[896]: [INF]: Event "change" with ID 138 priority 0 succeeded.
548
Feb 06 02:30:32 driver run.sh[896]: [INF]: Published event "done" "du-cell" with ID 138 priority 0 for 17 subscribers.
549
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 17 subscribers).
550
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 16 subscribers).
551
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 16 subscribers).
552
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 15 subscribers).
553
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 15 subscribers).
554
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 14 subscribers).
555
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 14 subscribers).
556
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 13 subscribers).
557
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 13 subscribers).
558
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 12 subscribers).
559
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 12 subscribers).
560
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 11 subscribers).
561
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 11 subscribers).
562
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 10 subscribers).
563
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 10 subscribers).
564
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 9 subscribers).
565
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 9 subscribers).
566
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 8 subscribers).
567
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 8 subscribers).
568
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 7 subscribers).
569
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 7 subscribers).
570
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 6 subscribers).
571
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 6 subscribers).
572
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 5 subscribers).
573
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 5 subscribers).
574
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 4 subscribers).
575
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 4 subscribers).
576
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 3 subscribers).
577
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 3 subscribers).
578
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 2 subscribers).
579
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 2 subscribers).
580
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 1 subscribers).
581
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 138 priority 0 (remaining 1 subscribers).
582
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 138 priority 0 (remaining 0 subscribers).
583
Feb 06 02:30:32 driver run.sh[896]: [INF]: Published event "change" "du-cell" with ID 139 priority 0 for 17 subscribers.
584
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 17 subscribers).
585
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 16 subscribers).
586
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 16 subscribers).
587
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 15 subscribers).
588
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 15 subscribers).
589
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 14 subscribers).
590
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 14 subscribers).
591
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 13 subscribers).
592
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 13 subscribers).
593
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 12 subscribers).
594
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 12 subscribers).
595
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 11 subscribers).
596
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 11 subscribers).
597
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 10 subscribers).
598
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 10 subscribers).
599
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 9 subscribers).
600
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 9 subscribers).
601
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 8 subscribers).
602
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 8 subscribers).
603
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 7 subscribers).
604
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 7 subscribers).
605
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 6 subscribers).
606
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 6 subscribers).
607
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 5 subscribers).
608
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 5 subscribers).
609
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 4 subscribers).
610
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 4 subscribers).
611
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 3 subscribers).
612
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 3 subscribers).
613
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 2 subscribers).
614
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 2 subscribers).
615
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 1 subscribers).
616
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "change" event with ID 139 priority 0 (remaining 1 subscribers).
617
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "change" event with ID 139 priority 0 (remaining 0 subscribers).
618
Feb 06 02:30:32 driver run.sh[896]: [INF]: Event "change" with ID 139 priority 0 succeeded.
619
Feb 06 02:30:32 driver run.sh[896]: [INF]: Published event "done" "du-cell" with ID 139 priority 0 for 17 subscribers.
620
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 17 subscribers).
621
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 16 subscribers).
622
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 16 subscribers).
623
Feb 06 02:30:32 driver run.sh[896]: CORESET_INPUT BWPID 0 AVG_AL 2 BWP-Start 0 BWP-NumPRB 273
624
Feb 06 02:30:32 driver run.sh[896]: offset_to_point_a =24 cs0_rb_offset=12 cs0_size=48 cntrl_res_setzero=10
625
Feb 06 02:30:32 driver run.sh[896]: cs0_start_rb=0 cs0_end_rb=47 bwp0_start_prb=0 bwp0_num_prb=273
626
Feb 06 02:30:32 driver run.sh[896]: CORESET(s) FOR BWP[0] BWP-START 0 BWP-NUM-RB 273 UL_UE_PER_TTI 4 DL_UE_PER_TTI 4 AVG_AL 2
627
Feb 06 02:30:32 driver run.sh[896]: CORESET-0
628
Feb 06 02:30:32 driver run.sh[896]: CORESET-0
629
Feb 06 02:30:32 driver run.sh[896]:         StartRB 0 numRb 47 numSymbols 1 num_css 1 start_css 1 num_ccs 0 start_ccs 0
630
Feb 06 02:30:32 driver run.sh[896]: CORESET-1
631
Feb 06 02:30:32 driver run.sh[896]:         StartRB 48 numRb 192 numSymbols 1 num_uss 1 start_uss 2 num_ucs 1 start_ucs 1 num_ues_in_cs 128
632
Feb 06 02:30:32 driver run.sh[896]: Num of Dedicated PDCCH Resource configured [128] for BWP_ID [0]
633
Feb 06 02:30:32 driver run.sh[896]: gnb_du_cell::build_mib:cell_id=1,is_cell_barred=0!
634
Feb 06 02:30:32 driver run.sh[896]: gnb_du_cell::build_mib:Successfully encoded MIB cellid[1],mibLen[3],bcchLen[3]!
635
Feb 06 02:30:32 driver run.sh[896]: build_sib1 dlUlTxPrdcty = 6
636
Feb 06 02:30:32 driver run.sh[896]: gnb_du_cell::build_sib1:Successfully encoded SIB1 cellid[1],sib1Len[113],bcchSib1Len[113]!
637
Feb 06 02:30:32 driver run.sh[896]: [sch_cfg] type0 pdcch config is ok!
638
Feb 06 02:30:32 driver run.sh[896]: DL:[5417 13769 8352] UL:[5205 12913 7708]
639
Feb 06 02:30:32 driver run.sh[896]: DL:[5334 14043 8709] UL:[5122 13187 8065]
640
Feb 06 02:30:32 driver run.sh[896]: maxUePerUlSlot 4 maxUePerDlSlot 4 build_sib1 dlUlTxPrdcty = 6
641
Feb 06 02:30:32 driver run.sh[896]: gnb_du_cell::build_sib1:Successfully encoded SIB1 cellid[1],sib1Len[113],bcchSib1Len[113]!
642
Feb 06 02:30:32 driver run.sh[896]: SIB1 for SSB 0 added for schd in slot 10 sib1Lst 0x7d3a75c798 numEnt 1
643
Feb 06 02:30:32 driver run.sh[896]:  [DU_APP]: SI is configured to SCH with si index:1
644
Feb 06 02:30:32 driver run.sh[896]:  SI_CFG_REQ Received with SI index:1 prd 128
645
Feb 06 02:30:32 driver run.sh[896]:  [DU_APP]: SI is configured to SCH with si index:2
646
Feb 06 02:30:32 driver run.sh[896]:  SI_CFG_REQ Received with SI index:2 prd 256
647
Feb 06 02:30:32 driver run.sh[896]: CL:CellId=1 DL BW:100 MHz UL BW:100 MHz Mu:1
648
Feb 06 02:30:32 driver run.sh[896]: ysSm_Fapi_StEvtParam1:send Param succ
649
Feb 06 02:30:32 driver run.sh[896]: FAPI_MSG_TYPE_PHY_PARAM_RESP2:PARAM_RESP succ
650
Feb 06 02:30:32 driver run.sh[896]: ysUtl_Fapi_FillCfgReq: dlPcSwitch[0] ssPbchBlockPowerScaling[-1500] betaPssProfileSSS[0]
651
Feb 06 02:30:32 driver run.sh[896]: ysSm_Fapi_StIdleEvtCfg3:send configRequest succ
652
Feb 06 02:30:32 driver run.sh[896]: FAPI_MSG_TYPE_PHY_CONFIG_RESP4:CONFIG_RESP respCode[0]
653
Feb 06 02:30:32 driver run.sh[896]: ysSm_Fapi_StIdleEvtSTART5:send start succ
654
Feb 06 02:30:32 driver run.sh[896]: recv cl config confirm!send f1 config update!
655
Feb 06 02:30:32 driver run.sh[896]: du_mgr_cell_add_trans:recv f1 sctp assoc up msg!
656
Feb 06 02:30:32 driver run.sh[896]: add trans commit_to_du_mgr:cell setup success!cell_id=1 is UP!
657
Feb 06 02:30:32 driver run.sh[896]: upt_cell_run_info:update cell run info success,cell_id=1,run_state=2!
658
Feb 06 02:30:32 driver run.sh[896]: recv handle_oam_set_cell_status_info msg!
659
Feb 06 02:30:32 driver run.sh[896]: handle_oam_set_cell_status_info:prepare set cell[1] status[1]!
660
Feb 06 02:30:32 driver run.sh[896]: oam_agent_sr_set_item_valUI8:call sr_set_item set value success!
661
Feb 06 02:30:32 driver run.sh[896]: cell_base_para_change_cb:trig event will be ignored!event=1!
662
Feb 06 02:30:32 driver run.sh[896]: SR_OP_MODIFIED_old_value:/du-cell:DU-CELL/BASE/NR_CELL_STATUS=0!
663
Feb 06 02:30:32 driver run.sh[896]: SR_OP_MODIFIED_new_value:/du-cell:DU-CELL/BASE/NR_CELL_STATUS=1!
664
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_ENABLED =1
665
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_PERIOD =500
666
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_TX_ANTNUMBER =4
667
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_ANTNUMBER =4
668
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_AMPLIFER_SWITCH =0
669
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/INTER_CELL_INTERFERENCE_COORDINATION_CFG/ICIC_PATHLOSS_THRESTHOLD =90
670
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PUSCH_RSRP_SMOOTH_FACTOR =80
671
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_SMOOTH_FACTOR =80
672
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_BOOSTING_SWITCH =0
673
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_THRESHOID =50
674
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_THRESHOID =60
675
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_FACTOR =7
676
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_FACTOR =6
677
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_BAD_POINT_FACTOR =5
678
Feb 06 02:30:32 driver run.sh[896]: oam_agent_sr_set_item:call sr_apply_changes apply value success!
679
Feb 06 02:30:32 driver run.sh[896]: handle_oam_set_cell_status_info:set cell[1] status[1] success!
680
Feb 06 02:30:32 driver run.sh[896]: oam_agent_sr_set_item_valUI8:call sr_set_item set value success!
681
Feb 06 02:30:32 driver run.sh[896]: cell_base_para_change_cb:trig event will be ignored!event=1!
682
Feb 06 02:30:32 driver run.sh[896]: SR_OP_MODIFIED_old_value:/du-cell:DU-CELL/BASE/CELL_REBUILD_SWITCH=1!
683
Feb 06 02:30:32 driver run.sh[896]: SR_OP_MODIFIED_new_value:/du-cell:DU-CELL/BASE/CELL_REBUI[INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 15 subscribers).
684
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 15 subscribers).
685
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 14 subscribers).
686
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 14 subscribers).
687
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 13 subscribers).
688
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 13 subscribers).
689
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 12 subscribers).
690
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 12 subscribers).
691
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 11 subscribers).
692
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 11 subscribers).
693
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 10 subscribers).
694
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 10 subscribers).
695
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 9 subscribers).
696
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 9 subscribers).
697
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 8 subscribers).
698
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 8 subscribers).
699
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 7 subscribers).
700
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 7 subscribers).
701
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 6 subscribers).
702
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 6 subscribers).
703
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 5 subscribers).
704
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 5 subscribers).
705
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 4 subscribers).
706
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 4 subscribers).
707
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 3 subscribers).
708
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 3 subscribers).
709
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 2 subscribers).
710
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 2 subscribers).
711
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 1 subscribers).
712
Feb 06 02:30:32 driver run.sh[896]: [INF]: Processing "du-cell" "done" event with ID 139 priority 0 (remaining 1 subscribers).
713
Feb 06 02:30:32 driver run.sh[896]: [INF]: Successful processing of "done" event with ID 139 priority 0 (remaining 0 subscribers).
714
Feb 06 02:30:32 driver run.sh[896]: LD_SWITCH=0!
715
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_ENABLED =1
716
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /gnb-du:GNB-DU/INTERFERENCE_CONFIG/INTERFERENCE_MEASUREMENT_PERIOD =500
717
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_TX_ANTNUMBER =4
718
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PRU_RX_ANTNUMBER =4
719
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_AMPLIFER_SWITCH =0
720
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/INTER_CELL_INTERFERENCE_COORDINATION_CFG/ICIC_PATHLOSS_THRESTHOLD =90
721
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PUSCH_RSRP_SMOOTH_FACTOR =80
722
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_SMOOTH_FACTOR =80
723
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_POWER_BOOSTING_SWITCH =0
724
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_THRESHOID =50
725
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_THRESHOID =60
726
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_GOOD_POINT_FACTOR =7
727
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_MID_POINT_FACTOR =6
728
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/SCHEDULER_CONFIG/CELL_UL_POWER_CONTROL_CFG/UL_PATHLOSS_BAD_POINT_FACTOR =5
729
Feb 06 02:30:32 driver run.sh[896]: oam_agent_sr_set_item:call sr_apply_changes apply value success!
730
Feb 06 02:30:32 driver run.sh[896]: powerAmplifierInfo:staticType=1465445185,staticChannel=15,dynamicChannel=-1
731
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PA_RTX_TYPE = 4
732
Feb 06 02:30:32 driver run.sh[896]: get_cell_config /du-cell:DU-CELL/PRU_CONFIG/NR_CELL_PA_CHANNEL = 4369
733
Feb 06 02:30:32 driver run.sh[896]: PA SET CHANNEL SAME
734
Feb 06 02:30:32 driver run.sh[896]: CELL[1] is UP!!!
735
Feb 06 02:30:32 driver run.sh[896]: #############################################################################
736
Feb 06 02:30:32 driver run.sh[896]: ## DU VERSION
737
Feb 06 02:30:32 driver run.sh[896]: #############################################################################
738
Feb 06 02:30:32 driver run.sh[896]: ## Version: YZS-NRD-V2.2.24
739
Feb 06 02:30:32 driver run.sh[896]: ## Image Date: Jan 30 2026
740
Feb 06 02:30:32 driver run.sh[896]: ## Image Time: 01:08:59
741
Feb 06 02:30:32 driver run.sh[896]: ## The hash value is: 026eca687d88be0c649ca693c575b99aa5e8e53b
742
Feb 06 02:30:32 driver run.sh[896]: #############################################################################
(2-2/5)