From: mru@kth.se (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Cc: acpi-devel@lists.sourceforge.net
Subject: Re: [PM][ACPI] No ACPI interrupts after resume from S1
Date: Mon, 20 Oct 2003 21:08:16 +0200 [thread overview]
Message-ID: <yw1xekx7afrz.fsf@kth.se> (raw)
In-Reply-To: <20031020184750.GA26154@hell.org.pl>
Karol Kozimor <sziwan@hell.org.pl> writes:
>> 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?
>
> Please specify the type of suspend. The situation I described only occurs
> for S1 (or, echo -n standby, more specifically), and only in certain kernel
> versions.
standby, at least.
After echo -n mem > /sys/power/state, the display light won't turn on,
so I don't know what's going on. I've never managed to resume from a
suspend to disk. It just boots normally and makes a fuss about the
filesystems.
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2003-10-20 19:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 14:15 Karol Kozimor
2003-10-20 14:32 ` Måns Rullgård
2003-10-20 18:47 ` Karol Kozimor
2003-10-20 19:08 ` Måns Rullgård [this message]
2003-10-23 8:25 ` Pavel Machek
2003-10-24 9:11 ` Måns Rullgård
2003-10-24 10:24 ` Nick Piggin
2003-10-24 15:14 ` Måns Rullgård
2003-10-24 22:23 ` Pavel Machek
2003-10-24 22:45 ` Måns Rullgård
2003-10-24 23:59 ` Nigel Cunningham
2003-10-25 19:58 ` Pavel Machek
2003-10-25 17:05 ` Måns Rullgård
2003-10-23 8:24 ` Pavel Machek
2003-10-24 15:18 ` Karol Kozimor
2003-10-24 7:52 Yu, Luming
2003-10-26 21:41 ` Karol Kozimor
2003-10-27 8:56 Yu, Luming
2003-10-27 17:02 ` Karol Kozimor
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=yw1xekx7afrz.fsf@kth.se \
--to=mru@kth.se \
--cc=acpi-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®