From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Linux kernel <linux-kernel@vger.kernel.org>
Subject: bug?: strange behaviour with memory hogs and 2.6.9-rc3
Date: Fri, 01 Oct 2004 16:49:45 -0600 [thread overview]
Message-ID: <415DDF09.8030703@nortelnetworks.com> (raw)
I'm running 2.6.9-rc3 with 2GB of ram.
I've got a test app that loops allocating chunks of memory 60 pages at a time,
scribbles on each page, and mlock()s it, for a total of about a gig and a half.
It then sleeps for 100 seconds, and exits.
I ran one instance fine.
I ran the second instance, and userspace locked up. The machine still responds
to pings, but no userspace stuff works.
It's been about 10 minutes, and userspace still hasn't come back.
Obviously I'm out of memory, but I would have expected that the oom killer would
wake up or something.
Anyone have any ideas?
Chris
reply other threads:[~2004-10-01 22:52 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=415DDF09.8030703@nortelnetworks.com \
--to=cfriesen@nortelnetworks.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