public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@suse.cz>
Cc: linux-pm@lists.osdl.org, "Yu, Luming" <luming.yu@intel.com>,
	Andrew Morton <akpm@zip.com.au>,
	ACPI devel <acpi-devel@lists.sourceforge.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Re: swsusp: Not enough free pages
Date: Wed, 8 Jun 2005 23:42:13 +0200	[thread overview]
Message-ID: <200506082342.14420.rjw@sisk.pl> (raw)
In-Reply-To: <20050608162728.GA3969@openzaurus.ucw.cz>

Hi,

On Wednesday, 8 of June 2005 18:27, Pavel Machek wrote:
> Hi!
> 
]--snip--[
> > 
> > This is the worst result from the second box:
> > 
> > Freeing memory...  done (54641 pages freed)
> > Freeing memory...  done (0 pages freed)
> > Freeing memory...  done (5120 pages freed)
> > Freeing memory...  done (1952 pages freed)
> > Freeing memory...  done (2304 pages freed)
> > 
> > Still, there are 5x more pages freed in the first pass (80% of RAM was
> > empty anyway before suspend), and usually it is 10-20x more or so.
> 
> I have seen 0 freed on i386 machine with preempt -rc6-mm1, today...
> Something is definitely wrong there.

Well, I have compiled the kernel with preempt and retested (on -rc6) but it
doesn't want to get worse. :-)

The problem seems to be arch-dependent or at least configuration-dependent ... 

Hm, how much RAM is there in your box?

Rafael


-- 
- Would you tell me, please, which way I ought to go from here?
- That depends a good deal on where you want to get to.
		-- Lewis Carroll "Alice's Adventures in Wonderland"

  reply	other threads:[~2005-06-08 21:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-24 16:05 swsusp: Not enough free pages Yu, Luming
2005-05-24 16:55 ` Stefan Seyfried
     [not found]   ` <20050525012040.GA6145@linux.sh.intel.com>
2005-05-30  9:14     ` Yu, Luming
2005-05-30 15:01       ` Pavel Machek
     [not found]         ` <20050530150157.GC2207-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-05-30 17:01           ` James Sparenberg
2005-06-06  6:39         ` Yu, Luming
2005-06-06 10:39           ` [linux-pm] " Pavel Machek
     [not found]             ` <20050606103936.GA2520-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-06-06 17:02               ` Rafael J. Wysocki
2005-06-06 17:14                 ` Pavel Machek
2005-06-06 21:46                   ` Rafael J. Wysocki
2005-06-06 21:58                     ` Pavel Machek
     [not found]                       ` <20050606215815.GO2230-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-06-07 10:39                         ` [linux-pm] " Rafael J. Wysocki
     [not found]                           ` <200506071239.10125.rjw-KKrjLPT3xs0@public.gmane.org>
2005-06-08 15:02                             ` Rafael J. Wysocki
2005-06-08 16:27                               ` Pavel Machek
2005-06-08 21:42                                 ` Rafael J. Wysocki [this message]
2005-06-08 22:03                                   ` Pavel Machek

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=200506082342.14420.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=luming.yu@intel.com \
    --cc=pavel@suse.cz \
    /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