Custom Search
Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - S index
The Linux kernel configuration item CONFIG_SOFTWARE_SUSPEND has multiple definitions:
kernel/power/KconfigThe configuration item CONFIG_SOFTWARE_SUSPEND:
CONFIG_PM && CONFIG_SWAP && ((( CONFIG_X86 || CONFIG_PPC64_SWSUSP ) && (! CONFIG_SMP || CONFIG_SUSPEND_SMP )) || (( CONFIG_FRV || CONFIG_PPC32 ) && ! CONFIG_SMP ))Enable the suspend to disk (STD) functionality, which is usually called "hibernation" in user interfaces. STD checkpoints the system and powers it off; and restores that checkpoint on reboot.
You can suspend your machine with 'echo disk > /sys/power/state'. Alternatively, you can use the additional userland tools available from http://suspend.sf.net.
In principle it does not require ACPI or APM, although for example ACPI will be used for the final steps when it is available. One of the reasons to use software suspend is that the firmware hooks for suspend states like suspend-to-RAM (STR) often don't work very well with Linux.
It creates an image which is saved in your active swap. Upon the next boot, pass the 'resume=/dev/swappartition' argument to the kernel to have it detect the saved image, restore memory state from it, and continue to run as before. If you do not want the previous state to be reloaded, then use the 'noresume' kernel command line argument. Note, however, that fsck will be run on your filesystems and you will need to run mkswap against the swap partition used for the suspend.
It also works with swap files to a limited extent (for details see Documentation/power/swsusp-and-swap-files.txt).
Right now you may boot without resuming and resume later but in the meantime you cannot use the swap partition(s)/file(s) involved in suspending. Also in this case you must not use the filesystems that were mounted before the suspend. In particular, you MUST NOT MOUNT any journaled filesystems mounted before the suspend or they will get corrupted in a nasty way.
For more information take a look at Documentation/power/swsusp.txt.
kernel/power/KconfigThe configuration item CONFIG_SOFTWARE_SUSPEND:
CONFIG_PM && CONFIG_SWAP && (( CONFIG_X86 && (! CONFIG_SMP || CONFIG_SUSPEND_SMP )) || (( CONFIG_FRV || CONFIG_PPC32 ) && ! CONFIG_SMP ))Enable the suspend to disk (STD) functionality.
You can suspend your machine with 'echo disk > /sys/power/state'. Alternatively, you can use the additional userland tools available from http://suspend.sf.net.
In principle it does not require ACPI or APM, although for example ACPI will be used if available.
It creates an image which is saved in your active swap. Upon the next boot, pass the 'resume=/dev/swappartition' argument to the kernel to have it detect the saved image, restore memory state from it, and continue to run as before. If you do not want the previous state to be reloaded, then use the 'noresume' kernel command line argument. Note, however, that fsck will be run on your filesystems and you will need to run mkswap against the swap partition used for the suspend.
It also works with swap files to a limited extent (for details see Documentation/power/swsusp-and-swap-files.txt).
Right now you may boot without resuming and resume later but in the meantime you cannot use the swap partition(s)/file(s) involved in suspending. Also in this case you must not use the filesystems that were mounted before the suspend. In particular, you MUST NOT MOUNT any journaled filesystems mounted before the suspend or they will get corrupted in a nasty way.
For more information take a look at Documentation/power/swsusp.txt.
kernel/power/KconfigThe configuration item CONFIG_SOFTWARE_SUSPEND:
CONFIG_EXPERIMENTAL && CONFIG_PM && CONFIG_SWAPEnable the possibility of suspending the machine. It doesn't need APM. You may suspend your machine by 'swsusp' or 'shutdown -z <time>' (patch for sysvinit needed).
It creates an image which is saved in your active swap. Upon next boot, pass the 'resume=/dev/swappartition' argument to the kernel to have it detect the saved image, restore memory state from it, and continue to run as before. If you do not want the previous state to be reloaded, then use the 'noresume' kernel argument. However, note that your partitions will be fsck'd and you must re-mkswap your swap partitions. It does not work with swap files.
Right now you may boot without resuming and then later resume but in meantime you cannot use those swap partitions/files which were involved in suspending. Also in this case there is a risk that buffers on disk won't match with saved ones.
For more information take a look at Documentation/power/swsusp.txt.
arch/x86_64/KconfigThe configuration item CONFIG_SOFTWARE_SUSPEND:
CONFIG_EXPERIMENTAL && CONFIG_PM && CONFIG_SWAPEnable the possibilty of suspending the machine. It doesn't need APM. You may suspend your machine by 'swsusp' or 'shutdown -z <time>' (patch for sysvinit needed).
It creates an image which is saved in your active swaps. On the next boot, pass the 'resume=/path/to/your/swap/file' option and the kernel will detect the saved image, restore the memory from it, and then continue to run as before you suspended. If you don't want the previous state to continue, use the 'noresume' kernel option. However, note that your partitions will be fsck'd and you must re-mkswap your swap partitions/files.
Right now you may boot without resuming and then later resume but in the meantime you cannot use those swap partitions/files which were involved in suspending. Also in this case there is a risk that buffers on disk won't match with saved ones.
SMP is supported ``as-is''. There's code for it but doesn't work. There have been problems reported relating to SCSI.
This option is close to getting stable. However there is still some absence of features.
For more information take a look at Documentation/power/swsusp.txt.
arch/i386/KconfigThe configuration item CONFIG_SOFTWARE_SUSPEND:
CONFIG_EXPERIMENTAL && CONFIG_PM && CONFIG_SWAPEnable the possibilty of suspendig machine. It doesn't need APM. You may suspend your machine by 'swsusp' or 'shutdown -z <time>' (patch for sysvinit needed).
It creates an image which is saved in your active swaps. By the next booting the, pass 'resume=/path/to/your/swap/file' and kernel will detect the saved image, restore the memory from it and then it continues to run as before you've suspended. If you don't want the previous state to continue use the 'noresume' kernel option. However note that your partitions will be fsck'd and you must re-mkswap your swap partitions/files.
Right now you may boot without resuming and then later resume but in meantime you cannot use those swap partitions/files which were involved in suspending. Also in this case there is a risk that buffers on disk won't match with saved ones.
SMP is supported ``as-is''. There's a code for it but doesn't work. There have been problems reported relating SCSI.
This option is about getting stable. However there is still some absence of features.
For more information take a look at Documentation/swsusp.txt.
Raw data from LKDDb:
(none)This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).
The data is retrived from:
Popular queries:
Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - S index
Automatically generated (in year 2024). See also LKDDb sources on GitLab