public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Johan Vromans <jvromans@squirrel.nl>
To: linux-acpi@vger.kernel.org
Subject: Re: Acer smart battery: acpi_sbs and linux-2.6.17
Date: Wed, 28 Jun 2006 11:43:50 +0200	[thread overview]
Message-ID: <m23bdpeht5.fsf@phoenix.squirrel.nl> (raw)
In-Reply-To: <44A1AF40.3020701@rrz.uni-koeln.de> (Berthold Cogel's message of "Wed, 28 Jun 2006 00:20:48 +0200")

Berthold Cogel <cogel@rrz.uni-koeln.de> writes:

>> But I seem to have lost the ability to hibernate/resume. I consistently
>> get "swsusp: not enough free memory". Does 2.6.17 take so much more
>> memory than 2.6.16?
>
> For my System it's only about 1 MB difference in runlevel 1 with
> 2.6.17.1 compared with 2.6.16.20.

I've gone back to 2.6.16, and didn't notice a significant difference
in 'free' figures so the size increment is probably neglectible.
But I can only hibernate when I stop X first, while with 2.6.16 I'm
could hibernate with a fully loaded (X, WM, Emacs, Xterms) system.

BTW I hibernate with 

  cd /sys/power; echo shutdown > disk; echo disk > state

I don't use the pm-hibernate program (doesn't seem to make a
difference, except that I cannot choose a kernel upon boot).

> But I'm using suspend to disk with suspend2.

I've been told that swsusp2 and swsusp share the same memory
limitation: at least half of the memory must be freeable for suspend
to be able to continue. But it could be a problem with swsusp that it
somehow isn't able to free enough memory.

Since 2.6.16 swsusp does everything I need, I never tried swsusp2.
Last time I looked it seemed work in fast progress, much like a moving
target. Besides I'd like to stick as closely as possible to my
standard Fedora kernel so I can still use the prebuilt kernel modules.

-- Johan

      reply	other threads:[~2006-06-28  9:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25 23:14 Acer smart battery: acpi_sbs and linux-2.6.17 Berthold Cogel
2006-06-27 10:07 ` Johan Vromans
2006-06-27 15:17   ` Johan Vromans
2006-06-27 22:20     ` Berthold Cogel
2006-06-28  9:43       ` Johan Vromans [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=m23bdpeht5.fsf@phoenix.squirrel.nl \
    --to=jvromans@squirrel.nl \
    --cc=linux-acpi@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