mtk crash panic问题分析

1.起源
BT 站位发生的fail信息:21:46:23发生的AP PANICS_1,并向前查开始测试时间是21:46:10,006
2019-07-14 21:46:10,006     []     INFO      TEST_APP_2010    21:46:10.0063385    READ_LOG_PANIC_ANDROID_1_ERASE    Header    Test = READ_LOG_PANIC_ANDROID_1_ERASE  |  Barcode = NJIL440424  |  Time start = 7/14/2019 9:46:10 PM

2019-07-14 21:46:23,609     []     INFO      TEST_APP_2010    21:46:23.6090939    READ_LOG_PANIC_ANDROID_1_ERASE    EvalAndLogResults    52    46    AP PANICS_1    0    0    1    P/F    10    53919    * FAILED *    

2.追溯
根据问题发生的时间,在maillog对应的时间点附近查看问题:搜关键字 aee_core_forwarder
07-14 21:46:12.126704  2845  2845 I aee_core_forwarder: socket name: android:aee_aed, sfd: 5
再查看下面对应的aee_aed
07-14 21:46:12.126704  2845  2845 I aee_core_forwarder: socket name: android:aee_aed, sfd: 5
07-14 21:46:12.126821   660   660 D AEE_AED : $===AEE===AEE===AEE===$
07-14 21:46:12.126918   660   660 D AEE_AED : p 2 poll events 1 revents 1
07-14 21:46:12.127340   660   660 D AEE_AED : PPM cpu cores:8, online:8
07-14 21:46:12.128146   660   660 D AEE_AED : aed_main_fork_worker: generator 0xa84880d8, worker 0xbef5d8b8, recv_fd 10
07-14 21:46:12.131006  2851  2851 I AEE_AED : pid: 1486, tid: 1746, >>> com.android.bluetooth <<<
07-14 21:46:12.131316  2851  2851 D AEE_AED : u:r:bluetooth:s0
07-14 21:46:12.131353  2851  2851 V AEE_AED : dashboard_record_update() : rec->module = com.android.bluetooth 
07-14 21:46:12.131390  2851  2851 V AEE_AED : Update record[1] 

在看时间点附近的关键字com.android.bluetooth    再对照*** Exception ** 查看 
07-14 21:46:13.457265  2851  2851 I AEE_AED : $** *** *** *** *** *** *** *** Exception *** *** *** *** *** *** *** **$
07-14 21:46:13.457547  2851  2851 I AEE_AED : Build Info: 'alps-mp-p0.mp1.tc2sp:alps-mp-p0.mp1.tc2sp-V1.33:mt6771:S01,motorola/lima_32_factory/lima:9/PMD29.63/7a598:userdebug/release-keys'
07-14 21:46:13.457593  2851  2851 I AEE_AED : Flavor Info: 'None'
07-14 21:46:13.457662  2851  2851 I AEE_AED : Exception Log Time:[Sun Jul 14 21:46:13 GMT 2019] [31.216393]
07-14 21:46:13.457662  2851  2851 I AEE_AED : 
07-14 21:46:13.457707  2851  2851 I AEE_AED : Exception Class: Native (NE)
07-14 21:46:13.457773  2851  2851 I AEE_AED : Exception Type: SIGABRT
07-14 21:46:13.457773  2851  2851 I AEE_AED : 
07-14 21:46:13.457815  2851  2851 I AEE_AED : Current Executing Process: 
07-14 21:46:13.457815  2851  2851 I AEE_AED :   pid: 1486, tid: 1746
07-14 21:46:13.457815  2851  2851 I AEE_AED :   com.android.bluetooth
07-14 21:46:13.457815  2851  2851 I AEE_AED : 
07-14 21:46:13.457897  2851  2851 I AEE_AED : $** *** *** *** *** *** *** *** Exception *** *** *** *** *** *** *** **$
07-14 21:46:13.458057  2851  2851 D AEE_AED : /system/bin/aee_dumpstate: filepath /data/aee_exp/temp/db.CQ8mPB, pid 1486, tid 1746, exp_class 3, db_opt 0

总结:基本从上面可以锁定是com.android.bluetooth引起了系统panic


//最近崩溃的栈日志,这个用于快速定位问题  搜关键字backtrace
adb shell dumpsys dropbox --print > fc_log/dropbox.txt
 

你可能感兴趣的:(驱动管理)