diff options
| author | Matthew Garrett <mjg@redhat.com> | 2010-05-28 16:32:15 -0400 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2010-06-10 11:03:15 -0400 |
| commit | 2a6b69765ad794389f2fc3e14a0afa1a995221c2 (patch) | |
| tree | 63c22656f682ba94cdeb882ee370966af57f41c9 /arch | |
| parent | dd4c4f17d722ffeb2515bf781400675a30fcead7 (diff) | |
| download | linux-stable-2a6b69765ad794389f2fc3e14a0afa1a995221c2.tar.gz linux-stable-2a6b69765ad794389f2fc3e14a0afa1a995221c2.tar.bz2 linux-stable-2a6b69765ad794389f2fc3e14a0afa1a995221c2.zip | |
ACPI: Store NVS state even when entering suspend to RAM
https://bugzilla.kernel.org/show_bug.cgi?id=13931 describes a bug where
a system fails to successfully resume after the second suspend. Maxim
Levitsky discovered that this could be rectified by forcibly saving
and restoring the ACPI non-volatile state. The spec indicates that this
is only required for S4, but testing the behaviour of Windows by adding
an ACPI NVS region to qemu's e820 map and registering a custom memory
read/write handler reveals that it's saved and restored even over suspend
to RAM. We should mimic that behaviour to avoid other broken platforms.
Signed-off-by: Matthew Garrett <mjg@redhat.com>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'arch')
0 files changed, 0 insertions, 0 deletions