public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Sarjeant <greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>
To: "Scott T. Smith" <scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org>
Cc: "acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: broken power button
Date: Fri, 06 Feb 2004 07:46:21 -0500	[thread overview]
Message-ID: <1076071581.5785.15.camel@localhost> (raw)
In-Reply-To: <1076044045.4744.10.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>

On Fri, 2004-02-06 at 00:07, Scott T. Smith wrote:
> I applied the patch; I think ACPI should report a warning in this case. 
> According to p63, there are 2 bits of information (4 choices) but only 2
> legal possibilities.  Windows must be ignoring the PWR_BUTTON field and
> just checking for the existance of PWRB.  ACPI should complain if
> PWR_BUTTON is not set and PWRB exists, or if PWR_BUTTON is set and PWRB
> doesn't exist.
> 
> Similarly, if SLP_BUTTON is not set and SLPB exists, ACPI should throw a
> warning too.
> 
You're probably right.  I am hopeful that we can find a more robust
solution to the problem. This is an admittedly sloppy (and hopefully
temporary) workaround that just saves me the trouble of commenting out
those three whole lines of code in future kernels. :)

> Unfortunately, while this lets me receive PWRB notifications, it doesn't
> solve the lockup on suspend.  Ugh.
> 
Ah, drat. For what it's worth, I have similar issues with suspend,
though I haven't tried suspending to RAM for a while, which was when I
saw the behavior you describe. I have been able to suspend to disk from
a console, and others have reported doing so from unaccelerated X. I've
never managed to resume successfully from X, however.

Greg



-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn

  parent reply	other threads:[~2004-02-06 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06  2:55 broken power button Scott T. Smith
     [not found] ` <1076036158.4792.12.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06  3:33   ` Greg Sarjeant
     [not found]     ` <1076038435.5849.8.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-02-06  5:07       ` Scott T. Smith
     [not found]         ` <1076044045.4744.10.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06 12:46           ` Greg Sarjeant [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06 17:17 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB686-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-06 17:38   ` Scott T. Smith
     [not found]     ` <1076089128.4731.1.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06 17:53       ` greg
2004-02-06 17:53   ` Scott T. Smith
2004-02-11  8:02 Yu, Luming

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=1076071581.5785.15.camel@localhost \
    --to=greg-qniyhhqvzb9kr2e5yswmoq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox