0% found this document useful (0 votes)
60 views7 pages

Understanding Dumpstate Logs in Android

The document is a log file that summarizes the results of generating a bug report on an Android device. It lists the various system logs and files that were collected and the duration to collect each one. It also lists some warnings about not being able to fetch interfaces from certain Android services.

Uploaded by

Antonio Irías
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
60 views7 pages

Understanding Dumpstate Logs in Android

The document is a log file that summarizes the results of generating a bug report on an Android device. It lists the various system logs and files that were collected and the duration to collect each one. It also lists some warnings about not being able to fetch interfaces from certain Android services.

Uploaded by

Antonio Irías
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd

!

@bugreport_mode BUGREPORT_DEFAULT, and dumpstate by default


Module metadata package name: [Link]
No IDumpstateDevice AIDL implementation
Calling IDumpstateDevice implementation using path
/data/user_de/0/[Link]/files/bugreports/dumpstate_board.txt
Calling IDumpstateDevice implementation using path
/data/user_de/0/[Link]/files/bugreports/dumpstate_board.bin
Using IDumpstateDevice v1.1 HIDL HAL
Ignoring empty dumpstate_board.bin
Duration of 'DUMPSYS CRITICAL': 1.05s
*** command 'perfetto --save-for-bugreport' failed: exit code 1
Error: Tracing is not supported on user builds.
Duration of 'SYSTEM LOG': 3.63s
Duration of 'EVENT LOG': 0.29s
Duration of 'STATS LOG': 0.02s
Duration of 'RADIO LOG': 0.32s
Start thread pool:2
Duration of 'Dmabuf dump': 1.02s
Adding dir /cache/recovery (recursive: 1)
Duration of '/cache/recovery': 3.15s
Adding dir /data/misc/recovery (recursive: 1)
Adding dir /data/misc/update_engine_log (recursive: 1)
Adding dir /data/misc/logd (recursive: 0)
Adding dir /data/misc/prereboot (recursive: 0)
MOUNT INFO: 94 entries added to zip file
Duration of 'LPDUMP': 1.07s
Duration of 'DEVICE-MAPPER': 1.04s
Adding dir /metadata/ota (recursive: 1)
execvp on command 'iotop -n 1 -m 100' failed (error: No such file or directory)
*** command 'iotop -n 1 -m 100' timed out after 10.002s (killing pid 27857)
Duration of 'IOTOP': 10.00s
Duration of 'WIFI LSHAL DEBUG': 1.32s
Duration of 'FILESYSTEM DEBUG INFO.': 0.80s
Duration of 'DUMP TRACES': 48.61s
Duration of 'Wait for ': 28.41s
shutdown thread pool
Start thread pool:3
No IDumpstateDevice AIDL implementation
Calling IDumpstateDevice implementation using path
/data/user_de/0/[Link]/files/bugreports/dumpstate_board.txt
Calling IDumpstateDevice implementation using path
/data/user_de/0/[Link]/files/bugreports/dumpstate_board.bin
Using IDumpstateDevice v1.1 HIDL HAL
Ignoring empty dumpstate_board.bin
Warning: Skipping
"[Link]@2.0::ICameraService/default": cannot be
fetched from service manager (null)
Warning: Skipping
"[Link]@2.1::ICameraService/default": cannot be
fetched from service manager (null)
Warning: Skipping
"[Link]@2.2::ICameraService/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IDisplayService/default":
cannot be fetched from service manager (null)
Warning: Skipping
"[Link]@1.0::ISchedulingPolicyService/default": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@1.0::ISensorManager/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IStats/default": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@5.0::IEffectsFactory/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@5.0::IDevicesFactory/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IBluetoothHci/default": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@2.4::ICameraProvider/legacy/0":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.5::ICameraProvider/legacy/0":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.6::ICameraProvider/legacy/0":
cannot be fetched from service manager (null)
Warning: Skipping
"[Link]@1.0::ISurfaceFlingerConfigs/default": cannot be
fetched from service manager (null)
Warning: Skipping
"[Link]@1.1::ISurfaceFlingerConfigs/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IGatekeeper/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@2.1::IComposer/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.2::IComposer/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.3::IComposer/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::IHealth/default": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@2.1::IHealth/default": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@4.0::IKeymasterDevice/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@4.0::IKeymasterDevice/strongbox":
cannot be fetched from service manager (null)
Warning: Skipping "[Link].c2@1.0::IComponentStore/default": cannot
be fetched from service manager (null)
Warning: Skipping "[Link].c2@1.0::IComponentStore/software": cannot
be fetched from service manager (null)
Warning: Skipping "[Link].c2@1.1::IComponentStore/software": cannot
be fetched from service manager (null)
Warning: Skipping "[Link].c2@1.2::IComponentStore/software": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IOmx/default": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.0::IOmxStore/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IMemtrack/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IRadioConfig/default": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@1.1::IRadioConfig/default": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IRadio/slot1": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.0::IRadio/slot2": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.0::ISap/slot1": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::ISap/slot2": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.1::IRadio/slot1": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.1::IRadio/slot2": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.1::ISap/slot1": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.1::ISap/slot2": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.2::IRadio/slot1": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.2::IRadio/slot2": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.2::ISap/slot1": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.2::ISap/slot2": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.3::IRadio/slot1": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.3::IRadio/slot2": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.4::IRadio/slot1": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.4::IRadio/slot2": cannot be fetched
from service manager (null)
Warning: Skipping "[Link].secure_element@1.0::ISecureElement/eSE1":
cannot be fetched from service manager (null)
Warning: Skipping "[Link].secure_element@1.1::ISecureElement/eSE1":
cannot be fetched from service manager (null)
Warning: Skipping "[Link].secure_element@1.2::ISecureElement/eSE1":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISensors/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISoundTriggerHw/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IUsb/default": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.1::IUsb/default": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.2::IUsb/default": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.3::IUsb/default": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IAllocator/ashmem": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@1.0::IBase/ashmem": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/clearkey": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/default": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/eSE1": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/eden-drv": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/epdgd": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/epdgd2": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/imsd": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/imsd2": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/legacy/0": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/slot1": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/slot2": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/software": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/strongbox": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::IBase/widevine": cannot be fetched from
service manager (null)
Warning: Skipping "[Link]@1.0::ITokenManager/default": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@1.0::INetd/default": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.1::INetd/default": cannot be fetched
from service manager (null)
Warning: Skipping "[Link]@1.0::IKeystore/default": cannot be
fetched from service manager (null)
Warning: Skipping
"[Link]@1.0::ISehUcmKeystore/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@1.0::ISehDevicesFactory/default":
cannot be fetched from service manager (null)
Warning: Skipping
"[Link]@1.0::ISehAuthenticationFramework/default": cannot
be fetched from service manager (null)
Warning: Skipping
"[Link].a2dp@1.0::ISehBluetoothAudioOffload/default":
cannot be fetched from service manager (null)
Warning: Skipping
"[Link].a2dpsink@1.0::ISehBluetoothA2dpSinkProvidersFact
ory/default": cannot be fetched from service manager (null)
Warning: Skipping
"[Link]@2.0::ISehBluetoothAudioProvidersFactory/
default": cannot be fetched from service manager (null)
Warning: Skipping
"[Link]@2.1::ISehBluetoothAudioProvidersFactory/
default": cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehBluetooth/default":
cannot be fetched from service manager (null)
Warning: Skipping
"[Link]@4.0::ISehCameraProvider/legacy/0": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehHealth/default": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehMiscPower/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehBridge/slot1":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehBridge/slot2":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehChannel/epdgd":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehChannel/epdgd2":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehChannel/imsd":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehChannel/imsd2":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehRadio/slot1": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@2.0::ISehRadio/slot2": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@2.1::ISehRadio/slot1": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@2.1::ISehRadio/slot2": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@2.2::ISehRadio/slot1": cannot be
fetched from service manager (null)
Warning: Skipping "[Link]@2.2::ISehRadio/slot2": cannot be
fetched from service manager (null)
Warning: Skipping
"[Link]@1.0::ISehEngmode/default": cannot be
fetched from service manager (null)
Warning: Skipping
"[Link]@2.0::ISehVaultKeeper/default": cannot
be fetched from service manager (null)
Warning: Skipping "[Link]@1.0::ISehSysInputDev/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@1.1::ISehSysInputDev/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@1.2::ISehSysInputDev/default":
cannot be fetched from service manager (null)
Warning: Skipping "[Link]@1.3::ISehSysInputDev/default":
cannot be fetched from service manager (null)
Warning: Skipping
"vendor.samsung_slsi.hardware.ExynosA2DPOffload@3.0::IExynosA2DPOffload/default":
cannot be fetched from service manager (null)
Warning: Skipping
"vendor.samsung_slsi.[Link]@1.0::IExynosHWCServiceTW/default":
cannot be fetched from service manager (null)
Warning: Skipping
"vendor.samsung_slsi.[Link]@1.0::IExynosHWCConfigs/default": cannot
be fetched from service manager (null)
Warning: Skipping
"vendor.samsung_slsi.hardware.eden_runtime@1.0::IEdenruntime/default": cannot be
fetched from service manager (null)
Warning: Skipping "vendor.samsung_slsi.[Link]@1.0::IEpicRequest/default":
cannot be fetched from service manager (null)
Warning: Skipping
"vendor.samsung_slsi.[Link]@1.0::IGeoTransService/default":
cannot be fetched from service manager (null)
Warning: Skipping "vendor.samsung_slsi.[Link]@2.0::IOfiService/default":
cannot be fetched from service manager (null)
Warning: Skipping "vendor.samsung_slsi.[Link]@2.1::IOfiService/default":
cannot be fetched from service manager (null)
*** command 'lshal --all --types=all' failed: exit code 136
Duration of 'HARDWARE HALS': 1.29s
Duration of 'DUMP HALS': 1.38s
section 1000 status 1
section 1000 status 2
section 1002 status 1
section 1002 status 2
section 1109 status 1
section 1109 status 2
section 1110 status 1
section 1110 status 2
section 1111 status 1
section 1111 status 2
section 1112 status 1
section 1112 status 2
section 1113 status 1
section 1113 status 2
section 1114 status 1
section 1114 status 2
section 1115 status 1
section 1115 status 2
section 2001 status 1
section 2001 status 2
section 2002 status 1
section 2002 status 2
section 2003 status 1
Duration of 'CPU INFO': 2.40s
Duration of 'PROCESSES AND THREADS': 1.52s
section 2003 status 2
section 2004 status 1
section 2004 status 2
section 2005 status 1
ls: epdgcr: Permission denied
ls: netstats: Permission denied
ls: wdata: Permission denied
ls: wifi: Permission denied
*** command 'ls -a -l -R /data/log/' failed: exit code 1
AddAnrTraceDir(): dump_traces_file=/data/log/dumptrace_ABNu2g,
anr_traces_dir=/data/anr
Dumping current ANR traces (/data/log/dumptrace_ABNu2g) to the main bugreport entry
section 2005 status 2
section 2006 status 1
section 2006 status 2
section 2007 status 1
section 2007 status 2
Duration of 'INCIDENT REPORT': 4.10s
Duration of 'OLOG': 1.23s
Duration of 'DUMP CHECKINS': 1.68s
Duration of 'VISIBLE WINDOW VIEWS': 1.36s
Adjusting max progress from 5000 to 5507
Adjusting max progress from 5507 to 6068
Adjusting max progress from 6068 to 6684
Adjusting max progress from 6684 to 7355
Adjusting max progress from 7355 to 8092
Adjusting max progress from 8092 to 8906
Duration of 'for_each_tid(BLOCKED PROCESS WAIT-CHANNELS)': 1.07s
Adding dir /data/misc/nfc/logs (recursive: 1)
Adjusting max progress from 8906 to 9797
Adding dir /data/misc/snapshotctl_log (recursive: 0)
Adding dir /data/log/bt (recursive: 1)
Duration of 'APP SERVICES PLATFORM': 1.06s
Duration of 'APP SERVICES NON-PLATFORM': 5.80s
Duration of 'APP PROVIDERS PLATFORM': 0.79s
Duration of 'APP PROVIDERS NON-PLATFORM': 22.90s
Duration of 'DUMPSYS HIGH': 43.32s
Duration of 'DUMPSYS HIGH': 43.32s
Duration of 'APP PROVIDERS SEC_MEDIA': 1.47s
Adjusting max progress from 9797 to 10805
Error with service
'[Link]/default' while dumping:
FAILED_TRANSACTION
Error with service '[Link]/default' while dumping:
FAILED_TRANSACTION
Error with service '[Link]/secsnap' while dumping:
FAILED_TRANSACTION
Can't find service: vold
Duration of 'DUMPSYS NORMAL': 89.70s
Duration of 'DUMPSYS NORMAL': 89.89s
Duration of 'Wait for ': 44.99s
Adding dir /linkerconfig (recursive: 1)
Adding frozen processes from /sys/fs/cgroup
Duration of 'DUMPSTATE': 90.45s
Duration of 'Total Dumpstate': 143.98s
open(/data/user_de/0/[Link]/files/bugreports/dumpstate_board.txt): No
such file or directory
Failed to unlink file
(/data/user_de/0/[Link]/files/bugreports/dumpstate_board.txt): No such
file or directory
Adding main entry ([Link]) from
/data/user_de/0/[Link]/files/bugreports/[Link] to .zip bugreport
dumpstate id 2 finished around 2023/05/06 [Link] (147 s)
Adding zip text entry main_entry.txt
dumpstate_log.txt entry on zip file logged up to here

