Skip to main content
At a high level, you can categorize issues in the kernel space as kernel panic and bugs. To debug kernel-space issues, you can use the logs, command line tools, and dumps shown in the following figure: Visual representation of kernel space debugging resources, including system logs, command-line options, and memory dumps used to identify and resolve kernel-level issues.

Figure: Resources to debug issues in kernel space

  • Logs section includes dynamic debug, kernel debugging configuration, and function tracer
  • Command-line tools provide access to the /proc and debugfs file systems
  • Dumps section lists RAM dump, RAM parser, and crash utility that are used for analyzing system crashes and memory states
You can generate kernel logs using the dmesg command. To debug issues in the kernel space, it’s recommended to use the debug build. For more information about how to generate the debug build, see Qualcomm Linux metadata layers overview. For more information about kernel source configuration files, see [Qualcomm Linux Kernel Guide(https://dragonwingdocs.qualcomm.com/System/Kernel/kernel-overview). For more information about debugging Linux kernel‑space issues, see the following sections: