From: "Scott T. Smith" <scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Greg Sarjeant <greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>,
"acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: RE: broken power button
Date: Fri, 06 Feb 2004 09:38:48 -0800 [thread overview]
Message-ID: <1076089128.4731.1.camel@tinny.home.foo> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401CBB686-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Fri, 2004-02-06 at 09:17, Yu, Luming wrote:
> > > I applied the patch; I think ACPI should report a warning
> > in this case.
>
> I suspect that patch is not necessary.
>
> IAccording to the description of ACPI spec section 4.7.2.2.1.1
> there should have SCI interrupt triggered by Fixed Power Button.
>
> To verify whether Fixed Power Button works as expected, you
> can just hit power button , and check /proc/interrupts to see whether
> ACPI interrupt number get increased.
My ACPI interrupt number climbs by 8 about once every two seconds (step
function).
if I press the power button with Greg's patch (i.e. force PWRB not
PWRF), it jumps by 2 when I press the button (then another 8 less than
one second later). I also get this in /var/log/acpid:
[Fri Feb 6 09:26:22 2004] received event "button/power PWRB 00000080 00000006"
[Fri Feb 6 09:26:22 2004] executing action "/etc/acpi/default.sh button/power PWRB 00000080 00000006"
[Fri Feb 6 09:26:22 2004] BEGIN HANDLER MESSAGES
[Fri Feb 6 09:26:22 2004] END HANDLER MESSAGES
[Fri Feb 6 09:26:22 2004] action exited with status 0
[Fri Feb 6 09:26:22 2004] completed event "button/power PWRB 00000080 00000006"
without the patch, the power button also causes the # of interrupts to
jump by 2, but I get nothing in /var/log/acpid.
Scott
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-02-06 17:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 17:17 broken power button Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB686-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-06 17:38 ` Scott T. Smith [this message]
[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
-- strict thread matches above, loose matches on Subject: below --
2004-02-11 8:02 Yu, Luming
2004-02-06 2:55 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
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=1076089128.4731.1.camel@tinny.home.foo \
--to=scott-j3vavq9dnb9byusxxbvqtw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@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