From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Jani-Matti Hätinen" <jani-matti.hatinen-X3B1VOXEql0@public.gmane.org>
Cc: acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
venkatesh.pallipadi-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [Acpi4asus-user] Asus S5000: Problems with Suspend-to-RAM
Date: Sun, 15 Jan 2006 00:06:48 +0100 [thread overview]
Message-ID: <20060114230647.GA12613@hell.org.pl> (raw)
In-Reply-To: <200601142257.46188.jani-matti.hatinen-X3B1VOXEql0@public.gmane.org>
Thus wrote Jani-Matti Hätinen:
> I have an Asus S5000 laptop and I have some problems with Suspend-to-RAM on
> it.
> The laptop goes into suspend just fine, but on resume it immediately
> switches to runlevel 0 and goes down.
You're getting spurious power button events, and since your acpid is
configured to shut the system down on power button press, that's exactly
what happens. Turn off acpid and try again or work it around in your
scripts.
BTW: This bug has been present since at least 2.5.7x, reported a couple of
times, even tracked (http://bugme.osdl.org/show_bug.cgi?id=3525 is the only
one I can find now, but I'm sure there are more). In spite of that, it
occurs on every single machine I tested for S3. And contrary to what the
comments on #3525 say, it's definitely not a userspace issue, because the
power button event is sent *regardless* what triggered the wake-up, be it a
keypress, lid event, one of the ACPI-controlled buttons or RTC alarm.
Should I just reopen #3525 (it says Toshiba?) or file a new one?
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2006-01-14 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601142257.46188.jani-matti.hatinen@iki.fi>
[not found] ` <200601142257.46188.jani-matti.hatinen-X3B1VOXEql0@public.gmane.org>
2006-01-14 23:06 ` Karol Kozimor [this message]
[not found] ` <20060114230647.GA12613-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2006-01-14 23:28 ` [Acpi4asus-user] Asus S5000: Problems with Suspend-to-RAM John H.
[not found] ` <5b9417770601141528h77410d57g9c9b6dbcbb2df72f-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-01-15 0:07 ` John H.
[not found] ` <5b9417770601141607l6912c3f3wb160c29142b216e4-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2006-01-15 1:03 ` Karol Kozimor
[not found] ` <20060115010337.GA6244-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2006-01-15 1:08 ` John H.
[not found] ` <200601151518.30358.jani-matti.hatinen@iki.fi>
[not found] ` <200604252205.53022.jani-matti.hatinen@iki.fi>
2006-06-10 8:55 ` [Acpi4asus-user] Asus S5000: Problems with Suspend-to-RAM (almost solved) Jani-Matti Hätinen
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=20060114230647.GA12613@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=jani-matti.hatinen-X3B1VOXEql0@public.gmane.org \
--cc=linux-acpi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=venkatesh.pallipadi-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