Re: 2.6.9-rc2-mm1 swsusp bug report.

[Kevin Fenzi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Nigel" == Nigel Cunningham <ncunningham@xxxxxxxxxxxxx> writes:

Nigel> Hi.  On Sat, 2004-09-25 at 07:09, Kevin Fenzi wrote:
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> >>>>> "Pavel" == Pavel Machek <pavel@xxxxxx> writes:
>> 
Pavel> Hi!
>> >> Was trying to swsusp my 2.6.9-rc2-mm1 laptop tonight. It churned
>> >> for a while, but didn't hibernate. Here are the messages.
>> >> 
>> >>
>> ....................................................................................................
>> >> .........................swsusp: Need to copy 34850 pages Sep 23
>> >> 16:53:37 voldemort kernel: hibernate: page allocation >>
>> failure. order:8, mode:0x120 Sep 23 16:53:37 voldemort kernel:
Pavel> Out of memory... Try again with less loaded system.
>> The system was no more loaded than usual. I have 1GB memory and 4GB
>> of swap defined. I almost never touch swap. It might have been
>> 100mb into the 4Gb of swap when this happened.
>> 
>> What would cause it to be out of memory? swsup needs to be
>> reliable... rebooting when you are using your memory kinda defeats
>> the purpose of swsusp.

Nigel> The problem isn't really that you're out of memory. Rather, the
Nigel> memory is so fragmented that swsusp is unable to get an order 8
Nigel> allocation in which to store its metadata. There isn't really
Nigel> anything you can do to avoid this issue apart from eating
Nigel> memory (which swsusp is doing anyway).

Odd. I have never run into this before with either swsusp2 or
swsusp1. 

What causes memory to be so fragmented? 
Nothing can be done to prevent it?

Nigel> Regards,
Nigel> Nigel

kevin


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFBVM3K3imCezTjY0ERAh75AJ43eMOWlXc2HFQGhTBfgO9G+nI8tACgl7t9
bc6Lo+2guz9WRcu5FhInWMc=
=hunr
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/