From: Pavel Machek <pavel-AlSwsSmVLrQ@public.gmane.org>
To: Ow Mun Heng <ow.mun.heng-Sjgp3cTcYWE@public.gmane.org>
Cc: "Acpi-List (E-mail)"
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: 2.6.5-rc2-mm5 + Suspend
Date: Fri, 2 Apr 2004 22:47:13 +0200 [thread overview]
Message-ID: <20040402204713.GG195@elf.ucw.cz> (raw)
In-Reply-To: <C386328088ED7F4E9F81AFBABDDF60DA04A930D1-Yw6hFe9C1vnHQcBQSaPqJq0fmWJ9l57d0E9HWUfgJXw@public.gmane.org>
Hi!
> I used to run 2.6.3 and suspend to disk works fine. Yesterday night
> I tinkered with 2.6.5-rc2-mm5 and tried suspend to disk. It failed and hung.
>
> since the messages were not logged into syslog, all I can remember is
> somthing
> about preempt being the issue. Note that I didn't make any significant
> changes in
> my .config.
>
> I'm not sure if it's a pmdisk/suspend issue or ACPI.
>
> Let me know if I should post more details or I should seek help in
> swsuspend list.
swsusp list is probably not the right place (it deals with
swsusp2). There are some bad interactions between new vm and
swsusp. Look for Andrea Arcangeli's mails on lkml.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
prev parent reply other threads:[~2004-04-02 20:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-01 1:38 2.6.5-rc2-mm5 + Suspend Ow Mun Heng
[not found] ` <C386328088ED7F4E9F81AFBABDDF60DA04A930D1-Yw6hFe9C1vnHQcBQSaPqJq0fmWJ9l57d0E9HWUfgJXw@public.gmane.org>
2004-04-02 20:47 ` Pavel Machek [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=20040402204713.GG195@elf.ucw.cz \
--to=pavel-alswssmvlrq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ow.mun.heng-Sjgp3cTcYWE@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