mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mudeem Siddiqui" <mudeem@quartics.com>
To: <linux-kernel@vger.kernel.org>
Subject: VM: killing process - How to identify the problem
Date: Tue, 20 May 2008 14:10:31 -0700	[thread overview]
Message-ID: <87A697E50899F541B77272C331CEB74401746058@exchange.Q-DOMAIN> (raw)

Hi all, 

I have linux 2.4.25 on a mips processor. Other than my application, the
other processes that are running on the system are udhcpd, dhcpd,
mini_dns etc. The applicaiton is quite memory intensive, it has
allocated 5 MB of a buffer which acts as a queue and the applicaiton
queues and de-queues packets in the queue at frequents intervals. The
memory for this buffer is allocated just once when the application
starts at the time of boot. So I would assume that there would be quite
a lot of paging going on. 

The issue is that randomly the application gets killed, there is no
segmnetation fault or anything and if I look at /var/log/messages I see
quite a lot of 

__alloc_pages: 0-order allocation failed 
__alloc_pages: 0-order allocation failed 
__alloc_pages: 0-order allocation failed 


and then 

VM: killing process 

I have read that the application can be killed if the kernel is not able
to service the paging request or oom-killer can also kill the process.
How can I confirm that one of these is happening? I want to identify the
root cause of the application crash before experimenting like increasing
the swap space or even disable the oom-killer (i don't know if that
would be a good idea though). Any suggestions 

Thanks 
Mudeem 

             reply	other threads:[~2008-05-20 21:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 21:10 Mudeem Siddiqui [this message]
2008-05-21  7:44 ` Jiri Slaby
2008-05-21 19:30   ` Mudeem Siddiqui

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=87A697E50899F541B77272C331CEB74401746058@exchange.Q-DOMAIN \
    --to=mudeem@quartics.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

all inboxes | Powered by JetHome®