All of
 help / color / mirror / Atom feed
From: Eric Altendorf <>
To: "Grover,
	Andrew" <>,
	ACPI List
Subject: Re: Re: [Swsusp-devel] ACPI A/C adaptor status not updated	upon resume
Date: Sun, 20 Jul 2003 19:31:21 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Friday 18 July 2003 21:54, Nigel Cunningham wrote:
> Hi.
> Yes, swsusp will be storing the ACPI state (along with all the rest
> of memory). Swsusp has no way to tell whether the state is invalid
> or not, or to exclude arbitrary parts of the memory from the image
> (particularly since we're probably not talking about a whole page
> here). The easiest way to overcome this problem at the moment is to
> make sure the state is the same when you resume as it is when you
> suspend. Failing that, a DSDT override that does the right thing.
> Does unplugging and plugging in the power post resume get the BIOS
> to set things right?

Yes, but only if the post is live, which generally isn't the case when 
this problem pops up. :-)


This email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here:

  parent reply	other threads:[~2003-07-21  2:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-18 23:53 Re: [Swsusp-devel] ACPI A/C adaptor status not updated upon resume Grover, Andrew
     [not found] ` <>
2003-07-19  4:13   ` Ka-shu Wong
     [not found]     ` <>
2003-07-19  4:54       ` Nigel Cunningham
     [not found]         ` <>
2003-07-21  2:31           ` Eric Altendorf [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-07-19  0:01 Grover, Andrew
2003-07-17 20:49 Grover, Andrew
     [not found] ` <>
2003-07-18 23:38   ` Ka-shu Wong
     [not found]     ` <>
2003-07-19  1:20       ` Gabor FLEISCHER
     [not found]         ` <>
2003-07-19  3:46           ` Ka-shu Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.