€•Ÿ      Œsphinx.addnodes”Œdocument”“”)”}”(Œ	rawsource”Œ ”Œchildren”]”(Œtranslations”ŒLanguagesNode”“”)”}”(hhh]”(h Œpending_xref”“”)”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…””}”Œparent”hsbaŒ
attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ	refdomain”Œstd”Œreftype”Œdoc”Œ	reftarget”Œ,/translations/zh_CN/power/basic-pm-debugging”Œmodname”NŒ	classname”NŒrefexplicit”ˆuŒtagname”hhhubh)”}”(hhh]”hŒChinese (Traditional)”…””}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ,/translations/zh_TW/power/basic-pm-debugging”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒItalian”…””}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ,/translations/it_IT/power/basic-pm-debugging”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒJapanese”…””}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ,/translations/ja_JP/power/basic-pm-debugging”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒKorean”…””}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ,/translations/ko_KR/power/basic-pm-debugging”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubh)”}”(hhh]”hŒSpanish”…””}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ	refdomain”h)Œreftype”h+Œ	reftarget”Œ,/translations/sp_SP/power/basic-pm-debugging”Œmodname”NŒ	classname”NŒrefexplicit”ˆuh1hhhubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h
hhŒ	_document”hŒsource”NŒline”NubhŒsection”“”)”}”(hhh]”(hŒtitle”“”)”}”(hŒ!Debugging hibernation and suspend”h]”hŒ!Debugging hibernation and suspend”…””}”(hh¨hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hh£hžhhŸŒF/var/lib/git/docbuild/linux/Documentation/power/basic-pm-debugging.rst”h KubhŒblock_quote”“”)”}”(hŒ.(C) 2007 Rafael J. Wysocki <rjw@sisk.pl>, GPL
”h]”hŒenumerated_list”“”)”}”(hhh]”hŒ	list_item”“”)”}”(hŒ*2007 Rafael J. Wysocki <rjw@sisk.pl>, GPL
”h]”hŒ	paragraph”“”)”}”(hŒ)2007 Rafael J. Wysocki <rjw@sisk.pl>, GPL”h]”(hŒ2007 Rafael J. Wysocki <”…””}”(hhÊhžhhŸNh NubhŒ	reference”“”)”}”(hŒrjw@sisk.pl”h]”hŒrjw@sisk.pl”…””}”(hhÔhžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”Œmailto:rjw@sisk.pl”uh1hÒhhÊubhŒ>, GPL”…””}”(hhÊhžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KhhÄubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhh¿ubah}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œ
upperalpha”Œprefix”Œ(”Œsuffix”Œ)”Œstart”Kuh1h½hh¹ubah}”(h]”h ]”h"]”h$]”h&]”uh1h·hŸh¶h Khh£hžhubh¢)”}”(hhh]”(h§)”}”(hŒ31. Testing hibernation (aka suspend to disk or STD)”h]”hŒ31. Testing hibernation (aka suspend to disk or STD)”…””}”(hj
  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj  hžhhŸh¶h KubhÉ)”}”(hŒNTo check if hibernation works, you can try to hibernate in the "reboot" mode::”h]”hŒQTo check if hibernation works, you can try to hibernate in the â€œrebootâ€ mode:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K
