public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: mru-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org (Måns Rullgård)
To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PM][ACPI] No ACPI interrupts after resume from S1
Date: Mon, 20 Oct 2003 16:32:59 +0200	[thread overview]
Message-ID: <yw1x8yngj7xg.fsf@users.sourceforge.net> (raw)
In-Reply-To: 20031020141512.GA30157@hell.org.pl

Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org> writes:

> Suspending and resuming from S1 disables ACPI interrupts for my machine
> (ASUS L3800C laptop). No further interrupts and events are generated,
> /proc/interrupts shows no change w.r. to ACPI. This happens regardless of
> whether the specific IRQ is shared or not.

I've got an Asus M2400E laptop, and have seen similar things.  After a
suspend, the extra buttons (I use them to fire up programs) stop
working.  Normally, they will generate an ACPI event, that is
processed by acpid etc.  After a suspend, each button will work once.
If I then close and open the lid, they will work one more time, and so
on.  Any way I can help?

-- 
Måns Rullgård
mru-iA+eEnwkJgzk1uMJSBkQmQ@public.gmane.org

  reply	other threads:[~2003-10-20 14:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-20 14:15 [PM][ACPI] No ACPI interrupts after resume from S1 Karol Kozimor
2003-10-20 14:32 ` Måns Rullgård [this message]
     [not found]   ` <yw1x8yngj7xg.fsf-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
2003-10-20 18:47     ` Karol Kozimor
2003-10-20 19:08       ` Måns Rullgård
     [not found]         ` <yw1xekx7afrz.fsf-UNjuZkX4dYU@public.gmane.org>
2003-10-23  8:25           ` Pavel Machek
2003-10-24  9:11             ` Måns Rullgård
     [not found]               ` <yw1xr813f1a3.fsf-UNjuZkX4dYU@public.gmane.org>
2003-10-24 10:24                 ` Nick Piggin
2003-10-24 15:14                   ` Måns Rullgård
     [not found]                     ` <yw1xbrs6652m.fsf-UNjuZkX4dYU@public.gmane.org>
2003-10-24 22:23                       ` Pavel Machek
2003-10-24 22:45                         ` Måns Rullgård
     [not found]                           ` <yw1xbrs6p85n.fsf-UNjuZkX4dYU@public.gmane.org>
2003-10-24 23:59                             ` Nigel Cunningham
     [not found]                               ` <1067039997.2114.16.camel-udXHSmD1qAy4CTf7w+cZoA@public.gmane.org>
2003-10-25 19:58                                 ` [PM]No " Pavel Machek
2003-10-25 17:05                         ` [PM][ACPI] No " Måns Rullgård
     [not found]       ` <20031020184750.GA26154-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-10-23  8:24         ` [PM]No " Pavel Machek
     [not found]           ` <20031023082410.GC643-u08AdweFZfgxtPtxi4kahqVXKuFTiq87@public.gmane.org>
2003-10-24 15:18             ` [PM][ACPI] No " Karol Kozimor
  -- strict thread matches above, loose matches on Subject: below --
2003-10-24  7:52 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401720B63-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-10-26 21:41   ` Karol Kozimor
2003-10-27  8:56 Yu, Luming
2003-11-21  1:10 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=yw1x8yngj7xg.fsf@users.sourceforge.net \
    --to=mru-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@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