All of
 help / color / mirror / Atom feed
From: Ka-shu Wong <>
To: "Grover, Andrew" <>
Cc: Nigel Cunningham
	ACPI List
Subject: Re: Re: [Swsusp-devel] ACPI A/C adaptor status not updated upon resume
Date: Sat, 19 Jul 2003 14:13:25 +1000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, Jul 18, 2003 at 04:53:22PM -0700, Grover, Andrew wrote:
> > 000031bd:     Method _PSR (\_SB_.ADP1._PSR)
> > 000031c3:       ArgCount 0; NotSerialized
> > 000031c4:       Return
> > 000031c5:         \_SB_.MEM_.ACST (000002da)
> See, now your system is different from Eric's, which looks like this:
>             Method (_PSR, 0, NotSerialized)
>             {
>                 Return (\_SB.MEM.ACST)
>             }

That's strange, it looks the same to me.

> Basically, I am at a loss as to why Eric's machine would report the
> wrong thing. Whoever is setting that bit in memory isn't doing it
> properly, for some reason. (There could be a lot of reasons. Eric, you
> might try sticking a printk in the memory read function in
> drivers/acpi/osl.c and seeing that we are doing a read from 0x000EE8FF
> and what the value is.)

I believe what's happening is that software suspend is somehow saving 
the ACPI state on suspend, and after resume the state from before 
suspend (which is no longer valid) is restored.

If the ACPI state is stored in kernel memory, then this makes sense.

So, my question (to the swsusp people) is whether it is possible to stop
swsusp from restoring the old (invalid) ACPI state; and
(to the ACPI people) is whether it is possible to reset the ACPI
subsystem in some way.

- KS

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-19  4:13 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 [this message]
     [not found]     ` <>
2003-07-19  4:54       ` Nigel Cunningham
     [not found]         ` <>
2003-07-21  2:31           ` Eric Altendorf
  -- 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.