Removing temporary file


/data/user_de/0/[Link]/files/bugreports/[Link]
Going to copy file
(/data/user_de/0/[Link]/files/bugreports/[Link]) to 7
Final progress: 10290/10805 (estimated 5000)
Saving stats (total=10290, runs=1, average=10290) on /bugreports/dumpstate-
[Link]
done (id 2)

Common questions

Powered by AI

The dependency of hardware interfaces on the service manager, as evidenced by warnings about interfaces being skipped because they 'cannot be fetched from service manager (null)' , indicates that any failure in the service manager can hinder the ability to access these interfaces. This may impede the debugging process by constraining the operational data available from these interfaces from being used in diagnostics, potentially delaying problem resolution .

Omissions of services like IStats and ISensorManager during bug reporting—where these services cannot be fetched—can lead to missing data that is crucial for understanding performance metrics and sensor data integrations within the system . Such omissions would likely hinder comprehensive system analysis, reducing the ability to identify performance bottlenecks or specific hardware interaction failures, ultimately compromising the diagnostics efficacy .

The failure of the 'lshal' command, indicated by an 'exit code 136', impacts hardware abstraction layer debugging by potentially halting the acquisition of detailed hardware layer insights, which are crucial for identifying misconfigurations or hardware failures . Mitigating this issue could involve ensuring correct permissions for execution, troubleshooting the cause of the failure such as checking for missing binaries, or using alternative commands that can perform similar tasks if 'lshal' continues to fail .

