Hi, On Friday 14 April 2006 07:33, Nigel Cunningham wrote: > On Friday 14 April 2006 00:28, Felix Kuehling wrote: > > On Tue, 2006-11-04 at 14:14 +1000, Nigel Cunningham wrote: > > > Hi. > > > > > > On Tuesday 11 April 2006 12:35, Sanjoy Mahajan wrote: > > > > > if(acpi_during_suspend_resume) > > > > > don't generate power button event to confuse user space daemon > > > > > > > > This patch might be useful useful in setting and unsetting > > > > acpi_during_suspend_resume (and also using it, but you should ignore > > > > those as they are hacks for a different problem). The equivalent > > > > variable in the patch below is acpi_in_suspend. > > > > > > If you want this to get wider testing, I'll be happy to include it in the > > > Suspend2 patchset. > > > > Just to clarify, software suspend is not affected by this problem. Only > > S3, possibly S1 and maybe S4BIOS are affected, though I've never seen > > the latter on any real system. > > Thanks. I still think it would be worth including, because Suspend2 (and now > uswsusp, I believe) lets you choose what to do after writing the image. One > of the options is suspending to ram, so that you effectively get disk-backed > suspend to ram. It might be useful in this situation. Yes we support suspend-to-disk-and-RAM now, so it may be useful to us too. Greetings, Rafael - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