hj  hžhubhŒliteral_block”“”)”}”(hŒ># echo reboot > /sys/power/disk
# echo disk > /sys/power/state”h]”hŒ># echo reboot > /sys/power/disk
# echo disk > /sys/power/state”…””}”hj(  sbah}”(h]”h ]”h"]”h$]”h&]”Œ	xml:space”Œpreserve”uh1j&  hŸh¶h Khj  hžhubhÉ)”}”(hX¿  and the system should create a hibernation image, reboot, resume and get back to
the command prompt where you have started the transition.  If that happens,
hibernation is most likely to work correctly.  Still, you need to repeat the
test at least a couple of times in a row for confidence.  [This is necessary,
because some problems only show up on a second attempt at suspending and
resuming the system.]  Moreover, hibernating in the "reboot" and "shutdown"
modes causes the PM core to skip some platform-related callbacks which on ACPI
systems might be necessary to make hibernation work.  Thus, if your machine
fails to hibernate or resume in the "reboot" mode, you should try the
"platform" mode::”h]”hXÎ  and the system should create a hibernation image, reboot, resume and get back to
the command prompt where you have started the transition.  If that happens,
hibernation is most likely to work correctly.  Still, you need to repeat the
test at least a couple of times in a row for confidence.  [This is necessary,
because some problems only show up on a second attempt at suspending and
resuming the system.]  Moreover, hibernating in the â€œrebootâ€ and â€œshutdownâ€
modes causes the PM core to skip some platform-related callbacks which on ACPI
systems might be necessary to make hibernation work.  Thus, if your machine
fails to hibernate or resume in the â€œrebootâ€ mode, you should try the
â€œplatformâ€ mode:”…””}”(hj8  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khj  hžhubj'  )”}”(hŒ@# echo platform > /sys/power/disk
# echo disk > /sys/power/state”h]”hŒ@# echo platform > /sys/power/disk
# echo disk > /sys/power/state”…””}”hjF  sbah}”(h]”h ]”h"]”h$]”h&]”j6  j7  uh1j&  hŸh¶h Khj  hžhubhÉ)”}”(hŒ9which is the default and recommended mode of hibernation.”h]”hŒ9which is the default and recommended mode of hibernation.”…””}”(hjT  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khj  hžhubhÉ)”}”(hŒ¢Unfortunately, the "platform" mode of hibernation does not work on some systems
with broken BIOSes.  In such cases the "shutdown" mode of hibernation might
work::”h]”hŒ©Unfortunately, the â€œplatformâ€ mode of hibernation does not work on some systems
with broken BIOSes.  In such cases the â€œshutdownâ€ mode of hibernation might
work:”…””}”(hjb  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khj  hžhubj'  )”}”(hŒ@# echo shutdown > /sys/power/disk
# echo disk > /sys/power/state”h]”hŒ@# echo shutdown > /sys/power/disk
# echo disk > /sys/power/state”…””}”hjp  sbah}”(h]”h ]”h"]”h$]”h&]”j6  j7  uh1j&  hŸh¶h K#hj  hžhubhÉ)”}”(hŒn(it is similar to the "reboot" mode, but it requires you to press the power
button to make the system resume).”h]”hŒr(it is similar to the â€œrebootâ€ mode, but it requires you to press the power
button to make the system resume).”…””}”(hj~  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K&hj  hžhubhÉ)”}”(hŒgIf neither "platform" nor "shutdown" hibernation mode works, you will need to
identify what goes wrong.”h]”hŒoIf neither â€œplatformâ€ nor â€œshutdownâ€ hibernation mode works, you will need to
identify what goes wrong.”…””}”(hjŒ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K)hj  hžhubh¢)”}”(hhh]”(h§)”}”(hŒa) Test modes of hibernation”h]”hŒa) Test modes of hibernation”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjš  hžhhŸh¶h K-ubhÉ)”}”(hX'  To find out why hibernation fails on your system, you can use a special testing
facility available if the kernel is compiled with CONFIG_PM_DEBUG set.  Then,
there is the file /sys/power/pm_test that can be used to make the hibernation
core run in a test mode.  There are 5 test modes available:”h]”hX'  To find out why hibernation fails on your system, you can use a special testing
facility available if the kernel is compiled with CONFIG_PM_DEBUG set.  Then,
there is the file /sys/power/pm_test that can be used to make the hibernation
core run in a test mode.  There are 5 test modes available:”…””}”(hj«  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K/hjš  hžhubhŒdefinition_list”“”)”}”(hhh]”(hŒdefinition_list_item”“”)”}”(hŒ)freezer
- test the freezing of processes
”h]”(hŒterm”“”)”}”(hŒfreezer”h]”hŒfreezer”…””}”(hjÆ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÄ  hŸh¶h K5hjÀ  ubhŒ
definition”“”)”}”(hhh]”hŒbullet_list”“”)”}”(hhh]”hÃ)”}”(hŒtest the freezing of processes
”h]”hÉ)”}”(hŒtest the freezing of processes”h]”hŒtest the freezing of processes”…””}”(hjâ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K5hjÞ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhjÛ  ubah}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jÙ  hŸh¶h K5hjÖ  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÔ  hjÀ  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¾  hŸh¶h K5hj»  ubj¿  )”}”(hŒCdevices
- test the freezing of processes and suspending of devices
”h]”(jÅ  )”}”(hŒdevices”h]”hŒdevices”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÄ  hŸh¶h K8hj
  ubjÕ  )”}”(hhh]”jÚ  )”}”(hhh]”hÃ)”}”(hŒ9test the freezing of processes and suspending of devices
”h]”hÉ)”}”(hŒ8test the freezing of processes and suspending of devices”h]”hŒ8test the freezing of processes and suspending of devices”…””}”(hj&  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K8hj"  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhj  ubah}”(h]”h ]”h"]”h$]”h&]”jü  jý  uh1jÙ  hŸh¶h K8hj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÔ  hj
  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¾  hŸh¶h K8hj»  hžhubj¿  )”}”(hŒlplatform
- test the freezing of processes, suspending of devices and platform
  global control methods [1]_
”h]”(jÅ  )”}”(hŒplatform”h]”hŒplatform”…””}”(hjP  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÄ  hŸh¶h K<hjL  ubjÕ  )”}”(hhh]”jÚ  )”}”(hhh]”hÃ)”}”(hŒ_test the freezing of processes, suspending of devices and platform
global control methods [1]_
”h]”hÉ)”}”(hŒ^test the freezing of processes, suspending of devices and platform
global control methods [1]_”h]”(hŒZtest the freezing of processes, suspending of devices and platform
global control methods ”…””}”(hjh  hžhhŸNh NubhŒfootnote_reference”“”)”}”(hŒ[1]_”h]”hŒ1”…””}”(hjr  hžhhŸNh Nubah}”(h]”Œid1”ah ]”h"]”h$]”h&]”Œrefid”Œid4”Œdocname”Œpower/basic-pm-debugging”uh1jp  hjh  Œresolved”Kubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K;hjd  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhja  ubah}”(h]”h ]”h"]”h$]”h&]”jü  jý  uh1jÙ  hŸh¶h K;hj^  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÔ  hjL  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¾  hŸh¶h K<hj»  hžhubj¿  )”}”(hŒprocessors
- test the freezing of processes, suspending of devices, platform
  global control methods [1]_ and the disabling of nonboot CPUs
”h]”(jÅ  )”}”(hŒ
processors”h]”hŒ
processors”…””}”(hj¨  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÄ  hŸh¶h K@hj¤  ubjÕ  )”}”(hhh]”jÚ  )”}”(hhh]”hÃ)”}”(hŒ~test the freezing of processes, suspending of devices, platform
global control methods [1]_ and the disabling of nonboot CPUs
”h]”hÉ)”}”(hŒ}test the freezing of processes, suspending of devices, platform
global control methods [1]_ and the disabling of nonboot CPUs”h]”(hŒWtest the freezing of processes, suspending of devices, platform
global control methods ”…””}”(hjÀ  hžhhŸNh Nubjq  )”}”(hŒ[1]_”h]”hŒ1”…””}”(hjÈ  hžhhŸNh Nubah}”(h]”Œid2”ah ]”h"]”h$]”h&]”j  j‚  jƒ  j„  uh1jp  hjÀ  j…  KubhŒ" and the disabling of nonboot CPUs”…””}”(hjÀ  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K?hj¼  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhj¹  ubah}”(h]”h ]”h"]”h$]”h&]”jü  jý  uh1jÙ  hŸh¶h K?hj¶  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÔ  hj¤  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¾  hŸh¶h K@hj»  hžhubj¿  )”}”(hŒ±core
- test the freezing of processes, suspending of devices, platform global
  control methods\ [1]_, the disabling of nonboot CPUs and suspending
  of platform/system devices
