Developer Reference

Intel® Graphics for Linux* - Programmer's Reference Manuals

Download PDF
ID 772629
Date 4/12/2022
Public
Document Table of Contents
Document Table of Contents x
Programmer's Reference Manuals
Programmer's Reference Manuals x
Hardware Specifications 2023 Intel® Processors - Alchemist/Arctic Sound-M Platform 2021 Intel® Processors (Formerly Rocket Lake) 2020-2021 Intel® Processors (Formerly Tiger Lake) 2020 Intel® Processors with Intel® Hybrid Technology (Formerly Lakefield) 2020 Intel® Iris® Xe MAX GPU (formerly DG1) 2019 Intel® Processors (Formerly Ice Lake) 2018-2019 Intel® Processors (Formerly Whiskey Lake) 2017-2019 Intel® Processors (Formerly Amber Lake) 2017-2019 Intel® Processors (Formerly Coffee Lake) 2019-2020 Intel® Processors (Formerly Comet Lake) 2016 Intel® Processors (Formerly Kaby Lake) 2016 Intel® Processors (Formerly Apollo Lake and Broxton) 2015-2016 Intel® Processors (Formerly Skylake) 2014 Intel® Processors (Formerly Bay Trail) 2014-2015 Intel® Processors (Formerly Cherry Trail and Braswell) 2014-2015 Intel® Processors (Formerly Broadwell) 2013 Intel® Core™ Processor Family (Formerly Haswell) 2012 Intel® Core™ Processor Family (Formerly IvyBridge) 2011 Intel® Core™ Processor Family (Formerly SandyBridge) 2010 Intel® Core™ Processor Family (Formerly Iron Lake) Code Documentation Bugs and Debugging Intel® G45 Express Chipset Intel® 965 Express Chipset Family and Intel® G35 Express Chipset Graphics Controller Intel® Integrated Graphics Device - OpRegion Specification Archived Documentation
Code Documentation x
Source Code Repositories Build Guide GuC KMD API
Bugs and Debugging x
How to Report Bugs How to get Kernel Backtrace Learn More About GFX Bug Handling Tips that may Help to Solve your Issue in Less Timed How to Get the GPU Error State How to Dump Video BIOS (VBIOS) How to Debug Suspend-Resume Issues S3 Suspend (Suspend to RAM): S4 Hibernation (Suspend to Disk): Using Intel® Reg-Dumper
Archived Documentation x
3 - Pipes How to Set Up Dual Head for Intel® Graphics with RandR 1.2
Programmer's Reference Manuals

How to Debug Suspend-Resume Issues

The purpose of going through the steps below is to help narrow down the root cause (BIOS? Kernel? Graphics driver?) of the suspend/resume failure and provide more info for debugging.

Prerequisite: No processes using /proc/acpi/event (which might be used by, for example, gnome-power-manager, to interfere with some ACPI related actions, like pressing the power button).

  1. Get the process id by "lsof /proc/acpi/event".
  2. Kill these processes.
NOTE:
  1. Perform suspend/resume test under both text console mode (init level 3) and X mode (init level 5) to see if it's X specific. If they are with the same failure, let's focus on text console mode and just provide logs under that condition.

  2. Provide the following lofgs before and after suspend/resume:

    • dmesg output
    • intel_reg_dumper output (using reg_dump tool in xf86-video-intel source package)
    • intel_gpu_dump output (see this guide)
  3. To narrow down the issue, try removing modules before you suspend. This can help determine which module is responsible for a suspend or resume failure. For example, if you remove the b43 module and then suspend/resume works, there's likely a problem with either b43 or the wifi stack.
  4. If you remove i915 module, and suspend/resume still fails, it's likely not our drm graphics driver bug. Please file the bug at bugzilla.kernel.org,

    select the component "Power Management - Hibernation/Suspend", and CC rafael.j.wysocki@intel.com.

S3 Suspend (Suspend to RAM):

A. Check if the Resume Hang is Caused by a Graphics Driver:

  1. Run: dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after
  2. Press the power button to see if the machine can be resumed.
  3. If it can't be resumed, reboot the system then check if the file "dmesg_after" generated.
  4. If dmesg_after exists, it means that the system can be resumed from BIOS, so it's likely to be a graphics issue. Otherwise, it's not related to graphics and don't report it to freedesktop.org bugzilla.

B. Suspend/Resume by Skipping BIOS:

  1. Enable CONFIG_PM_DEBUG in kernel configuration, so that we can use /sys/power/pm_test.
  2. Run: echo core/processors/devices > /sys/power/pm_test
  3. Run: dmesg > dmesg_before; echo mem > /sys/power/state; dmesg > dmesg_after
  4. Wait for about five seconds and see whether it can be resumed correctly.
  5. If it can't be resumed correctly, it may be graphics driver bug. This information is helpful to narrow down the issue.

S4 Hibernation (Suspend to Disk):

If resume fails at kernel booting stage, try adding boot option "resume=/dev/XXXX" (XXXX means the swap partition).

Check if hibernation under console mode has the same failure as in X mode.

  1. Boot the system into init level 3 (text mode).
  2. Run: echo disk > /sys/power/state
  3. Press the power button to see if the system can be resumed correctly.
  4. If it can be resumed normally, the issue may be related to the graphics driver.
  5. If it can't be resumed normally, the issue may be related to the Linux kernel.
Parent topic: Bugs and Debugging
Level Two Title