This document describes what the log entries mean. Each entry has a matching section. Please add a section here for new entries and some brief description of what it means and how to parse it.
Disk I/O stats for all block devices on the system.
Value of the SMU idlemask
Contains the time when the system last entered/exited S0ix and how long it remained in that state.
Contains additional timing information about the last S0ix suspend including how long it took to enter and exit that state.
Base64 encoded contents of the smart trace buffer, contains timestamped POST codes and logs from various other systems. Requires an AMD specific tool to decode.
Gets ARC app disk usage and includes SELinux context for /data files. This should be empty on virtio-blk devices.
Dumps kernel logs using vm_pstore_dump tool. The log is stored in pstore in the guest which is a file on the host side, similar to console-ramoops. Should show kernel logs when all else fails inside the guest OS. Timestamp is in seconds from guest Linux kernel boot.
Memory PSI of ARCVM that comes from /proc/pressure/memory. Memory PSI code
Zram activity of ARCVM which is the output of /sys/block/zram0/mm_stat.
Zram activity of ARCVM which is the output of /sys/block/zram0/stat.
Recent events in audit.log as generated by auditd(8). Only includes audit events of type=SYSCALL and type=AVC (SELinux denials).
Contains which TPM commands are used and its response when the command failed.
Log entries stored in console section of coreboot memory region. Contains logs from things such as coreboot and depthcarge before Linux kernel starts.
Same as bios_times, but in flame graph compatible stacked format and with enum names instead of human-readable descriptions.
This entry contains timestamps of events saved by BIOS and its components. Timestamps are in human-readable form with description and value.
This file records the debuggable logs generated by Bluetooth daemons ($syslogseverity < ‘7’), including logs from bluetoothd, btmanagerd, and btadapterd.
Logs from the Borealis VM's output (kernel logs to serial, in-VM services).
Logs from Borealis attempts to install shader cache DLCs when fossilize is called within the VM.
Frame timings from apps running in the Borealis VM. 16 KiB.
Summarization of borealis frame timings. 2 KiB.
Logs from Borealis game launches, including command line and compat tools used for the game launch.
Contains the most recent Proton crash dump containing debug info. ~11 KiB.
Contains both system-provided and user-specified configs which control the behaviour of Borealis system components (initially just Sommelier) on a per-game basis. For example, a setting might permit a specific game to control the position of its windows on-screen.
~93 bytes per setting. We print the first 10 KiB, enough for 110 settings.
Contains MD5 digests for paths in the Borealis read-only rootfs. This report may inform if the Borealis rootfs has become corrupted. ~44 KiB.
Contains the stdout and stderr of the Steam client and any games run since Borealis boot. ~8 KiB for start up and login of the Steam client. Each game launch adds ~8 KiB.
If the Borealis VM is running, displays a list of all Borealis windows and each window's title, size, and other X properties, as seen by the X server. Expected size is ~20 KiB.
Various virtual memory fragmentation details. See the /proc/buddyinfo section of the proc(5) man page for an explanation of each field.
Contains logs from Linux kernel from previous boot, in pstore ramoops logger.
Various CPU & system architecture details. Often shows exact CPU models and supported hardware flags, as well as how many CPUs and cores that are available. See the /proc/cpuinfo section of the proc(5) man page for more details.
UEFI boot log for ChromeOS Flex.
Disk I/O stats for block devices assigned to the stateful partition, user home, and root.
USB-C state returned by the ectool typecstatus and typecdiscovery commands. This includes the power role, data role, polarity, mux information, source/sink capabilities and the SOP/SOP' identity/mode responses if available.
FPMCU Panic Data in human readable form.
The output of crosid -v, which can be used to understand/debug why a device matched a certain config identity (or, why a device didn't match one).
Logs from the Termina VM's output (kernel logs to serial, in-VM services).
Logs collected from the ‘display_debug’ crosh tool, such as annotated drm_trace logs and snapshots of the output of ‘modetest’. The drm_trace logs are as described below, but with additional categories enabled. See http://go/cros-displaydebug for more details.
Linux kernel logs from the current run. See console-ramoops for previous boot.
Logs collected from the kernel's drm module. A subset of drm_debug_category messages are enabled and the tail of their output is collected here.
Same as above, but for older kernel versions using a legacy drm_trace implementation.
Shows system events such as when a device was turned on or off, and if a reboot was user-initiated. Comes from persistent firmware event log.
Logs collected from extension acting as system extensions (managing login and sessions).
The number of files opened on the system. Useful when trying to check if it's the system-wide limit or the per-process limit when failing to open new file descriptors.
https://docs.kernel.org/admin-guide/sysctl/fs.html#file-max-file-nr
The folder_size_dump helper dumps the actual disk usage (in bytes) of various system folders by calling du --human-readable --total --summarize --one-file-system. The list of folders and filtering can be found in folder_size_dump.cc. Each entry calls du individually with a sorted list of subfolders.
The output of the df command is available separately for comparison.
0 sized entries are filtered out to reduce the size of the report, this does not provide a complete folder contents listing.
The folder_size_dump helper dumps the actual disk usage (in bytes) of top level user directories du --human-readable --total --summarize --one-file-system. The output of the df command is available separately for comparison.
Logs printed from fwupd daemon execution.
Current state of the system as reported by fwupd daemon.
The fwupd client and daemon versions.
The Google Security Chip console log.
The internal state of the hwsec daemons.
The kernel log from the ManaTEE hypervisor.
Return a (compressed) binary i915_error_state.
Return a (compressed) human readable i915_error_state decoded using aubinator_error_decode.
Per-CPU interrupt statistics. See the /proc/interrupts section of the proc(5) man page for an explanation of each field.
Information about an MCU controlling an RGB keyboard, including FW version.
Console output of an MCU controlling an RGB keyboard.
Application level logs collected from kiosk apps including logs from browser windows, service workers and secondary extensions.
kiosk_apps.1.log file which stores a day older kiosk application level logs from different sources like browser windows, service workers and app windows.
Log (adb logcat) from Android instance in ARC. Note that timestamp timezone is in local time unlike other logs which are mostly in UTC.
TODO(b/180562941): Migrate to UTC.
Information about connected printer and scanner devices produced by lpstat -l -r -v -a -p -o. Produces ~22 lines of output for each device.
Lists PCI devices. Contains output for lspci.
Lists USB devices. Contains output for lsusb and lsusb -t for topology.
Verbose output of the lsusb tool. Provides more detailed information including decoded common descriptors of all currently enumerated USB devices.
Latency Tolerance Reporting value of each external components in the Intel PCH (Platform Controller Hub).
Information about LVM logical volumes.
Various memory usage statistics. See the /proc/meminfo section of the proc(5) man page for an explanation of each field.
Error counters of MMC controllers. Each counter represents the number of fatal error events that occurred since boot. Error types include CRC mismatches and transfer timeouts.
File system mount information from the init process's mount namespace. See https://www.kernel.org/doc/html/latest/filesystems/sharedsubtree.html for what it means.
Details of Network Based Recovery (NBR) process.
Details of update engine progress during Network Based Recovery (NBR).
Upstart details from Network Based Recovery (NBR).
Each of Package Cstate residencies timer count value.
Whether the Intel proprietary components within the Intel PCH (Platform Controller Hub) is power gated.
Performance profiling information about how much time the system spends on various activities (program execution stack traces). The full detail of can be found in the Profile protocol buffer message type. This field is xz-compressed and base64-encoded.
A trace timeline of system and kernel performance events. The data is formatted as a Perfetto trace protocol buffer message and can be viewed with the Perfetto UI. This field is zstd-compressed and base64-encoded.
For use mostly on chromebox debugging, displays which keyboards/mice system services are tracking and considering as ‘primary’ to the device.
Memory PSI of host, output of /proc/pressure/memory. Memory PSI code
Information about LVM physical volumes.
This file records the debuggable logs generated by the secagentd daemon.
Return the feature level calculated for this device. It is produced by the segmentation library, retrieved by the feature_check command.
Return the scope level for this device. It is produced by the segmentation library, retrieved by the feature_check command.
Kernel memory allocator/cache statistics. See the slabinfo(5) man page for an explanation of each field.
Lists the quota disk usage information for all users, groups and projects for the /home directory.
The Modern Standby (S0ix) is one state of ACPI. Also called “S0 idle low power mode”. Modern Standby (S0ix) and Intel S0ix Sub-states are triggered when specific conditions within the SoC have been achieved. Show the status of the low power mode requirements at the time of reading.
Display the required power state for various IP blocks to enter a given power state, and whether or not that was achieved.
Each of Intel S0ix Sub-states residencies timer count.
Show the status of Modern Standby (S0ix) and Intel S0ix Sub-states requirements. They are latched on every Package Cstate 10 entry & exit and Intel S0ix Sub-states entry & exit as well
Shows the stats for the top I/O intensive threads, including the thread and process IDs, the associated command name, and the number of bytes read and written.
Information about the state of USB Type-C ports, partners and cables from the USB Type-C connector class.
Short summary of the current system information from the uname(1) command. It will include the Linux kernel version (including the git commit), when the kernel was compiled, and some details for the system's CPU.
Logs from update_engine. Useful to know what version the system upgraded to and from and when. Shows lsb-release inside the old and new rootfs when updating.
The current system uptime(1) in seconds, including time spent in suspend. In other words, how long since the system was booted.
Dumps the size of all folders inside the primary user's folder and the size of all daemon stores for all mounted users.
The previous vmlog; see vmlog.LATEST.
The previous vmlog; see vmlog.LATEST.
virtual memory related log written by vmlog_writer, documented here.
The previous vmlog; see vmlog.LATEST.
Various virtual memory statistics. See the /proc/vmstat section of the proc(5) man page for an explanation of each field.
Wakeup sources are devices capable of waking the system from a suspend. Contains various stats about each wakeup source. See struct wakeup_source in include/linux/pm_wakeup.h in the kernel for a description of fields in this file.
Useful for debugging suspend issues.
block I/O statistics for zram, space-delimited, documented at https://www.kernel.org/doc/html/latest/block/stat.html
Useful to know how many I/O happened and how much time was spent using zram swap.
Memory management related statistics for zram from /sys/block/zram0/, Documented at https://www.kernel.org/doc/html/latest/admin-guide/blockdev/zram.html#stats
Useful to know how much memory is being stored compressed in zram.