Collect PCIe link statistics in dumpstate.
DO NOT MERGE because the same functionality is already
implemented in dump_pcie.sh in upstream branches.
Test: adb bugreport && unzip bugreport*.zip &&
grep link_stats dumpstate_board.txt
Bug: 266561593
Change-Id: I5b530b68f8c8cd6ed2bc5016d5aef55c3caafbd8
Signed-off-by: Doug Zobel <zobel@google.com>
Bug: 240346564
Test: Build for Cheetah device with user build,
check bugreport for decon_counters content
Merged-In: I0026378d81f5de5ac48b658861a2d8a85c817820
Change-Id: Ia20e1e985d3d83b58e4dce28d7537b49b545e243
Signed-off-by: Taylor Nelms <tknelms@google.com>
Add logbuffer_dual_batt to dumpstate.
Also fix some dual batt related dump pathes.
Bug: 263496320
Test: build pass, no related permission errors.
Change-Id: Ibfd3dfc18acc049052f07246c8d85ae04b4f95f5
Signed-off-by: Wasb Liu <wasbliu@google.com>
Bug: 254201934
Test: The BR has the data of "Golden Mutual Raw Data.
Signed-off-by: Mason Wang <masonwang@google.com>
Change-Id: I017462d0cd6f2ed3032f0f775d078ef3f5790193
Modify the logging mask file path to instead point to the new history
directory, as well as include more files (right now only logging mask
history and logging enabled history).
Bug: 259174982
Test: Manually build and inspect bugreport to make sure files are
included
Change-Id: Id87f381a4895399a035ea4fe55d132e31d5d796c
Merged-In: Id87f381a4895399a035ea4fe55d132e31d5d796c
At the bugreport, capture long irq metrics and resume latency metrics
Bug: 227809911
Bug: 232541623
Test: "adb bugreport" includes metrics capture.
Signed-off-by: Ziyi Cui <ziyic@google.com>
Change-Id: I8dc3330da3b9274be24534b52db86f0b3d01a482
Bug: 241739027
Test: trigger bugreport with `adb bugreport` and inspect the
logs to to make sure it is copying over LoggingMaskHistory and
including it in the tar file at the end.
Change-Id: I93ad2655193c57a0782c1535dc1cde3d0db1aeec
At the bugreport, capture pixel tracee vents. It's useful to know
what happened in kernel side at that time.
Test: "adb bugreport" includes the pixel trace dump.
Bug: 238728493
Change-Id: I43a0b0bc51fc9aae7149e461761b798da9fce5e8
Signed-off-by: Minchan Kim <minchan@google.com>
Since design was adjusted, we are no longer need
to cat dump_start when bugreport be triggered.
Bug: 256746618
Test: Trigger bugreport and check debug files.
Change-Id: I1c381a1e0a9bd0611b804c3dd9364eb48e8d4e49
Signed-off-by: Roger Wang <wangroger@google.com>
USF saves a stat buffer to the filesystem periodically. Dump this as
part of bugreports.
Bug: 242320914
Test: Stats are visible in a bugreport.
Change-Id: I2020f48026fcad19e41c8959e404e0a0783a2ef0
Dump the touch information and rawdata when bugreport is triggered.
Bug: 214118904
Test: adb bugreport
Change-Id: I08834cf0176be69359264189b703486e33925f2b
Signed-off-by: Wendly Li <wendlyli@google.com>
thismeal.txt captures the ODPM breakdown when mitigation interrupt
occurs. This can help understand the power breakdown when interrupt
happens.
Bug: 238435115
Test: Bugreport contains the thismeal.txt once mitigation interrupt
triggers.
Signed-off-by: George Lee <geolee@google.com>
Change-Id: I5dcfbaae9832b4e0c50293d0cc45d4b40ac9da7f
At bugreport, dump cma information, which is useful for CMA
memory leak.
Bug: 233535442
Test: adb bugreport contains cma information in dumpstate_board.txt
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: I37aa901b0376d5187c18c73422e9fa56bfd0d6bc
Mitigation Logger logs battery related information for 1 second when it
is triggered by under voltage or over current interrupts. Information
collected is to help debug system brownout. This change is to enable
bugreport reading out the mitigation log.
Bug: 228383769
Test: Boot and Test
Signed-off-by: George Lee <geolee@google.com>
Change-Id: Ia735e46fc1b86b1971e8838d43f8733c73793ef8
Change konb name to "buffer"
Bug: 230651222
Test: check dumpstate_board.txt from adb bugreport
Signed-off-by: Minchan Kim <minchan@google.com>
Change-Id: I80674d8728bab322ae2acdb3a8cd0ffaff39c977
The duration of dumpstate board binary is only 45s.
Change the log compression timeout from 120s to 20s.
Bug: 229932116
Change-Id: I4f3ebe0c89db50a3ad7071fe730585a391f7ac81
lshal is not supported for AIDL, now use dumpsys instead.
Update the debug command as below.
Old: lshal debug android.hardware.dumpstate@1.1::IDumpstateDevice/default [section]
New: dumpsys android.hardware.dumpstate.IDumpstateDevice/default [section]
Currently dumpsys does not start the Lazy HAL service, only dumpstate does.
Because we need to run dumpsys for debugging, keep the dumpstate HAL running at boot.
Do not set it to be a lazy HAL.
Test: atest VtsHalDumpstateTargetTest pass
adb shell dumpsys -t 30 android.hardware.dumpstate.IDumpstateDevice/default all
Bug: 223118410
Change-Id: I7f866a57c3eff8c9783fee89dce205cf9728c459
2022-04-15 17:00:31 +08:00
Renamed from dumpstate/DumpstateDevice.cpp (Browse further)
