From: Michal Jaegermann <michal@harddata.com>
To: linux-kernel@vger.kernel.org
Subject: vm in 2.2.18pre23 - behaving worse
Date: Fri, 24 Nov 2000 00:40:13 -0700 [thread overview]
Message-ID: <20001124004013.A8944@mail.harddata.com> (raw)
I was busy with other things and did not track 2.2.18pre kernels very
carefuly, but now I tried 2.2.18pre23 on Alpha and got an impression
that a situation with a virtual memory handling is worse than it was,
say, in 2.2.18pre15. I can now see in /var/log/messages entries like
"VM: killing process sh" or "VM: killing process emacs" because I was
compiling a kernel. This does not happen consistently, predictably, or
very often but it does happen and I should not be oom. Nothing else
crashes, or leaves any traces in log files, and a machine continues
apparently not disturbed, but a process is gone.
Applying patches from Andrea and the one from Rik, posted some week
ago under "blindingly stupid 2.2 VM bug" subject, does not seem
to help very much. Sigh!
Am I isolated in this experience?
Michal
-
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-11-24 8:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20001124004013.A8944@mail.harddata.com \
--to=michal@harddata.com \
--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