Linux Kernel Testing and Debugging
Linux PM Sub-system Testing in Simulation Mode
The Linux PM sub-system provides five PM test modes to test hibernation in a simulated mode. These modes allow exercising the hibernation code in various layers of the kernel without actually suspending the system. This is useful when there is a concern that suspend might not work on a specific platform and help detect errors in a simulation similar to simulating flying a plane, so to speak.
- freezer - test the freezing of processes
echo freezer > /sys/power/pm_test echo platform > /sys/power/disk echo disk > /sys/power/state
- devices - test the freezing of processes and suspending of devices
echo devices > /sys/power/pm_test echo platform > /sys/power/disk echo disk > /sys/power/state
- platform - test the freezing of processes, suspending of devices and platform global control methods(*)
echo platform > /sys/power/pm_test echo platform > /sys/power/disk echo disk > /sys/power/state
- processors - test the freezing of processes, suspending of devices, platform global control methods(*) and the disabling of non-boot CPUs
echo processors > /sys/power/pm_test echo platform > /sys/power/disk echo disk > /sys/power/state
- core - test the freezing of processes, suspending of devices, platform global control methods, the disabling of non-boot CPUs and suspending of platform/system devices. Note: this mode is tested on ACPI systems.
echo core > /sys/power/pm_test echo platform > /sys/power/disk echo disk > /sys/power/state
Linux PM Sub-system Trace Events
PM sub-system supports several tracepoints and trace events that can be enabled to trigger during run-time. I will give an overview on how to enable couple of these trace events and where to find the trace information they generate:
- Enabling PM events at run-time:
cd /sys/kernel/debug/tracing/events/power echo 1 > cpu_frequency/enable cat /sys/kernel/debug/tracing/set_event less /sys/kernel/debug/tracing/trace
- Enabling events at boot-time kernel trace parameter with a kernel boot option:
For more information on Linux PM testing, please consult the Documentation/power/basic-pm-debugging.txt and other documents in the same directory.
git bisect is an invaluable and powerful tool to isolate an offending commit. I will go over very basic git bisect steps.
- This is how the process works:
git bisect start git bisect bad # Current version is bad git bisect good v3.14-rc6 # last good version
Once, one bad and one good version are specified, git bisect will start bisecting by pulling in commits between the good version and the bad. Once a set of commits are pulled in, compile the kernel, install, test, and tag the version good or bad. This process repeats until the selected commits are tested and tagged as good or bad. There can be several kernel versions to test. When the last version is tested, git bisect will flag a commit that is bad. The following useful git-bisect command can aid in using git-bisect process:
- See step by step bisect progress
git bisect log
- Reset git bisect can be used in case of mistakes in tagging, save git log output and replay prior to reset
git bisect reset
- Replay a git-bisect log
git bisect replay git_log_output
git bisect can be run on a section of kernel source tree if the problem is clearly in that area. For example, when debugging a problem in radeon driver, running git bisect on drivers/drm/radeon will limit the scope of bisect to just the commits to drivers/drm/radeon driver.
- Start git bisect on a section of a kernel tree
git bisect start drivers/drm/radeon
Shuah Khan is a Senior Linux Kernel Developer at Samsung's Open Source Group.
Getting Started with DevOps - Including New Data on IT Performance from Puppet Labs 2015 State of DevOps Report
August 27, 2015
12:00 PM CDT
DevOps represents a profound change from the way most IT departments have traditionally worked: from siloed teams and high-anxiety releases to everyone collaborating on uneventful and more frequent releases of higher-quality code. It doesn't matter how large or small an organization is, or even whether it's historically slow moving or risk averse — there are ways to adopt DevOps sanely, and get measurable results in just weeks.
Free to Linux Journal readers.Register Now!
|Secure Server Deployments in Hostile Territory, Part II||Jul 29, 2015|
|Hacking a Safe with Bash||Jul 28, 2015|
|KDE Reveals Plasma Mobile||Jul 28, 2015|
|Huge Package Overhaul for Debian and Ubuntu||Jul 23, 2015|
|diff -u: What's New in Kernel Development||Jul 22, 2015|
|Shashlik - a Tasty New Android Simulator||Jul 21, 2015|
- Hacking a Safe with Bash
- Secure Server Deployments in Hostile Territory, Part II
- Home Automation with Raspberry Pi
- Huge Package Overhaul for Debian and Ubuntu
- The Controversy Behind Canonical's Intellectual Property Policy
- KDE Reveals Plasma Mobile
- Shashlik - a Tasty New Android Simulator
- Purism Librem 13 Review
- Embed Linux in Monitoring and Control Systems
- diff -u: What's New in Kernel Development