From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
linux-pm@lists.osdl.org, pavel@suse.cz
Subject: Re: 2.6.21-rc5: swsusp: Not enough free memory
Date: Sun, 01 Apr 2007 20:17:10 +0200 [thread overview]
Message-ID: <460FF726.7090601@gmail.com> (raw)
In-Reply-To: <200703291639.41515.rjw@sisk.pl>
Rafael J. Wysocki napsal(a):
> 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 Priority
>> /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?
Hm, there is some kind of magic.
First, I have fglrx, that taints kernel. If I use vesa drv with X, it
doesn't resume the card. If I try console, it doesn't resume it too.
fglrx + suspend.sf.net seems to work -- 3 unsuccesfull disk >
sys/power/state and after s2dsk with backspace during suspend, disk >
sys/power/state works. But this sceniario happened only once...
Next, it was so early to utter -rc4 is good, it happens there too, so it's
not a regression.
I have no idea what's wrong, is there any possibility to figure out, what
happens (esp. kick fglrx off)? Disable higmem? Try UP?
thanks,
--
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 prev parent reply other threads:[~2007-04-01 18:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-29 7:44 2.6.21-rc5: swsusp: Not enough free memory Jiri Slaby
2007-03-29 14:39 ` Rafael J. Wysocki
2007-03-29 14:39 ` Jiri Slaby
2007-04-01 18:17 ` Jiri Slaby [this message]
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=460FF726.7090601@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