public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: thunder7@xs4all.nl
To: linux-kernel@vger.kernel.org
Subject: 2.2.18pre25: VM: do_try_to_free_pages failed for
Date: Sun, 10 Dec 2000 14:18:30 +0100	[thread overview]
Message-ID: <20001210141830.A692@middle.of.nowhere> (raw)

for almost everything:

Dec 10 13:33:47 middle kernel: VM: do_try_to_free_pages failed for kswapd...
Dec 10 13:33:50 middle kernel: VM: do_try_to_free_pages failed for gdb...
Dec 10 13:33:50 middle last message repeated 9 times
Dec 10 13:33:57 middle kernel: VM: do_try_to_free_pages failed for kswapd...
Dec 10 13:33:59 middle kernel: VM: do_try_to_free_pages failed for gdb...
Dec 10 13:34:04 middle last message repeated 13 times
Dec 10 13:34:05 middle kernel: VM: do_try_to_free_pages failed for init...
Dec 10 13:34:06 middle last message repeated 12 times
Dec 10 13:34:07 middle kernel: VM: do_try_to_free_pages failed for gdb...
Dec 10 13:34:07 middle last message repeated 12 times
Dec 10 13:34:07 middle kernel: VM: do_try_to_free_pages failed for vmware-nmbd...
Dec 10 13:34:07 middle kernel: VM: do_try_to_free_pages failed for cron...
Dec 10 13:34:07 middle last message repeated 2 times
Dec 10 13:34:07 middle kernel: VM: do_try_to_free_pages failed for slrnpull...
Dec 10 13:34:07 middle kernel: VM: do_try_to_free_pages failed for klogd...
Dec 10 13:34:07 middle kernel: VM: do_try_to_free_pages failed for klogd...
Dec 10 13:34:07 middle kernel: VM: do_try_to_free_pages failed for cron...
Dec 10 13:34:08 middle last message repeated 5 times
Dec 10 13:34:09 middle kernel: VM: do_try_to_free_pages failed for gdb...
Dec 10 13:34:22 middle last message repeated 10 times
Dec 10 13:34:22 middle kernel: VM: do_try_to_free_pages failed for slrnpull...
Dec 10 13:34:24 middle last message repeated 2 times
<tried to log in over the network, didn't work, pressed C-A-D and
watched fsck mull over 60+ Gb>

Now it was true I forgot to re-instate the mem=512M line for loadlin,
but even so:
/usr/bin/free:
             total       used       free     shared    buffers     cached
Mem:         63740      56064       7676      22160      23032      17396
-/+ buffers/cache:      15636      48104
Swap:       530104        304     529800

should be enough to run slrnpull and expire a newsspool with about
2,000,000 files, right?

Most messages I was able to dig up about this mentioned 2.2.17 and
suggested upgrading to 2.2.18pre. I didn't think there is anything
changed between 2.2.18pre25 and 2.2.18pre26(2.2.18 to be) in VM
handling, so the problem still seems to persist. What are the
suggestions? Moving to 2.4 is not possible, since the isdn compression
module isdn_lzscomp.o won't work in 2.4.

Greetings,
Jurriaan
-- 
(A)bort, (R)etry, (I)gnore, (V)alium?
GNU/Linux 2.2.18pre25 SMP 2x1117 bogomips load av: 1.05 1.91 1.11
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

             reply	other threads:[~2000-12-10 13:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-10 13:18 thunder7 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-10 19:44 2.2.18pre25: VM: do_try_to_free_pages failed for Szabolcs Szakacsits

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=20001210141830.A692@middle.of.nowhere \
    --to=thunder7@xs4all.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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