All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wes Janzen <superchkn@sbcglobal.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: ACPI Power Button Event problems(?)
Date: Thu, 07 Aug 2003 20:29:03 -0500	[thread overview]
Message-ID: <3F32FCDF.9000903@sbcglobal.net> (raw)
In-Reply-To: <1060285317.3351.7.camel@litshi.luna.local>

I did the cat /proc/acpi/event shortly after implementing my script and 
finding out it was continually being called after pressing the power 
button.  I got/(still get):
button/power PWRF 00000080 00000001
...
button/power PWRF 00000080 00006bbb
... etc.

Of course, with 2.6.0-test1-mm2, it would stop when I restarted acpid or 
pushed the power button again.  With 2.6.0-test2-mm1 that has changed in 
that stopping the events requires a reboot.

I can recompile my 2.4.18 with ACPI support and see what happens if that 
is necessary...just let me know.

Thanks.

Micha Feigin wrote:

>On Thu, 2003-08-07 at 09:51, Wes Janzen wrote:
>  
>
>>I'm having an interesting, and relatively benign problem with ACPI 
>>events.  I downloaded the ACPI daemon from SourceForge and with 
>>2.6.0-test1-mm2 when I pressed the power button, ACPI would be deluded 
>>with PWRF events until I pushed the button again or acpid was 
>>restarted.  That's easy enough to work around, but with 2.6.0-test2-mm1 
>>the events never stop.  Restarting the daemon makes no difference, nor 
>>does pushing the button have any effect.  That wouldn't be too big of a 
>>problem if I was using the power button to restart the PC, but I'm using 
>>the event to kill sawfish since it likes locking up (and disregarding 
>>any keyboard input) leaving me with no recourse but to press the reset 
>>button otherwise.  So, it works great for the first lockup, but I can't 
>>reset the power button event so I'm stuck with the reset button on the 
>>second round.  Unless I want to reboot, which I'd rather not. 
>>
>>Is this a bug in 2.6.0-test2-mm1 or was the bug the fact it could be 
>>cancelled in 2.6.0-test1-mm2?
>>
>>Thanks,
>>
>>-Wes-
>>
>>-
>>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>the body of a message to majordomo@vger.kernel.org
>>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>Please read the FAQ at  http://www.tux.org/lkml/
>>    
>>
>
>I am guessing that it is not a bug in acpid since stop it didn't help.
>You could try a
>cat /proc/acpi/event
>to make sure that you are actually getting these events no stop.
>I am guessing that it is a faulty dsdt since you got the same the
>behavior on the different kernel.
>Can you tell if this also happens with 2.4 kernel?
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/
>
>  
>


      reply	other threads:[~2003-08-08  1:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07  6:51 ACPI Power Button Event problems(?) Wes Janzen
2003-08-07 19:41 ` Micha Feigin
2003-08-08  1:29   ` Wes Janzen [this message]

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=3F32FCDF.9000903@sbcglobal.net \
    --to=superchkn@sbcglobal.net \
    --cc=linux-kernel@vger.kernel.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 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.