微波EDA网,见证研发工程师的成长!
首页 > 研发问答 > 移动通信 > 通信设备厂商 > 隐性2A:9告警现有log文件还请高手看看哪块的问题

隐性2A:9告警现有log文件还请高手看看哪块的问题

时间:10-14 整理:3721RD 点击:
如题。

[12-09-12 15:47:27.064] P_MPSS_MMI_HNDL LED.c:895 TRACEH:MMI indication for LED_Operational state ON
[12-09-12 15:47:27.088] EC_Main /C//PowerCtrlImplBase.cpp:205 TRACED:PowerCtrl_PSU_PowerSavingCmd/Disable received
[12-09-12 15:47:27.088] EC_Main P/C//PowerCtrlManager.cpp:716 TRACED:PSU-3 set to Active
[12-09-12 15:47:27.088] EC_Main P/C//PowerCtrlManager.cpp:716 TRACED:PSU-2 set to Active
[12-09-12 15:47:27.088] EC_Main P/C//PowerCtrlManager.cpp:716 TRACED:PSU-1 set to Active
[12-09-12 15:47:27.088] EC_Main P/C//PowerCtrlManager.cpp:716 TRACED:PSU-0 set to Active
[12-09-12 15:47:27.110] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS
[12-09-12 15:47:27.110] TSC_CO_Timing methods.c:1031 TRACEH:External State = RESET
[12-09-12 15:47:27.150] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS
[12-09-12 15:47:27.150] TSC_CO_Timing methods.c:1031 TRACEH:External State = RESET
[12-09-12 15:47:27.150] TSC_CO_Timing methods.c:939 TRACEH:External State = DISABLED
[12-09-12 15:47:27.158] TSC_CO_Timing hw_driver_garp.c:1283 TRACED:NO! TRAFFIC ON SBUS
[12-09-12 15:47:31.076] TSC_CO_Timing methods.c:166 TRACEH:coConfig syncSource = 3, coConfig syncMode = 1
[12-09-12 15:47:31.076] TSC_CO_Timing methods.c:168 TRACEH:coConfig compValue = 0, coConfig FS offset = FFFFFFFFFF
[12-09-12 15:47:31.076] TSC_CO_Timing methods.c:173 TRACEH:coConfig, esbTs= 255, master_TgInst= 65535, master_TXChainDelay:=65535
[12-09-12 15:47:31.076] TSC_CO_Timing methods.c:410 TRACEH:The DXU has been configured to Standalone mode!
[12-09-12 15:47:31.282] TSC_Regulation regulation.c:1464 TRACED:Send subscrSynchStateRsp: synched 0, frame 0, exec 0
[12-09-12 15:48:13.546] O_RBS_Status RBS_STATUS_DEF.c:398 FAULT:12-09-12 15:48 FuncType: DX, Instance 0,  Cease , EC2, SUPPRESS TERR LINK
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:1333 TRACEH:S Y N C H  S T A T E  =  S Y N C H E D !
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2336 TRACED:syncState: SYNCHRONIZED
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2355 TRACED:syncStatus.freqSync: GOOD
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2396 TRACED:syncStatus.frameSync: BAD
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2644 TRACED:exec_ref: 0
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2648 TRACED:FI: 2051
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2651 TRACED:FI_error: 96
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2657 TRACED:freqEst: -1, ip: -1552683998, ep: -31
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2662 TRACED:freqEstVar: 3, ip: 1416582810, ep: -29
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2683 TRACED:c_adj CO.ip:0  C0.ep:-30
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2686 TRACED:c_adj C1.ip:0  C1.ep:-30
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2689 TRACED:c_adj C2.ip:1073741824  C2.ep:-17
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2694 TRACED:refTemp: -1280, tempRange Tmin: 1280, Tmax-1280
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:2697 TRACED:C_V: 8425
[12-09-12 15:50:51.784] TSC_Regulation regulation.c:1464 TRACED:Send subscrSynchStateRsp: synched 1, frame 0, exec 0
[12-09-12 15:50:51.786] TRNS_PATSY_DRV patsy_drv.c:4637 TRACED: AlarmId:69 ATC adj bigger than 150ns
[12-09-12 15:50:51.988] TRNS_PATSY_DRV patsy_drv.c:4637 TRACED: AlarmId:69 ATC adj bigger than 150ns
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65789
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65792
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65790
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65788
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65795
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65793
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65796
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65791
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65794
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65797
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65798
[12-09-12 15:50:53.774] TSC_CO_Timing sync_client.c:373 TRACED:HWU_RC_StartTRX_SynchRsp_t.TarotResult:0  DiracResult:0 Owner pid: 65799

太高深了,不懂。。。。。。

不懂的飘过。。。。。。

更换CDU  代维飘过

不懂细分,一般都是更换CDU,如果问题还没有解决,更换DXU。要看设备的类型,CDU的类型是什么?如果是D型的就更换对应的CU,F就更换对应的CDU

风扇坏了吧

Copyright © 2017-2020 微波EDA网 版权所有

网站地图

Top