Hi. On Fri, 2007-04-13 at 14:00 +0200, Rafael J. Wysocki wrote: > > > > Shrinking memory... Pages needed: 128103 normal, 0 highmem > > Pages needed: 125226 normal, 0 highmem > > Pages needed: -5757 normal, 0 highmem > > Pages needed: -5757 normal, 0 highmem > > Pages needed: -5757 normal, 0 highmem > > Pages needed: -5757 > > Pages needed: 127953 normal, 0 highmem > > Pages needed: 125076 normal, 0 highmem > > Pages needed: -6043 normal, 0 highmem > > Pages needed: -6043 normal, 0 highmem > > Pages needed: -6043 normal, 0 highmem > > Pages needed: -6043 > > done (200 pages freed) > > Freed 800 kbytes in 0.16 seconds (5.00 MB/s) > > Suspending console(s) > > ... > > CPU1 is down > > swsusp: critical section: > > swsusp: Need to copy 131358 pages > > swsusp: Normal pages needed: 131358 > > swsusp: Normal pages needed: 131358 + 1024 + 22, available pages: 130607 > > Well, it looks like someone allocated about 6000 pages after we had freed > enough memory for suspending. We have a tunable allowance in Suspend2 for this, because fglrx allocates a lot of pages in its suspend routine if DRI is enabled. I think some other drivers do too, but fglrx is the main one I know. Nigel
Attachment:
signature.asc
Description: This is a digitally signed message part
- Follow-Ups:
- References:
- Re: 2.6.21-rc5: swsusp: Not enough free memory
- From: "Rafael J. Wysocki" <[email protected]>
- Re: 2.6.21-rc5: swsusp: Not enough free memory
- From: "Jiri Slaby" <[email protected]>
- Re: 2.6.21-rc5: swsusp: Not enough free memory
- From: "Rafael J. Wysocki" <[email protected]>
- Re: 2.6.21-rc5: swsusp: Not enough free memory
- Prev by Date: Re: [PATCH 0/13] maps: pagemap, kpagemap, and related cleanups
- Next by Date: Re: [CRYPTO] is it really optimized ?
- Previous by thread: Re: 2.6.21-rc5: swsusp: Not enough free memory
- Next by thread: [RFD] swsusp problem: Drivers allocate much memory during suspend (was: Re: 2.6.21-rc5: swsusp: Not enough free memory)
- Index(es):
 |