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.
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.
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).
Frame timings from apps running in the Borealis VM. 16 KiB.
Summarization of borealis frame timings. 2 KiB.
Contains the most recent Proton crash dump containing debug info. ~11 KiB.
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 versions of Steam compatibility tools used per game in the last 5 min. Only one line (less than 100 chars) printed per game.
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.
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.
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.
Logs printed from fwupd daemon execution.
Current state of the system as reported by fwupd daemon.
The fwupd client and daemon versions.
The kernel log from the ManaTEE hypervisor.
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.
Information about connected printer and scanner devices produced by lpstat -l -r -v -a -p -o. Produces ~22 lines of output for each device.
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.
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.
Information about LVM physical volumes.
This file records the debuggable logs generated by the secagentd daemon.
Kernel memory allocator/cache statistics. See the slabinfo(5) man page for an explanation of each field.
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.
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.
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.