public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Grzegorz Piotr Jaskiewicz <gj@pointblue.com.pl>
To: Pavel Machek <pavel@ucw.cz>
Cc: ncunningham@linuxmail.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: swsusp: fix error handling in "not enough swap space"
Date: Sun, 25 Apr 2004 09:51:31 +0100	[thread overview]
Message-ID: <408B7C13.1000708@pointblue.com.pl> (raw)
In-Reply-To: <20040424183505.GB2525@elf.ucw.cz>

Pavel Machek wrote:

>>Second one, starting KDE, and when swap usage != 0 (just to be sure 
>>there is no problem with any assumption), gives me loads of error 
>>messages (see attached file).
>>    
>>
>
>Can you try CONFIG_PREEMPT=n?
>	
>
Funny, now it doesn't run BUG(), but, instead I have two way behavior. 
Either he is complaining that bash
will not stop !! or that there is not enough pages free. Both wrong and 
bizzareus. This really needs fixing before 2.6.6 is out (imo).


1:

Apr 25 09:47:58 nalesnik kernel: Stopping tasks: 
========================================================================
Apr 25 09:47:58 nalesnik kernel:  stopping tasks failed (1 tasks remaining)
Apr 25 09:47:58 nalesnik kernel: Suspend failed: Not all processes stopped!
Apr 25 09:47:58 nalesnik kernel: Restarting tasks...<6> Strange, bash 
not stopped


2:

Apr 25 10:53:52 nalesnik kernel: Stopping tasks: 
=======================================================================|
Apr 25 10:53:52 nalesnik kernel: Freeing memory: ..........|
Apr 25 10:53:52 nalesnik kernel: /critical section: counting pages to 
copy..[nosave pfn 0x44d]........................... (pages needed: 
24493+512=25005 free: 4162)
Apr 25 10:53:52 nalesnik kernel: Suspend Machine: Couldn't get enough 
free pages, on 20843 pages short
Apr 25 10:53:52 nalesnik kernel: Suspend Machine: Suspend failed, trying 
to recover...
Apr 25 10:53:52 nalesnik kernel: blk: queue c6d40e00, I/O limit 4095Mb 
(mask 0xffffffff)
Apr 25 10:53:52 nalesnik kernel: Fixing swap signatures... ok
Apr 25 10:53:52 nalesnik kernel: Restarting tasks... done



--
GJ


  parent reply	other threads:[~2004-04-25  8:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-24  3:17 swsusp: fix error handling in "not enough swap space" Grzegorz Piotr Jaskiewicz
2004-04-24  3:27 ` Nigel Cunningham
2004-04-24  4:04   ` Grzegorz Piotr Jaskiewicz
2004-04-24  4:13     ` Nigel Cunningham
2004-04-24  4:45       ` Grzegorz Piotr Jaskiewicz
2004-04-24 18:35         ` Pavel Machek
2004-04-25  6:48           ` Grzegorz Piotr Jaskiewicz
2004-04-25 20:46             ` Pavel Machek
2004-04-25  8:51           ` Grzegorz Piotr Jaskiewicz [this message]
2004-04-25 20:45             ` Pavel Machek
2004-04-26 20:22               ` Grzegorz Piotr Jaskiewicz
2004-04-26 20:32                 ` Pavel Machek
     [not found]                   ` <408D7555.1000607@pointblue.com.pl>
2004-04-26 20:54                     ` Pavel Machek
2004-04-24 18:32 ` Pavel Machek
2004-04-25  2:53   ` Grzegorz Piotr Jaskiewicz
  -- strict thread matches above, loose matches on Subject: below --
2004-02-29 13:04 Pavel Machek

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=408B7C13.1000708@pointblue.com.pl \
    --to=gj@pointblue.com.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncunningham@linuxmail.com \
    --cc=pavel@ucw.cz \
    /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