Lines Matching +full:platform +full:- +full:level

17 modes causes the PM core to skip some platform-related callbacks which on ACPI
19 to hibernate or resume in the "reboot" mode, you should try the "platform" mode:
21 # echo platform > /sys/power/disk
26 Unfortunately, the "platform" mode of hibernation does not work on some systems
36 If neither "platform" nor "shutdown" hibernation mode works, you will need to
47 - test the freezing of processes
50 - test the freezing of processes and suspending of devices
52 platform
53 - test the freezing of processes, suspending of devices and platform
57 - test the freezing of processes, suspending of devices, platform
61 - test the freezing of processes, suspending of devices, platform global
63   platform/system devices
65 (*) the platform global control methods are only available on ACPI systems
66     and are only tested if the hibernation mode is set to "platform"
71 to use the "devices" test mode along with the "platform" mode of hibernation,
75 # echo platform > /sys/power/disk
80 parameter), resume devices and thaw processes.  If "platform" is written to
83 prepare the platform firmware for hibernation.  Next, it will wait a
84 configurable number of seconds and invoke the platform (eg. ACPI) global
89 contains a space-separated list of all available tests (including "none" that
90 represents the normal functionality) in which the current test level is
93 Generally, as you can see, each test level is more "invasive" than the previous
94 one and the "core" level tests the hardware and drivers as deeply as possible
96 the "platform" test will fail as well and so on.  Thus, as a rule of thumb, you
97 should try the test modes starting from "freezer", through "devices", "platform"
98 and "processors" up to "core" (repeat the test on each level a couple of times
103 dmesg obtained after the failing test).  Failure at this level usually means
111 - if the test fails, unload a half of the drivers currently loaded and repeat
114 - if the test succeeds, load a half of the drivers you have unloaded most
127 If the "platform" test fails, there is a problem with the handling of the
128 platform (eg. ACPI) firmware on your system.  In that case the "platform" mode
138 If the "core" test fails, which means that suspending of the system/platform
140 the problem is most probably hardware-related and serious, so it should be
143 A failure of any of the "platform", "processors" or "core" tests may cause your
152 "reboot", "shutdown" and "platform" modes.  If that does not work, there
158 - if there are n modules loaded and the attempt to suspend and resume fails,
161 - if there are n modules loaded and the attempt to suspend and resume succeeds,
178 immediately without involving the platform firmware in any way.
181 related to bad interactions with the platform firmware.  That is, if the above
183 unreliable, the platform firmware may be responsible for the failures.
211 Namely, after writing "freezer", "devices", "platform", "processors", or "core"
217 invocation of the platform firmware in order to put the system into the sleep
234 	# mount -t debugfs none /sys/kernel/debug
247 	  last_failed_errno:	-16
248 				-16