Re: [PATCH] swsuspend breakage in 2.6.17-git

[Shaohua Li <shaohua.li@intel.com>]

On Sun, 2006-06-25 at 09:46 -0700, Linus Torvalds wrote:
> 
> On Sun, 25 Jun 2006, Daniel Ritz wrote:
> > 
> > commit b6370d96e09944c6e3ae8d5743ca8a8ab1f79f6c:
> > 	[PATCH] swsusp: i386 mark special saveable/unsaveable pages
> > breaks swsusp for me with a page fault in kernel/power/snapshot.c:save_arch_mem()
> > 
> > the following patch makes suspend-resume working again, but some
> > problems still remain: fan goes on and stays on after resume (same as
> > in bug #5000). i guess this is a due to a change in ACPI which i still
> > have to track down along with the problem that acpi is not powering-off
> > my other laptop anymore...
> > 
> > comments?
> 
> Looking at that whole commit, it looks bogus.
> 
> The rule about ACPI memory (whether NVS or not) according to what I have 
> seen is that the OS is _not_ supposed to touch that memory except through 
> ACPI routines.
> 
> So saving and restoring those pages sounds really really wrong in the 
> first place. We have no idea what current state it could screw up.
Below is from ACPI spec 3.0 (p405). From my understanding, OS should
save/restore NVS memory ?

ACPI Non-Volatile-Sleeping Memory (NVS). Memory identified by the BIOS
as being reserved by the BIOS for its use. OSPM is required to tag this
memory as cacheable, and to save and restore its image before entering
an S4 state. Except as directed by control methods, OSPM is not allowed
to use this physical memory. OSPM will call the _PTS control method some
time before entering a sleeping state, to allow the platforms AML code
to update this memory image before entering the sleeping state. After
the system awakes from an S4 state, OSPM will restore this memory area
and call the _WAK control method to enable the BIOS to reclaim its
memory image.

Thanks,
Shaohua