From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hugang@soulinfo.com
Subject: Re: 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10)
Date: Thu, 13 Jan 2005 22:22:46 +0100 [thread overview]
Message-ID: <200501132222.46726.rjw@sisk.pl> (raw)
In-Reply-To: <20050113195941.GD2599@openzaurus.ucw.cz>
Hi,
On Thursday, 13 of January 2005 20:59, Pavel Machek wrote:
[-- snip --]
> > > Anyway here's that patch ported to 2.6.10+my_bigdiff (just in case
> > > anyone has the same problem on i386).
> >
> > Has this patch been ported to x86_64? Or is there a newer version of it anywhere,
> > or an alternative?
>
> Was that hugang's patch we were talking about?
Yes.
> Anyway ugly workaround for this is to just try harder to free memory during
> suspend... Just do free_some_memory five times with msleep(200) in between.
I found your patch that added this to free_some_memory(), so I decided I'd try it first.
Then, if "out of memory" problems continue, I'll try the hugang's patch.
Greets,
RJW
--
- 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"
next prev parent reply other threads:[~2005-01-13 21:30 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-24 22:39 Ho ho ho - Linux v2.6.10 Linus Torvalds
2004-12-25 11:11 ` Andrew Walrond
2004-12-25 12:19 ` Alan Cox
2004-12-26 11:30 ` Wichert Akkerman
2004-12-26 13:45 ` R. J. Wysocki
2004-12-26 19:37 ` Pavel Machek
2004-12-26 19:39 ` Pavel Machek
2004-12-26 20:27 ` R. J. Wysocki
2004-12-26 22:10 ` Pavel Machek
2005-01-13 18:09 ` 2.6.10-mm3: swsusp: out of memory on resume (was: Re: Ho ho ho - Linux v2.6.10) Rafael J. Wysocki
2005-01-13 19:59 ` Pavel Machek
2005-01-13 21:22 ` Rafael J. Wysocki [this message]
2005-01-14 14:34 ` hugang
2005-01-14 17:25 ` Rafael J. Wysocki
2005-01-15 21:43 ` Rafael J. Wysocki
2005-01-16 21:51 ` Pavel Machek
2005-01-17 14:53 ` Rafael J. Wysocki
2005-01-17 15:22 ` Pavel Machek
2005-01-18 1:44 ` hugang
[not found] ` <200501150042.35377.rjw@sisk.pl>
2005-01-15 1:21 ` hugang
[not found] ` <200501151147.32919.rjw@sisk.pl>
[not found] ` <200501152220.42129.rjw@sisk.pl>
2005-01-16 5:54 ` hugang
2005-01-16 10:07 ` Rafael J. Wysocki
2005-01-16 14:46 ` hugang
2005-01-17 15:48 ` Rafael J. Wysocki
2005-01-17 16:49 ` Rafael J. Wysocki
2004-12-30 9:58 ` Ho ho ho - Linux v2.6.10 Rafael J. Wysocki
2004-12-26 15:45 ` Alan Cox
2004-12-29 12:44 ` Paolo Ciarrocchi
2004-12-26 2:55 ` Bill Davidsen
2004-12-26 3:36 ` Linus Torvalds
[not found] ` <1104171962.18174.28.camel@d845pe>
2004-12-28 16:38 ` Ho ho ho - Linux v2.6.10 (irq18) Bill Davidsen
2004-12-26 4:19 ` Ho ho ho - Linux v2.6.10 Alexander E. Patrakov
2004-12-26 5:12 ` [PATCH] parport_pc: don't mix module parameter styles Randy.Dunlap
2004-12-26 20:35 ` Ho ho ho - Linux v2.6.10 Greg Norris
2004-12-27 1:31 ` Dmitry Torokhov
2004-12-28 2:36 ` Greg Norris
2004-12-27 16:10 ` Ho ho ho - Linux v2.6.10 (compile stats) John Cherry
2004-12-28 1:04 ` Ho ho ho - Linux v2.6.10 Håkan Lindqvist
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=200501132222.46726.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=hugang@soulinfo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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