The time distribution in the bug report generation process shows a high duration for tasks like 'DUMP TRACES' (48.61s) and 'DUMPSYS NORMAL' (89.70s). This indicates a significant computational load and implies that comprehensive data gathering and analysis are resource-intensive tasks, requiring substantial processing power and time, reflecting on the overall complexity of capturing a complete system state effectively during bug reporting .

The challenges encountered include numerous services that cannot be fetched from the service manager, as repeatedly indicated by warnings such as 'cannot be fetched from service manager (null)' for various services like ICameraService, IDisplayService, ISensorManager, etc. . This signifies a potential lack of visibility into the current status of several hardware components and services, which can have implications for system diagnostics by limiting the ability to derive insights from these components, potentially affecting the identification and resolution of system issues .

When 'PERFETTO' commands fail, as seen with error messages like 'exit code 1', considerations should include checking build configurations for tracing support, ensuring the tool is correctly installed and configured, and verifying that all necessary system dependencies are present and functional . Additionally, reviewing alternative methods for performance analysis or tracing that conform to the constraints of the system's security framework may be beneficial .

The system’s adjustments to 'max progress' values, as seen with increases from 5000 to 10805 , suggest dynamic prioritization mechanisms at play that adjust based on real-time analysis of the reporting load and sequence dependencies. These adjustments imply that the system actively manages its reporting tasks, potentially prioritizing completion and accuracy over static progress targets. These mechanisms ensure that comprehensive data gathering continues smoothly even as new tasks emerge or durations extend beyond initial estimates .

The execution failures include errors such as 'Tracing is not supported on user builds' and command failures like 'iotop' due to missing directories, shown in error messages like 'No such file or directory' . These failures suggest a lacking environment for executing certain debugging or monitoring tools, which could severely impact comprehensive system monitoring by preventing data collection from these tools .

Commands like 'perfetto' failing with errors like 'Tracing is not supported on user builds' suggests restrictions imposed by user build configurations which do not permit certain kernel or user-space tracing features . Ensuring successful execution could involve switching to developer or engineering builds where such limitations are less rigid, or alternatively, adjusting configurations in the existing build to permit execution where security allows .

The execution failure of 'iotop', possibly due to directory issues like 'No such file or directory', disrupts the ability to monitor real-time I/O usage by processes, a vital aspect for performance diagnostics . This affects system diagnostics by potentially leading to an incomplete understanding of resource usage patterns, thereby obscuring insights into system bottlenecks or inefficiencies that could impact overall performance .

You might also like