From: Jiri Slaby <jirislaby@gmail.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.osdl.org, pavel@suse.cz
Subject: 2.6.21-rc5: swsusp: Not enough free memory
Date: Thu, 29 Mar 2007 09:44:11 +0200 [thread overview]
Message-ID: <460B6E4B.3060004@gmail.com> (raw)
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 Priority
/dev/sda6 partition 1004020 0 -1
Any other info needed?
BTW. is this OK on resume?
PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100006, 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/driver
-> ../../../bus/pnp/drivers/i8042 kbd
lrwxrwxrwx 1 root root 0 2007-03-29 09:16 /sys/bus/pnp/devices/00:05/driver
-> ../../../bus/pnp/drivers/i8042 aux
regards,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
Hnus <hnus@fi.muni.cz> is an alias for /dev/null
next reply other threads:[~2007-03-29 7:44 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 7:44 Jiri Slaby [this message]
2007-03-29 14:39 ` 2.6.21-rc5: swsusp: Not enough free memory Rafael J. Wysocki
2007-03-29 14:39 ` Jiri Slaby
2007-04-01 18:17 ` Jiri Slaby
2007-04-01 19:23 ` Rafael J. Wysocki
2007-04-02 8:24 ` Jiri Slaby
2007-04-02 21:18 ` Rafael J. Wysocki
2007-04-03 7:37 ` Jiri Slaby
2007-04-03 10:50 ` Rafael J. Wysocki
2007-04-03 19:59 ` Jiri Slaby
2007-04-09 20:07 ` Jiri Slaby
2007-04-09 20:20 ` Rafael J. Wysocki
2007-04-11 7:36 ` Jiri Slaby
2007-04-11 9:55 ` Rafael J. Wysocki
2007-04-11 10:45 ` Jiri Slaby
2007-04-11 14:40 ` Rafael J. Wysocki
2007-04-11 15:02 ` Jiri Slaby
2007-04-12 21:36 ` Rafael J. Wysocki
2007-04-13 10:14 ` Jiri Slaby
2007-04-13 12:00 ` Rafael J. Wysocki
2007-04-13 12:21 ` Nigel Cunningham
2007-04-13 20:41 ` [RFD] swsusp problem: Drivers allocate much memory during suspend (was: Re: 2.6.21-rc5: swsusp: Not enough free memory) Rafael J. Wysocki
2007-04-13 21:34 ` Nigel Cunningham
2007-04-13 21:40 ` [RFD] swsusp problem: Drivers allocate much memory during suspend Chuck Ebbert
2007-04-13 22:10 ` [RFD] swsusp problem: Drivers allocate much memory during suspend (was: Re: 2.6.21-rc5: swsusp: Not enough free memory) Pavel Machek
2007-04-13 22:34 ` Nigel Cunningham
2007-04-13 22:38 ` [linux-pm] " Pavel Machek
2007-04-13 22:43 ` Nigel Cunningham
2007-04-13 22:35 ` Rafael J. Wysocki
2007-04-13 22:36 ` Nigel Cunningham
2007-04-13 22:40 ` Pavel Machek
2007-04-13 22:45 ` Nigel Cunningham
2007-04-13 22:57 ` Rafael J. Wysocki
2007-04-13 23:03 ` Nigel Cunningham
2007-04-14 9:33 ` Rafael J. Wysocki
2007-04-14 22:53 ` [linux-pm] " Rafael J. Wysocki
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=460B6E4B.3060004@gmail.com \
--to=jirislaby@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@suse.cz \
--cc=rjw@sisk.pl \
/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