Bug #117970
测试 Test-ST #113421: V4.0功能与专项测试
测试 Test-ST #113422: V4.0专项--AF专项--monkey测试
【IOVDEV-28247】【AF】【EVT3】【Monkey】【稳定性测试】【VC1】【副屏】/system/bin/audioserver tombstone
| Status: | CLOSED | Start date: | 2023-05-16 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | 物联网测试组_CDTS 唐霞 | % Done: | 0% | |
| Category: | AUDIO-FW | |||
| Target version: | - | |||
| Need_Info: | -- | Found Version: | 03.02.0078.C101 | |
| Resolution: | DUPLICATE | Degrated: | -- | |
| Severity: | Normal | Verified Version: | ||
| Reproducibility: | Occasionally | Fixed Version: | ||
| Test Type: | Monkey Test | Root cause: |
Description
测试手顺：
副屏执行monkey稳定性测试
预期结果：
无黑卡死等严重问题发生，无Crash、ANR、Tombstone内存泄露等
实际结果：
/system/bin/audioserver tombstone
History
#2 Updated by CD FW 曹覃刚 about 2 years ago
- Category changed from 客户jira bug to AUDIO-FW
- Status changed from New to ASSIGNED
- Assignee changed from CD FW 曹覃刚 to Multimedia组-RD3_TSCD 梁卿山
Hi 卿山
/system/bin/audioserver tombstone
audio相关，请帮忙分析
#3 Updated by CD MM陈海波 about 2 years ago
AudioServer中有个守护线程TimeCheckThread, 会监控Audioflinger响应客户段请求命令的响应情况.
一旦传给服务端Audioflinger的binder指令处理的线程超时, 就会报出'TimeCheck timeout for IAudioFlinger command xx'的tombstone.
当前票报的正是这个错误:
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- Abort message: 'TimeCheck timeout for IAudioFlinger command 23'---
从tombstone上推断, 怀疑是FastMixer写不下数据导致.
但由于bugreport和提供的log和tombstone报的时间不符, 没法在继续推断到底是哪个流程环境被卡住了,
需要重新抓取log信息才可以.
所以麻烦重新测试, 并根据下边的要求抓取对应的log信息.
测试前环境准备:
1. 清空anr和tombstones文件夹, 以免影响问题产生原因. adb shell rm -rf /data/anr/* adb shell rm -rf /data/tombstones/* 2. 执行下边的命令, 放开audio驱动的log: adb shell echo -n "file soc-pcm.c +p" > /sys/kernel/debug/dynamic_debug/control;echo -n "file soc-dapm.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file adsp_err.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file audio_cal_utils.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file audio_calibration.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file audio_slimslave.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-audio-effects-q6-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-compress-q6-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-dai-q6-hdmi-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-dai-q6-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-dai-slim.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-dai-stub-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-dolby-dap-config.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-ds2-dap-config.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-dts-srs-tm-config.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-lsm-client.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-afe-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-dtmf-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-host-voice-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-loopback-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-lpa-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-q6-noirq.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-q6-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-routing-devdep.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-routing-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-voice-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-pcm-voip-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file msm-qti-pp-config.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file q6adm.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file q6afe.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file q6asm.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file q6audio-v2.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file q6core.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file q6lsm.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file q6voice.c +p" > /sys/kernel/debug/dynamic_debug/control; echo -n "file sm6150.c +p" > /sys/kernel/debug/dynamic_debug/control 3. 设置下边的属性: log.tag.APM_AudioPolicyManager D
当问题复现时, 请重新提供bugreport和对应的logcat文件.
同时, 也请描述下问题复现的情况, 比如跑monkey中断时出现界面无响应, crash或者重启等.
多谢!
#4 Updated by CD MM陈海波 about 2 years ago
- Assignee changed from Multimedia组-RD3_TSCD 梁卿山 to CDTS_TEST 王成
#5 Updated by Multimedia组-RD3_TSCD 梁卿山 about 2 years ago
- Status changed from ASSIGNED to NEED_INFO
#6 Updated by CDTS_Test 吴诗雨 about 2 years ago
VIN号无法追溯，客户用0100复现中
#7 Updated by CDTS_TEST 王成 about 2 years ago
- Status changed from NEED_INFO to ASSIGNED
- Assignee changed from CDTS_TEST 王成 to CD FW 曹覃刚
ftp://cdiot@192.168.87.46/Pre_figure/Test_Log/118059-118047/5_26_.7z 118047 118059为同一日志文件
#8 Updated by CDTS_TEST 王成 about 2 years ago
- Assignee changed from CD FW 曹覃刚 to CD MM陈海波
#9 Updated by CD MM陈海波 about 2 years ago
从log看, crash 从01-01 08:00:06.846开始, 当05-25 20:58:07.102中surfaceflinger挂掉后,
SystemServiceManager重启了后一切开始正常.
--------- beginning of crash
01-01 08:00:06.846 root 522 522 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 522 (init), pid 522 (init)
01-01 08:00:06.858 root 522 522 F libc : crash_dump helper failed to exec, or was killed
05-24 10:29:43.380 root 2633 2633 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 2633 (init), pid 2633 (init)
05-24 10:29:43.401 root 2633 2633 F libc : crash_dump helper failed to exec, or was killed
05-24 10:29:44.005 10062 2253 2253 E AndroidRuntime: FATAL EXCEPTION: main
05-24 10:29:44.005 10062 2253 2253 E AndroidRuntime: Process: com.qualcomm.qti.devicestatisticsservice, PID: 2253
05-24 10:29:44.005 10062 2253 2253 E AndroidRuntime: java.lang.NoClassDefFoundError: Failed resolution of: Landroid/hidl/manager/V1_0/IServiceNotification$Stub;
...
05-25 06:03:22.832 1041 4167 4167 F DEBUG : Cmdline: /vendor/bin/hw/android.hardware.audio.service
05-25 06:03:24.016 1041 4177 4177 F DEBUG : Cmdline: /system/bin/audioserver
05-25 06:31:03.500 1041 19280 19280 F DEBUG : Cmdline: /vendor/bin/hw/android.hardware.audio.service
05-25 06:31:04.809 1041 19286 19286 F DEBUG : Cmdline: /system/bin/audioserver
05-25 06:50:10.317 10068 30585 30585 F DEBUG : Cmdline: com.android.webview:webview_apk
05-25 07:59:46.447 1041 7136 7136 F DEBUG : Cmdline: /vendor/bin/hw/android.hardware.audio.service
05-25 07:59:47.556 1041 7143 7143 F DEBUG : Cmdline: /system/bin/audioserver
05-25 09:50:10.372 1041 30704 30704 F DEBUG : Cmdline: /vendor/bin/hw/android.hardware.audio.service
05-25 09:50:11.764 1041 30714 30714 F DEBUG : Cmdline: /system/bin/audioserver
05-25 09:52:24.805 1041 32027 32027 F DEBUG : Cmdline: /vendor/bin/hw/android.hardware.audio.service
05-25 09:52:25.762 1041 32053 32053 F DEBUG : Cmdline: /system/bin/audioserver
05-25 20:57:53.508 1000 1517 27438 I MicroServiceManager: requestResult(requestAudioFocus) parameters is{"functionInfo":{"IDCM_AudioFocus":"AudioFocus_Media"}}.
05-25 20:58:07.102 1000 20995 20995 F DEBUG : Cmdline: /system/bin/surfaceflinger
05-25 20:58:09.297 1000 21105 21105 I SystemServiceManager: Starting com.android.server.security.FileIntegrityService
这期间bug-report除了下边的log信息外, 没发现额外的信息.
2023-05-24 14:33:38 system_server_wtf (text, 1159 bytes)
Process: system_server/Subject: DisplayDeviceConfig/Build: HiPhi/Passe ...
2023-05-24 14:35:14 system_server_wtf (text, 1159 bytes)
Process: system_server/Subject: DisplayDeviceConfig/Build: HiPhi/Passe ...
2023-05-24 14:35:14 system_server_wtf (text, 1159 bytes)
Process: system_server/Subject: DisplayDeviceConfig/Build: HiPhi/Passe ...
...
2023-05-25 20:58:16 system_server_wtf (text, 1266 bytes)
2023-05-25 21:58:37 system_server_wtf (text, 736 bytes)
2023-05-25 21:58:52 system_server_wtf (text, 736 bytes)
..
2023-05-26 09:03:08 system_server_wtf (text, 736 bytes)
2023-05-26 09:07:49 system_server_wtf (text, 736 bytes)
2023-05-26 09:08:16 system_server_wtf (text, 736 bytes)
不知问题是否和这些log相关.
目前需要验证.
同时
/system/bin/audioserver和android.hardware.audio.service不停地重启几次.
原因就是请求的binder指定都不能得到响应. 每个线程都被堵塞住了.
#10 Updated by CD MM陈海波 about 2 years ago
- Assignee changed from CD MM陈海波 to Multimedia组-RD3_TSCD 梁卿山
#11 Updated by CDTS_TEST 王成 about 2 years ago
#12 Updated by Multimedia组-RD3_TSCD 梁卿山 about 2 years ago
Hi ALL
当前发现在5月25日7点59分时的crash中，
可以看到很多以下日志反复出现，
怀疑是audio-bsp出现问题导致android.hardware.audio.service反复crash.
000074_persist_00000_230525_075945.log
05-25 07:59:46.133 0 0 I : [77385.993563] snd_pcm_hw_constraint_integer failed 05-25 07:59:46.133 0 0 I [77385.993567] msm_pcm_open: P buffer bytes minmax constraint ret 1 05-25 07:59:46.137 0 0 I [77385.999485] afe_find_cal_topo_id_by_port: port id: 0x9000, dev_acdb_id: 0 05-25 07:59:46.137 0 0 I [77385.999490] afe_find_cal_topo_id_by_port: top_id:112fc acdb_id:15 afe_port:0x9000 05-25 07:59:46.137 0 0 I [77385.999493] afe_get_cal_topology_id: port_id = 0x9000 acdb_id = 15 topology_id = 0x112fc cal_type_index=8 ret=0 05-25 07:59:46.137 0 0 I [77385.999692] afe_send_port_topology_id: AFE set topology id 0x112fc enable for port 0x9000 ret 0 05-25 07:59:46.137 0 0 I [77385.999695] send_afe_cal_type: cal_index is 0 05-25 07:59:46.137 0 0 I [77385.999698] send_afe_cal_type: dev_acdb_id[55] is 0 05-25 07:59:46.137 0 0 I [77385.999700] send_afe_cal_type: Sending cal_index cal 0 05-25 07:59:46.138 0 0 E [77385.999702] send_afe_cal_type: No cal sent for cal_index 0, port_id = 0x9000! ret -22 05-25 07:59:46.138 0 0 I [77385.999896] afe_send_hw_delay: port_id 0x9000 rate 48000 delay_usec 474 status 0 05-25 07:59:46.139 0 0 E [77386.001494] afe_callback: cmd = 0x100e5 returned error = 0x1 05-25 07:59:46.139 0 0 E [77386.001518] afe_apr_send_pkt: DSP returned error[ADSP_EFAILED] 05-25 07:59:46.139 0 0 E [77386.001527] afe_send_cmd_port_start: AFE enable for port 0x9000 failed -131 05-25 07:59:46.139 19299 19447 E audio_hw_primary: pcm_open_prepare_helper: pcm_prepare returned -1 05-25 07:59:46.141 0 0 E : [77386.001929] msm-dai-q6-tdm soc:qcom,msm-dai-tdm-pri-rx:qcom,msm-dai-q6-tdm-pri-rx-0: msm_dai_q6_tdm_prepare: fail to open AFE port 0x9000 05-25 07:59:46.141 0 0 E : [77386.001937] msm-dai-q6-tdm soc:qcom,msm-dai-tdm-pri-rx:qcom,msm-dai-q6-tdm-pri-rx-0: ASoC: cpu DAI prepare error: -131 05-25 07:59:46.141 0 0 E [77386.001941] soc_pcm_prepare: Issue stop stream for codec_dai due to op failure -131 = ret 05-25 07:59:46.141 0 0 E [77386.002227] PRI_TDM_RX_0: ASoC: backend prepare failed -131
下一步
继续调查以上日志是否正常。
#13 Updated by Multimedia组-RD3_TSCD 梁卿山 about 2 years ago
Hi ALL
该问题经过audio-bsp的分析，
怀疑是以下通路的channel问题导致，无法正常播放，进而导致了audio 服务的crash。
05-25 07:59:46.130 19299 19447 D audio_hw_primary: enable_audio_route: apply mixer and update path: audio-ull-playback 05-25 07:59:46.130 19299 19447 D audio_route: Apply path: audio-ull-playback 05-25 07:59:46.130 19299 19447 D audio_hw_primary: select_devices: done 05-25 07:59:46.130 19299 19447 D msm8974_platform: platform_set_channel_map mixer_ctl_name:Playback Channel Map13 05-25 07:59:46.130 19299 19447 D msm8974_platform: platform_set_channel_map: set mapping(1 2 0 0 0 0 0 0) for channel:2 05-25 07:59:46.130 19299 19447 E msm8974_platform: platform_set_channel_map: Could not set ctl, error:-22 ch_count:2
下一步
1.尝试将audio-ull-playback去掉尝试会不会有该日志输出。
2.基于错误日志咨询高通，看看该问题是怎么引起的。
#14 Updated by Multimedia组-RD3_TSCD 梁卿山 about 2 years ago
HI ALL
已经提case咨询高通
case号：06653784
#15 Updated by Multimedia组-RD3_TSCD 梁卿山 about 2 years ago
Hi ALL
高通回复如下：
根据回复，出问题的地方是打开TDM端口时，出现错误；
在ULL用例中不支持通道映射。流程将继续进行并忽略这样的错误。
Hi Customer, Channel mapping is not supported on ULL use case. The flow will continue and ignore such an error. In your logs the critical error is on opening TDM port. 207 05-25 07:59:46.139 0 0 E [77386.001494] afe_callback: cmd = 0x100e5 returned error = 0x1 208 05-25 07:59:46.139 0 0 E [77386.001518] afe_apr_send_pkt: DSP returned error[ADSP_EFAILED] 209 05-25 07:59:46.139 0 0 E [77386.001527] afe_send_cmd_port_start: AFE enable for port 0x9000 failed -131 210 05-25 07:59:46.139 19299 19447 E audio_hw_primary: pcm_open_prepare_helper: pcm_prepare returned -1
下一步：
继续分析是否和system die 有关系
#16 Updated by Multimedia组-RD3_TSCD 梁卿山 about 2 years ago
HI ALL
高通回复如下：
It is unlikely the crash of audioserver is caused by this error. Because the error can be observed at 07:50:03 (I did not check further previous logs). But crash is observed until 07:59:46.
高通判断以下错误不是导致audioservice crash的原因，该问题还需要继续跟踪。
207 05-25 07:59:46.139 0 0 E [77386.001494] afe_callback: cmd = 0x100e5 returned error = 0x1 208 05-25 07:59:46.139 0 0 E [77386.001518] afe_apr_send_pkt: DSP returned error[ADSP_EFAILED] 209 05-25 07:59:46.139 0 0 E [77386.001527] afe_send_cmd_port_start: AFE enable for port 0x9000 failed -131 210 05-25 07:59:46.139 19299 19447 E audio_hw_primary: pcm_open_prepare_helper: pcm_prepare returned -1
#17 Updated by CD MM唐驭俊 about 2 years ago
分析：
bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-19-24-42-479:14730:#4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-19-24-42-479:14811:/system_ext/app/MStatsSystemService/oat/arm64/MStatsSystemService.odex: verify bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-19-24-42-479:15074:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-56-51-757:11508:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-56-51-757:11518:#4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-56-51-757:11599:/system_ext/app/MStatsSystemService/oat/arm64/MStatsSystemService.odex: verify bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-56-51-757:11862:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-19-09-05-876:11710:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-19-09-05-876:11720:#4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-19-09-05-876:11801:/system_ext/app/MStatsSystemService/oat/arm64/MStatsSystemService.odex: verify bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-19-09-05-876:12064:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-08-39-24-480:16090:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-08-39-24-480:16100:#4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-08-39-24-480:16181:/system_ext/app/MStatsSystemService/oat/arm64/MStatsSystemService.odex: verify bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-08-39-24-480:16444:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-10-59-049:11612:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-10-59-049:11622:#4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-10-59-049:11703:/system_ext/app/MStatsSystemService/oat/arm64/MStatsSystemService.odex: verify bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-24-06-10-59-049:11966:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-18-48-44-401:11571:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-18-48-44-401:11581:#4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-18-48-44-401:11662:/system_ext/app/MStatsSystemService/oat/arm64/MStatsSystemService.odex: verify bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-18-48-44-401:11925:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-17-28-57-570:10851:Cmd line: com.qti.qualcomm.mstatssystemservice bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-17-28-57-570:10861:#4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-17-28-57-570:10942:/system_ext/app/MStatsSystemService/oat/arm64/MStatsSystemService.odex: verify bugreports/bugreport-figure_0526093044/FS/data/anr/anr_2023-05-23-17-28-57-570:11205:Cmd line: com.qti.qualcomm.mstatssystemservice Cmd line: com.qti.qualcomm.mstatssystemservice Build fingerprint: 'HiPhi/PassengerDisplay_CN/PassengerDisplay:12/SKQ1.220201.001/3388:user/test-keys' ABI: 'arm64' Build type: optimized Zygote loaded classes=19571 post zygote classes=10 Dumping registered class loaders #0 dalvik.system.PathClassLoader: [], parent #1 #1 java.lang.BootClassLoader: [], no parent #2 dalvik.system.PathClassLoader: [/system/framework/tcmclient.jar], parent #0 #3 dalvik.system.PathClassLoader: [], parent #0 #4 dalvik.system.PathClassLoader: [/system_ext/app/MStatsSystemService/MStatsSystemService.apk], parent #1 Done dumping class loaders Classes initialized: 0 in 0 Intern table: 29998 strong; 1180 weak JNI: CheckJNI is off; globals=351 (plus 58 weak) Libraries: libandroid.so libaudioeffect_jni.so libcompiler_rt.so libframework-connectivity-jni.so libicu_jni.so libjavacore.so libjavacrypto.so libjnigraphics.so libmedia_jni.so libopenjdk.so libqti_performance.so librs_jni.so librtp_jni.so libsoundpool.so libstats_jni.so libwebviewchromium_loader.so (16) Heap: 92% free, 1925KB/25MB; 147075 objects
Audio service tomestone 之前SystemService已经异常，日志不足，原因不明.
01-01 08:00:06.846 root 522 522 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 522 (init), pid 522 (init)
01-01 08:00:06.858 root 522 522 F libc : crash_dump helper failed to exec, or was killed
05-24 10:29:43.380 root 2633 2633 F libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 2633 (init), pid 2633 (init)
05-24 10:29:43.401 root 2633 2633 F libc : crash_dump helper failed to exec, or was killed
"DefaultDispatcher-worker-2" daemon prio=5 tid=66 TimedWaiting
| group="main" sCount=1 ucsCount=0 flags=1 obj=0x12ec1da0 self=0xb400007540121b10
| sysTid=2633 nice=0 cgrp=default sched=0/0 handle=0x72f6126cb0
| state=S schedstat=( 2100209 26929952 106 ) utm=0 stm=0 core=0 HZ=100
| stack=0x72f6023000-0x72f6025000 stackSize=1039KB
| held mutexes=
at sun.misc.Unsafe.park(Native method)
- waiting on an unknown object
at java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:353)
at kotlinx.coroutines.scheduling.a.run(chromium-ChromePublic.apk-stable-134305015:794)
----- Waiting Channels: pid 2317 at 2023-05-24 06:56:51.759202225+0800 -----
Cmd line: com.microsoft.emmx
sysTid=2633 futex_wait_queue_me
launcher异常
05-25 06:03:22.832 1041 4167 4167 F DEBUG : Cmdline: /vendor/bin/hw/android.hardware.audio.service
05-25 06:03:22.832 1041 4167 4167 F DEBUG : pid: 801, tid: 801, name: audio.service >>> /vendor/bin/hw/android.hardware.audio.service <<<
05-25 06:03:22.832 1041 4167 4167 F DEBUG : uid: 1041
05-25 06:03:22.832 1041 4167 4167 F DEBUG : signal 35 (<debuggerd signal>), code 1 (SI_QUEUE from pid 970, uid 1041), fault addr -------
audio.service异常
05-25 06:50:10.317 10068 30585 30585 F DEBUG : Cmdline: com.android.webview:webview_apk
05-25 06:50:10.317 10068 30585 30585 F DEBUG : pid: 30471, tid: 30471, name: iew:webview_apk >>> com.android.webview:webview_apk <<<
webview异常
......
SystemService异常后发生多次Fatal signal.
05-25 20:58:13.142 21105 21105 I SystemServerTiming: StartBootPhaseSystemServicesReady
SystemService在05-25 20:58 重启完成，之后未发现audio.service tomestone。
结论：
判断audio.service tomestone 是由于SystemService异常导致（SystemService异常原因不明，日志不足,从日志看还同时导致了launcher异常）
压测：
使用106系统优化的版本压测，暂未复现该问题
压测次数:3
单次压测时间>10h
Next Action：
继续观测3个版本的后续Monkey测试结果，确认该问题是否复现。
不复现的话关闭
#18 Updated by CD TPM-王祥林 about 2 years ago
- Status changed from ASSIGNED to RESOLVED
- Resolution changed from -- to DUPLICATE
在JIRA上跟踪， 内部关闭此票。
#19 Updated by 物联网测试组_CDTS 唐霞 about 2 years ago
- Status changed from RESOLVED to VERIFIED
#20 Updated by 物联网测试组_CDTS 唐霞 about 2 years ago
- Status changed from VERIFIED to CLOSED
- Assignee changed from Multimedia组-RD3_TSCD 梁卿山 to 物联网测试组_CDTS 唐霞
在JIRA上跟踪， 内部关闭此票。