From: Samuli Suonpaa <suonpaa@iki.fi>
To: linux-kernel@vger.kernel.org
Subject: 2.4.16: Out of memory - when still more than 100MB free
Date: 17 Dec 2001 23:44:28 +0200 [thread overview]
Message-ID: <87elltwmgz.fsf@puck.erasmus.jurri.net> (raw)
I've got VMWare killed a couple of times mysteriously.
I've got 256MB memory and no swap on my laptop running 2.4.16 and for
some reason VMWare has got killed with the following syslog
information:
Dec 17 23:33:23 puck kernel: Out of Memory: Killed process 28803 (vmware).
Dec 17 23:33:35 puck kernel: Out of Memory: Killed process 28804 (vmware).
Dec 17 23:33:37 puck kernel: /dev/vmmon: Vmx86_ReleaseVM: unlocked pages: 75286, unlocked dirty pages: 51084
What I find odd is, that I am quite certain this machine did _not_ run
out of memory when this happened. Just a few minutes ago I had an idle
VMWare session and started an XEmacs to edit a large file. Just being
curious, I happened to say 'free' a few seconds before VMWare got
killed:
$ free
total used free shared buffers cached
Mem: 256224 219748 36476 0 12956 48816
-/+ buffers/cache: 157976 98248
Swap: 0 0 0
Boom, it died about the same time I exit from XEmacs. After that, I
ran 'free' again:
n$ free
total used free shared buffers cached
Mem: 256224 203644 52580 0 13148 81620
-/+ buffers/cache: 108876 147348
Swap: 0 0 0
I may be missing something obvious herfe, but I just can't figure out
why kernel killes VMWare in this situation.
If anyone's interested, I think I can reproduce this and - if someone
will kindly instruct me a bit - produce some more information. I
_think_ this is the place where experienced kernel hackers start
speaking about running 'vmstat'. And where I usually start having
problems undertanding what it is that people are talking about...
Suonpää...
next reply other threads:[~2001-12-17 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 21:44 Samuli Suonpaa [this message]
2001-12-17 21:10 ` Marcelo Tosatti
2001-12-18 12:18 ` Ville Herva
2001-12-17 22:54 Steve Kieu
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=87elltwmgz.fsf@puck.erasmus.jurri.net \
--to=suonpaa@iki.fi \
--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
all inboxes | Powered by JetHome®