”h]”(jÅ  )”}”(hŒcore”h]”hŒcore”…””}”(hjý  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jÄ  hŸh¶h KEhjù  ubjÕ  )”}”(hhh]”jÚ  )”}”(hhh]”hÃ)”}”(hŒ¦test the freezing of processes, suspending of devices, platform global
control methods\ [1]_, the disabling of nonboot CPUs and suspending
of platform/system devices
”h]”hÉ)”}”(hŒ¥test the freezing of processes, suspending of devices, platform global
control methods\ [1]_, the disabling of nonboot CPUs and suspending
of platform/system devices”h]”(hŒXtest the freezing of processes, suspending of devices, platform global
control methods  ”…””}”(hj  hžhhŸNh Nubjq  )”}”(hŒ[1]_”h]”hŒ1”…””}”(hj  hžhhŸNh Nubah}”(h]”Œid3”ah ]”h"]”h$]”h&]”j  j‚  jƒ  j„  uh1jp  hj  j…  KubhŒI, the disabling of nonboot CPUs and suspending
of platform/system devices”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KChj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhj  ubah}”(h]”h ]”h"]”h$]”h&]”jü  jý  uh1jÙ  hŸh¶h KChj  ubah}”(h]”h ]”h"]”h$]”h&]”uh1jÔ  hjù  ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¾  hŸh¶h KEhj»  hžhubeh}”(h]”h ]”h"]”h$]”h&]”uh1j¹  hjš  hžhhŸNh NubhŒfootnote”“”)”}”(hŒˆthe platform global control methods are only available on ACPI systems
and are only tested if the hibernation mode is set to "platform"
”h]”(hŒlabel”“”)”}”(hŒ1”h]”hŒ1”…””}”(hj\  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jZ  hjV  ubhÉ)”}”(hŒ‡the platform global control methods are only available on ACPI systems
and are only tested if the hibernation mode is set to "platform"”h]”hŒ‹the platform global control methods are only available on ACPI systems
and are only tested if the hibernation mode is set to â€œplatformâ€”…””}”(hjj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KIhjV  ubeh}”(h]”j‚  ah ]”h"]”Œ1”ah$]”h&]”(j|  jÒ  j'  ejƒ  j„  uh1jT  hŸh¶h KGhjš  hžhj…  KubhÉ)”}”(hXJ  To use one of them it is necessary to write the corresponding string to
/sys/power/pm_test (eg. "devices" to test the freezing of processes and
suspending devices) and issue the standard hibernation commands.  For example,
to use the "devices" test mode along with the "platform" mode of hibernation,
you should do the following::”h]”hXU  To use one of them it is necessary to write the corresponding string to
/sys/power/pm_test (eg. â€œdevicesâ€ to test the freezing of processes and
suspending devices) and issue the standard hibernation commands.  For example,
to use the â€œdevicesâ€ test mode along with the â€œplatformâ€ mode of hibernation,
you should do the following:”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KLhjš  hžhubj'  )”}”(hŒd# echo devices > /sys/power/pm_test
# echo platform > /sys/power/disk
# echo disk > /sys/power/state”h]”hŒd# echo devices > /sys/power/pm_test
# echo platform > /sys/power/disk
# echo disk > /sys/power/state”…””}”hj  sbah}”(h]”h ]”h"]”h$]”h&]”j6  j7  uh1j&  hŸh¶h KRhjš  hžhubhÉ)”}”(hX4  Then, the kernel will try to freeze processes, suspend devices, wait a few
seconds (5 by default, but configurable by the suspend.pm_test_delay module
parameter), resume devices and thaw processes.  If "platform" is written to
/sys/power/pm_test , then after suspending devices the kernel will additionally
invoke the global control methods (eg. ACPI global control methods) used to
prepare the platform firmware for hibernation.  Next, it will wait a
configurable number of seconds and invoke the platform (eg. ACPI) global
methods used to cancel hibernation etc.”h]”hX8  Then, the kernel will try to freeze processes, suspend devices, wait a few
seconds (5 by default, but configurable by the suspend.pm_test_delay module
parameter), resume devices and thaw processes.  If â€œplatformâ€ is written to
/sys/power/pm_test , then after suspending devices the kernel will additionally
invoke the global control methods (eg. ACPI global control methods) used to
prepare the platform firmware for hibernation.  Next, it will wait a
configurable number of seconds and invoke the platform (eg. ACPI) global
methods used to cancel hibernation etc.”…””}”(hj›  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KVhjš  hžhubhÉ)”}”(hXS  Writing "none" to /sys/power/pm_test causes the kernel to switch to the normal
hibernation/suspend operations.  Also, when open for reading, /sys/power/pm_test
contains a space-separated list of all available tests (including "none" that
represents the normal functionality) in which the current test level is
indicated by square brackets.”h]”hX[  Writing â€œnoneâ€ to /sys/power/pm_test causes the kernel to switch to the normal
hibernation/suspend operations.  Also, when open for reading, /sys/power/pm_test
contains a space-separated list of all available tests (including â€œnoneâ€ that
represents the normal functionality) in which the current test level is
indicated by square brackets.”…””}”(hj©  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K_hjš  hžhubhÉ)”}”(hX  Generally, as you can see, each test level is more "invasive" than the previous
one and the "core" level tests the hardware and drivers as deeply as possible
without creating a hibernation image.  Obviously, if the "devices" test fails,
the "platform" test will fail as well and so on.  Thus, as a rule of thumb, you
should try the test modes starting from "freezer", through "devices", "platform"
and "processors" up to "core" (repeat the test on each level a couple of times
to make sure that any random factors are avoided).”h]”hX3  Generally, as you can see, each test level is more â€œinvasiveâ€ than the previous
one and the â€œcoreâ€ level tests the hardware and drivers as deeply as possible
without creating a hibernation image.  Obviously, if the â€œdevicesâ€ test fails,
the â€œplatformâ€ test will fail as well and so on.  Thus, as a rule of thumb, you
should try the test modes starting from â€œfreezerâ€, through â€œdevicesâ€, â€œplatformâ€
and â€œprocessorsâ€ up to â€œcoreâ€ (repeat the test on each level a couple of times
to make sure that any random factors are avoided).”…””}”(hj·  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kehjš  hžhubhÉ)”}”(hX@  If the "freezer" test fails, there is a task that cannot be frozen (in that case
it usually is possible to identify the offending task by analysing the output of
dmesg obtained after the failing test).  Failure at this level usually means
that there is a problem with the tasks freezer subsystem that should be
reported.”h]”hXD  If the â€œfreezerâ€ test fails, there is a task that cannot be frozen (in that case
it usually is possible to identify the offending task by analysing the output of
dmesg obtained after the failing test).  Failure at this level usually means
that there is a problem with the tasks freezer subsystem that should be
reported.”…””}”(hjÅ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kmhjš  hžhubhÉ)”}”(hX'  If the "devices" test fails, most likely there is a driver that cannot suspend
or resume its device (in the latter case the system may hang or become unstable
after the test, so please take that into consideration).  To find this driver,
you can carry out a binary search according to the rules:”h]”hX+  If the â€œdevicesâ€ test fails, most likely there is a driver that cannot suspend
or resume its device (in the latter case the system may hang or become unstable
after the test, so please take that into consideration).  To find this driver,
you can carry out a binary search according to the rules:”…””}”(hjÓ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kshjš  hžhubjÚ  )”}”(hhh]”(hÃ)”}”(hŒ½if the test fails, unload a half of the drivers currently loaded and repeat
(that would probably involve rebooting the system, so always note what drivers
have been loaded before the test),”h]”hÉ)”}”(hŒ½if the test fails, unload a half of the drivers currently loaded and repeat
(that would probably involve rebooting the system, so always note what drivers
have been loaded before the test),”h]”hŒ½if the test fails, unload a half of the drivers currently loaded and repeat
(that would probably involve rebooting the system, so always note what drivers
have been loaded before the test),”…””}”(hjè  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kxhjä  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhjá  hžhhŸh¶h NubhÃ)”}”(hŒ]if the test succeeds, load a half of the drivers you have unloaded most
recently and repeat.
”h]”hÉ)”}”(hŒ\if the test succeeds, load a half of the drivers you have unloaded most
recently and repeat.”h]”hŒ\if the test succeeds, load a half of the drivers you have unloaded most
recently and repeat.”…””}”(hj   hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K{hjü  ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÂhjá  hžhhŸh¶h Nubeh}”(h]”h ]”h"]”h$]”h&]”jü  jý  uh1jÙ  hŸh¶h Kxhjš  hžhubhÉ)”}”(hŒÌOnce you have found the failing driver (there can be more than just one of
them), you have to unload it every time before hibernation.  In that case please
make sure to report the problem with the driver.”h]”hŒÌOnce you have found the failing driver (there can be more than just one of
them), you have to unload it every time before hibernation.  In that case please
make sure to report the problem with the driver.”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K~hjš  hžhubhÉ)”}”(hXz  It is also possible that the "devices" test will still fail after you have
unloaded all modules. In that case, you may want to look in your kernel
configuration for the drivers that can be compiled as modules (and test again
with these drivers compiled as modules).  You may also try to use some special
kernel command line options such as "noapic", "noacpi" or even "acpi=off".”h]”hXŠ  It is also possible that the â€œdevicesâ€ test will still fail after you have
unloaded all modules. In that case, you may want to look in your kernel
configuration for the drivers that can be compiled as modules (and test again
with these drivers compiled as modules).  You may also try to use some special
kernel command line options such as â€œnoapicâ€, â€œnoacpiâ€ or even â€œacpi=offâ€.”…””}”(hj(  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K‚hjš  hžhubhÉ)”}”(hX  If the "platform" test fails, there is a problem with the handling of the
platform (eg. ACPI) firmware on your system.  In that case the "platform" mode
of hibernation is not likely to work.  You can try the "shutdown" mode, but that
is rather a poor man's workaround.”h]”hX  If the â€œplatformâ€ test fails, there is a problem with the handling of the
platform (eg. ACPI) firmware on your system.  In that case the â€œplatformâ€ mode
of hibernation is not likely to work.  You can try the â€œshutdownâ€ mode, but that
is rather a poor manâ€™s workaround.”…””}”(hj6  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Kˆhjš  hžhubhÉ)”}”(hXI  If the "processors" test fails, the disabling/enabling of nonboot CPUs does not
work (of course, this only may be an issue on SMP systems) and the problem
should be reported.  In that case you can also try to switch the nonboot CPUs
off and on using the /sys/devices/system/cpu/cpu*/online sysfs attributes and
see if that works.”h]”hXM  If the â€œprocessorsâ€ test fails, the disabling/enabling of nonboot CPUs does not
work (of course, this only may be an issue on SMP systems) and the problem
should be reported.  In that case you can also try to switch the nonboot CPUs
off and on using the /sys/devices/system/cpu/cpu*/online sysfs attributes and
see if that works.”…””}”(hjD  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h Khjš  hžhubhÉ)”}”(hŒòIf the "core" test fails, which means that suspending of the system/platform
devices has failed (these devices are suspended on one CPU with interrupts off),
the problem is most probably hardware-related and serious, so it should be
reported.”h]”hŒöIf the â€œcoreâ€ test fails, which means that suspending of the system/platform
devices has failed (these devices are suspended on one CPU with interrupts off),
the problem is most probably hardware-related and serious, so it should be
reported.”…””}”(hjR  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K“hjš  hžhubhÉ)”}”(hX  A failure of any of the "platform", "processors" or "core" tests may cause your
system to hang or become unstable, so please beware.  Such a failure usually
indicates a serious problem that very well may be related to the hardware, but
please report it anyway.”h]”hX  A failure of any of the â€œplatformâ€, â€œprocessorsâ€ or â€œcoreâ€ tests may cause your
system to hang or become unstable, so please beware.  Such a failure usually
indicates a serious problem that very well may be related to the hardware, but
please report it anyway.”…””}”(hj`  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K˜hjš  hžhubeh}”(h]”Œa-test-modes-of-hibernation”ah ]”h"]”Œa) test modes of hibernation”ah$]”h&]”uh1h¡hj  hžhhŸh¶h K-ubh¢)”}”(hhh]”(h§)”}”(hŒ b) Testing minimal configuration”h]”hŒ b) Testing minimal configuration”…””}”(hjy  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjv  hžhhŸh¶h KžubhÉ)”}”(hXQ  If all of the hibernation test modes work, you can boot the system with the
"init=/bin/bash" command line parameter and attempt to hibernate in the
"reboot", "shutdown" and "platform" modes.  If that does not work, there
probably is a problem with a driver statically compiled into the kernel and you
can try to compile more drivers as modules, so that they can be tested
individually.  Otherwise, there is a problem with a modular driver and you can
find it by loading a half of the modules you normally use and binary searching
in accordance with the algorithm:
- if there are n modules loaded and the attempt to suspend and resume fails,
unload n/2 of the modules and try again (that would probably involve rebooting
the system),
- if there are n modules loaded and the attempt to suspend and resume succeeds,
load n/2 modules more and try again.”h]”hXa  If all of the hibernation test modes work, you can boot the system with the
â€œinit=/bin/bashâ€ command line parameter and attempt to hibernate in the
â€œrebootâ€, â€œshutdownâ€ and â€œplatformâ€ modes.  If that does not work, there
probably is a problem with a driver statically compiled into the kernel and you
can try to compile more drivers as modules, so that they can be tested
individually.  Otherwise, there is a problem with a modular driver and you can
find it by loading a half of the modules you normally use and binary searching
in accordance with the algorithm:
- if there are n modules loaded and the attempt to suspend and resume fails,
unload n/2 of the modules and try again (that would probably involve rebooting
the system),
- if there are n modules loaded and the attempt to suspend and resume succeeds,
load n/2 modules more and try again.”…””}”(hj‡  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K hjv  hžhubhÉ)”}”(hŒ‘Again, if you find the offending module(s), it(they) must be unloaded every time
before hibernation, and please report the problem with it(them).”h]”hŒ‘Again, if you find the offending module(s), it(they) must be unloaded every time
before hibernation, and please report the problem with it(them).”…””}”(hj•  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K®hjv  hžhubeh}”(h]”Œb-testing-minimal-configuration”ah ]”h"]”Œ b) testing minimal configuration”ah$]”h&]”uh1h¡hj  hžhhŸh¶h Kžubh¢)”}”(hhh]”(h§)”}”(hŒ-c) Using the "test_resume" hibernation option”h]”hŒ1c) Using the â€œtest_resumeâ€ hibernation option”…””}”(hj®  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj«  hžhhŸh¶h K²ubhÉ)”}”(hŒé/sys/power/disk generally tells the kernel what to do after creating a
hibernation image.  One of the available options is "test_resume" which
causes the just created image to be used for immediate restoration.  Namely,
after doing::”h]”hŒì/sys/power/disk generally tells the kernel what to do after creating a
hibernation image.  One of the available options is â€œtest_resumeâ€ which
causes the just created image to be used for immediate restoration.  Namely,
after doing:”…””}”(hj¼  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K´hj«  hžhubj'  )”}”(hŒC# echo test_resume > /sys/power/disk
# echo disk > /sys/power/state”h]”hŒC# echo test_resume > /sys/power/disk
# echo disk > /sys/power/state”…””}”hjÊ  sbah}”(h]”h ]”h"]”h$]”h&]”j6  j7  uh1j&  hŸh¶h K¹hj«  hžhubhÉ)”}”(hŒŠa hibernation image will be created and a resume from it will be triggered
immediately without involving the platform firmware in any way.”h]”hŒŠa hibernation image will be created and a resume from it will be triggered
immediately without involving the platform firmware in any way.”…””}”(hjØ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K¼hj«  hžhubhÉ)”}”(hX(  That test can be used to check if failures to resume from hibernation are
related to bad interactions with the platform firmware.  That is, if the above
works every time, but resume from actual hibernation does not work or is
unreliable, the platform firmware may be responsible for the failures.”h]”hX(  That test can be used to check if failures to resume from hibernation are
related to bad interactions with the platform firmware.  That is, if the above
works every time, but resume from actual hibernation does not work or is
unreliable, the platform firmware may be responsible for the failures.”…””}”(hjæ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h K¿hj«  hžhubhÉ)”}”(hXŽ  On architectures and platforms that support using different kernels to restore
hibernation images (that is, the kernel used to read the image from storage and
load it into memory is different from the one included in the image) or support
kernel address space randomization, it also can be used to check if failures
to resume may be related to the differences between the restore and image
kernels.”h]”hXŽ  On architectures and platforms that support using different kernels to restore
hibernation images (that is, the kernel used to read the image from storage and
load it into memory is different from the one included in the image) or support
kernel address space randomization, it also can be used to check if failures
to resume may be related to the differences between the restore and image
kernels.”…””}”(hjô  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KÄhj«  hžhubeh}”(h]”Œ*c-using-the-test-resume-hibernation-option”ah ]”h"]”Œ-c) using the "test_resume" hibernation option”ah$]”h&]”uh1h¡hj  hžhhŸh¶h K²ubh¢)”}”(hhh]”(h§)”}”(hŒd) Advanced debugging”h]”hŒd) Advanced debugging”…””}”(hj  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hj
  hžhhŸh¶h KÌubhÉ)”}”(hXì  In case that hibernation does not work on your system even in the minimal
configuration and compiling more drivers as modules is not practical or some
modules cannot be unloaded, you can use one of the more advanced debugging
techniques to find the problem.  First, if there is a serial port in your box,
you can boot the kernel with the 'no_console_suspend' parameter and try to log
kernel messages using the serial console.  This may provide you with some
information about the reasons of the suspend (resume) failure.  Alternatively,
it may be possible to use a FireWire port for debugging with firescope
(http://v3.sk/~lkundrak/firescope/).  On x86 it is also possible to
use the PM_TRACE mechanism documented in Documentation/power/s2ram.rst .”h]”(hXe  In case that hibernation does not work on your system even in the minimal
configuration and compiling more drivers as modules is not practical or some
modules cannot be unloaded, you can use one of the more advanced debugging
techniques to find the problem.  First, if there is a serial port in your box,
you can boot the kernel with the â€˜no_console_suspendâ€™ parameter and try to log
kernel messages using the serial console.  This may provide you with some
information about the reasons of the suspend (resume) failure.  Alternatively,
it may be possible to use a FireWire port for debugging with firescope
(”…””}”(hj  hžhhŸNh NubhÓ)”}”(hŒ!http://v3.sk/~lkundrak/firescope/”h]”hŒ!http://v3.sk/~lkundrak/firescope/”…””}”(hj#  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j%  uh1hÒhj  ubhŒj).  On x86 it is also possible to
use the PM_TRACE mechanism documented in Documentation/power/s2ram.rst .”…””}”(hj  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KÎhj
  hžhubeh}”(h]”Œd-advanced-debugging”ah ]”h"]”Œd) advanced debugging”ah$]”h&]”uh1h¡hj  hžhhŸh¶h KÌubeh}”(h]”Œ.testing-hibernation-aka-suspend-to-disk-or-std”ah ]”h"]”Œ31. testing hibernation (aka suspend to disk or std)”ah$]”h&]”uh1h¡hh£hžhhŸh¶h Kubh¢)”}”(hhh]”(h§)”}”(hŒ2. Testing suspend to RAM (STR)”h]”hŒ2. Testing suspend to RAM (STR)”…””}”(hjO  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1h¦hjL  hžhhŸh¶h KÚubhÉ)”}”(hŒÂTo verify that the STR works, it is generally more convenient to use the s2ram
tool available from http://suspend.sf.net and documented at
http://en.opensuse.org/SDB:Suspend_to_RAM (S2RAM_LINK).”h]”(hŒcTo verify that the STR works, it is generally more convenient to use the s2ram
tool available from ”…””}”(hj]  hžhhŸNh NubhÓ)”}”(hŒhttp://suspend.sf.net”h]”hŒhttp://suspend.sf.net”…””}”(hje  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jg  uh1hÒhj]  ubhŒ and documented at
”…””}”(hj]  hžhhŸNh NubhÓ)”}”(hŒ)http://en.opensuse.org/SDB:Suspend_to_RAM”h]”hŒ)http://en.opensuse.org/SDB:Suspend_to_RAM”…””}”(hjx  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jz  uh1hÒhj]  ubhŒ (S2RAM_LINK).”…””}”(hj]  hžhhŸNh Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KÜhjL  hžhubhÉ)”}”(hX  Namely, after writing "freezer", "devices", "platform", "processors", or "core"
into /sys/power/pm_test (available if the kernel is compiled with
CONFIG_PM_DEBUG set) the suspend code will work in the test mode corresponding
to given string.  The STR test modes are defined in the same way as for
hibernation, so please refer to Section 1 for more information about them.  In
particular, the "core" test allows you to test everything except for the actual
invocation of the platform firmware in order to put the system into the sleep
state.”h]”hX4  Namely, after writing â€œfreezerâ€, â€œdevicesâ€, â€œplatformâ€, â€œprocessorsâ€, or â€œcoreâ€
into /sys/power/pm_test (available if the kernel is compiled with
CONFIG_PM_DEBUG set) the suspend code will work in the test mode corresponding
to given string.  The STR test modes are defined in the same way as for
hibernation, so please refer to Section 1 for more information about them.  In
particular, the â€œcoreâ€ test allows you to test everything except for the actual
invocation of the platform firmware in order to put the system into the sleep
state.”…””}”(hj‘  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KàhjL  hžhubhÉ)”}”(hŒÑAmong other things, the testing with the help of /sys/power/pm_test may allow
you to identify drivers that fail to suspend or resume their devices.  They
should be unloaded every time before an STR transition.”h]”hŒÑAmong other things, the testing with the help of /sys/power/pm_test may allow
you to identify drivers that fail to suspend or resume their devices.  They
should be unloaded every time before an STR transition.”…””}”(hjŸ  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KéhjL  hžhubhÉ)”}”(hXû  Next, you can follow the instructions at S2RAM_LINK to test the system, but if
it does not work "out of the box", you may need to boot it with
"init=/bin/bash" and test s2ram in the minimal configuration.  In that case,
you may be able to search for failing drivers by following the procedure
analogous to the one described in section 1.  If you find some failing drivers,
you will have to unload them every time before an STR transition (ie. before
you run s2ram), and please report the problems with them.”h]”hX  Next, you can follow the instructions at S2RAM_LINK to test the system, but if
it does not work â€œout of the boxâ€, you may need to boot it with
â€œinit=/bin/bashâ€ and test s2ram in the minimal configuration.  In that case,
you may be able to search for failing drivers by following the procedure
analogous to the one described in section 1.  If you find some failing drivers,
you will have to unload them every time before an STR transition (ie. before
you run s2ram), and please report the problems with them.”…””}”(hj­  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KíhjL  hžhubhÉ)”}”(hŒfThere is a debugfs entry which shows the suspend to RAM statistics. Here is an
example of its output::”h]”hŒeThere is a debugfs entry which shows the suspend to RAM statistics. Here is an
example of its output:”…””}”(hj»  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h KõhjL  hžhubj'  )”}”(hX”  # mount -t debugfs none /sys/kernel/debug
# cat /sys/kernel/debug/suspend_stats
success: 20
fail: 5
failed_freeze: 0
failed_prepare: 0
failed_suspend: 5
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_noirq: 0
failures:
  last_failed_dev:      alarm
                        adc
  last_failed_errno:    -16
                        -16
  last_failed_step:     suspend
                        suspend”h]”hX”  # mount -t debugfs none /sys/kernel/debug
# cat /sys/kernel/debug/suspend_stats
success: 20
fail: 5
failed_freeze: 0
failed_prepare: 0
failed_suspend: 5
failed_suspend_noirq: 0
failed_resume: 0
failed_resume_noirq: 0
failures:
  last_failed_dev:      alarm
                        adc
  last_failed_errno:    -16
                        -16
  last_failed_step:     suspend
                        suspend”…””}”hjÉ  sbah}”(h]”h ]”h"]”h$]”h&]”j6  j7  uh1j&  hŸh¶h KøhjL  hžhubhÉ)”}”(hX  Field success means the success number of suspend to RAM, and field fail means
the failure number. Others are the failure number of different steps of suspend
to RAM. suspend_stats just lists the last 2 failed devices, error number and
failed step of suspend.”h]”hX  Field success means the success number of suspend to RAM, and field fail means
the failure number. Others are the failure number of different steps of suspend
to RAM. suspend_stats just lists the last 2 failed devices, error number and
failed step of suspend.”…””}”(hj×  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhŸh¶h M
hjL  hžhubeh}”(h]”Œtesting-suspend-to-ram-str”ah ]”h"]”Œ2. testing suspend to ram (str)”ah$]”h&]”uh1h¡hh£hžhhŸh¶h KÚubeh}”(h]”Œ!debugging-hibernation-and-suspend”ah ]”h"]”Œ!debugging hibernation and suspend”ah$]”h&]”uh1h¡hhhžhhŸh¶h Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”h¶uh1hŒcurrent_source”NŒcurrent_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)”}”(h¦NŒ	generator”NŒ	datestamp”NŒsource_link”NŒ
source_url”NŒtoc_backlinks”Œentry”Œfootnote_backlinks”KŒsectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒstrip_classes”NŒreport_level”KŒ
halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ	traceback”ˆŒinput_encoding”Œ	utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”j  Œerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œlanguage_code”Œen”Œrecord_dependencies”NŒconfig”NŒ	id_prefix”hŒauto_id_prefix”Œid”Œdump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”h¶Œ_destination”NŒ_config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒraw_enabled”KŒline_length_limit”M'Œpep_references”NŒpep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒrfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ	tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œsmart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œdocinfo_xform”KŒsectsubtitle_xform”‰Œimage_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”Œ1”]”(jr  jÈ  j  esŒrefids”}”Œnameids”}”(jò  jï  jI  jF  js  jp  j|  j‚  j¨  j¥  j  j  jA  j>  jê  jç  uŒ	nametypes”}”(jò  ‰jI  ‰js  ‰j|  ˆj¨  ‰j  ‰jA  ‰jê  ‰uh}”(jï  h£jF  j  jp  jš  j|  jr  jÒ  jÈ  j'  j  j‚  jV  j¥  jv  j  j«  j>  j
  jç  jL  uŒfootnote_refs”}”jX  ]”(jr  jÈ  j  esŒcitation_refs”}”Œautofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ	footnotes”]”jV  aŒ	citations”]”Œautofootnote_start”KŒsymbol_footnote_start”K Œ
id_counter”Œcollections”ŒCounter”“”}”j&  Ks…”R”Œparse_messages”]”hŒsystem_message”“”)”}”(hhh]”hÉ)”}”(hŒ:Enumerated list start value not ordinal-1: "C" (ordinal 3)”h]”hŒ>Enumerated list start value not ordinal-1: â€œCâ€ (ordinal 3)”…””}”(hj‚  hžhhŸNh Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÈhj  ubah}”(h]”h ]”h"]”h$]”h&]”Œlevel”KŒtype”ŒINFO”Œsource”h¶Œline”Kuh1j}  hh¹ubaŒtransform_messages”]”Œtransformer”NŒinclude_log”]”Œ
decoration”Nhžhub.