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: Mon, 26 Apr 2004 21:22:15 +0100	[thread overview]
Message-ID: <408D6F77.4060303@pointblue.com.pl> (raw)
In-Reply-To: <20040425204506.GG24375@elf.ucw.cz>

Pavel Machek wrote:

>Hi!
>
>  
>
>>>>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).
>>    
>>
>
>Dump stack at time when process refuses to stop, and see why it can't
>be stopped. Then fix that :-).
>					
>
Quite easy to say. I don't really understeand all changes that 've been 
done over mm between 2.6.6-rc2-bk2 and 2.6.5.
But from my tests today, it looks like processes locked (?) in kernel 
are not getting freezed.

Simple example. Mount something over nfs, than disconnect your network 
cable, and inside that dir run ls.
Kernel will not be able to freeze bash !!, obvioulsy bug. I'll try to 
investigate it my self, but if someone can get with fast explanation, to 
enlight me problem, that would be nice.
Nfs is maybe a tougth example. Try i.e. dd bs=1 (to make it slower) 
if=/proc/kmem of=/dev/null,
or even open mc, and press F3 on /proc/kmem, providing that your 
machines is slow.  At that point, MC on my computer eats about  900MB of 
swap ! (I  have only 128MB of ram, so it's quite strange). Anyways,
echo "4" >/proc/acpi/sleep, and kernel will not be able to freeze it.

--
GJ



  reply	other threads:[~2004-04-26 20:22 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
2004-04-25 20:45             ` Pavel Machek
2004-04-26 20:22               ` Grzegorz Piotr Jaskiewicz [this message]
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=408D6F77.4060303@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