Lines Matching +full:suspend +full:- +full:in +full:- +full:wait
15 labels, which may be "mem" (suspend), "standby" (power-on
16 suspend), "freeze" (suspend-to-idle) and "disk" (hibernation).
21 See Documentation/admin-guide/pm/sleep-states.rst for more
29 system suspend. Reading from it returns the available modes
32 to suspend the system (by writing "mem" to the /sys/power/state
33 file described above) is enclosed in square brackets.
36 represented by it to be used on subsequent attempts to suspend
39 See Documentation/admin-guide/pm/sleep-states.rst for more
47 suspend-to-disk mechanism. Reading from this file returns
49 sleep on the next suspend. There are four methods supported:
51 'firmware' - means that the memory image will be saved to disk
52 by some firmware, in which case we also assume that the
53 firmware will handle the system suspend.
55 'platform' - the memory image will be saved by the kernel and
59 'shutdown' - the memory image will be saved by the kernel and
62 'reboot' - the memory image will be saved by the kernel and
66 two testing modes of the suspend-to-disk mechanism: 'testproc'
67 or 'test'. If the suspend-to-disk mechanism is in the
69 the kernel to disable nonboot CPUs and freeze tasks, wait for 5
70 seconds, unfreeze tasks and enable nonboot CPUs. If it is in
73 memory, suspend devices, wait for 5 seconds, resume devices,
75 look in the log messages and work out, for example, which code
78 The suspend-to-disk method may be chosen by writing to this
81 - 'firmware'
82 - 'platform'
83 - 'shutdown'
84 - 'reboot'
85 - 'testproc'
86 - 'test'
96 created by the suspend-to-disk mechanism. It can be written a
97 string representing a non-negative integer that will be used
98 as an upper limit of the image size, in bytes. The kernel's
99 suspend-to-disk code will do its best to ensure the image size
101 impossible, the kernel will try to suspend anyway using the
102 smallest image possible. In particular, if "0" is written to
103 this file, the suspend image will be as small as possible.
113 last PM event point in the RTC across reboots, so that you can
114 debug a machine that just hangs during suspend (or more
120 To use this debugging feature you should attempt to suspend
123 dmesg -s 1000000 | grep 'hash matches'
127 referred to a device created by a loadable kernel module. In
131 CAUTION: Using it will cause your machine's real-time (CMOS)
139 device associated with the last PM event point saved in the RTC
143 the device hash in the RTC at boot, with a newline after each
150 Due to the small hash size necessary to fit in the RTC, it is
151 possible that more than one device matches the hash, in which
162 user space to enable or disable asynchronous suspend and resume
164 drivers' suspend and resume callbacks to be executed in parallel
165 with each other and with the main suspend thread. It is enabled
167 disabled by writing "0" to this file, in which case all devices
192 be written a string representing a non-negative integer that
194 made by device drivers' "freeze" callbacks, in bytes.
208 in the system at that time. After every execution, regardless
232 The other part of the string will be regarded as a timeout (in
236 in question.
264 control whether the time taken by devices to suspend and
266 devices that take too long to suspend or resume.
279 kernel during the most recent system suspend/resume cycle.
289 of debug messages from the system suspend/hiberbation
314 The /sys/power/suspend_stats directory contains suspend related
343 number of times preparing all non-sysdev devices for
352 non-sysdev devices failed.
375 the number of times executing "suspend" callbacks
376 of all non-sysdev devices failed.
383 the number of times executing "late suspend" callbacks
391 the number of times executing "noirq suspend" callbacks
399 the last device for which a suspend/resume callback failed.
414 the last failed step in the suspend/resume path.
421 contains the duration of time spent in a hardware sleep
422 state in the most recent system suspend-resume cycle.
423 This number is measured in microseconds.
430 contains the aggregate of time spent in a hardware sleep
432 is measured in microseconds.
440 report for time spent in a hardware sleep state. When sleep
443 This number is measured in microseconds.
450 filesystems during system suspend (after freezing user space
455 The default is "1" if the build-time "SUSPEND_SKIP_SYNC" config