From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: 2.6.21-rc5: swsusp: Not enough free memory Date: Thu, 29 Mar 2007 16:39:40 +0200 Message-ID: <200703291639.41515.rjw@sisk.pl> References: <460B6E4B.3060004@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <460B6E4B.3060004@gmail.com> Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Jiri Slaby Cc: linux-pm@lists.osdl.org, Linux kernel mailing list List-Id: linux-pm@vger.kernel.org On Thursday, 29 March 2007 09:44, Jiri Slaby wrote: > Hi, > = > I'm getting this while trying to swsups the machine in -rc5, -rc4 is fine: > = > Disabling non-boot CPUs > CPU 1 is now offline > SMP alternatives: switching to UP code > CPU1 is down > swsusp: critical section: > swsusp: Need to copy 131380 pages > swsusp: Not enough free memory > Error -12 suspending > Enabling non-boot CPUs ... > = > # cat /sys/power/resume > 8:6 > # cat /proc/swaps > Filename Type Size Used P= riority > /dev/sda6 partition 1004020 0 -1 > = > Any other info needed? Beats me. There were no changes that could result in such a thing between -rc4 and -rc5, at least not in the swsusp department. Could you please try to bisect? > BTW. is this OK on resume? > PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100= 006, w > iting 100002) > pnp: Failed to activate device 00:04. > pnp: Failed to activate device 00:05. > usbdev5.3_ep00: PM: resume from 0, parent 5-4 still 2 > = > # ll /sys/bus/pnp/devices/00\:0{4,5}/driver > lrwxrwxrwx 1 root root 0 2007-03-29 09:16 /sys/bus/pnp/devices/00:04/driv= er > -> ../../../bus/pnp/drivers/i8042 kbd > lrwxrwxrwx 1 root root 0 2007-03-29 09:16 /sys/bus/pnp/devices/00:05/driv= er > -> ../../../bus/pnp/drivers/i8042 aux Well, I don't think so. Greetings, Rafael