From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Manish Neema <Manish.Neema@synopsys.com>
Cc: Keith Mannthey <kmannth@gmail.com>, linux-kernel@vger.kernel.org
Subject: RE: System hang problem.
Date: Wed, 04 Oct 2006 01:49:14 +0100 [thread overview]
Message-ID: <1159922954.17553.141.camel@localhost.localdomain> (raw)
In-Reply-To: <C9A861D62D068643A0F4A7B1BCB38E2C0327B5FE@US01WEMBX1.internal.synopsys.com>
Ar Maw, 2006-10-03 am 17:07 -0700, ysgrifennodd Manish Neema:
> Thanks Keith for the response.
>
> My explanation earlier is not clear. The "automount" process dying with
> restrictive overcommit settings is not because of the OOM kill. It looks
> like some bug with "automount" binary itself causing it to exit when it
> could not service a new request.
>
> "cd /remote/something" when the system is out of (allocate'able) memory
> causes the below events (obtained from /var/log/messages)
>
> Oct 3 13:35:32 gentoo036 automount[2060]: handle_packet_missing: fork:
> Cannot allocate memory
> Oct 3 13:35:34 gentoo036 automount[2060]: can't unmount /remote
Your kernel is behaving correctly if it does this in mode 2. You need
more memory or to better set resource limits on what is running.
Alan
next prev parent reply other threads:[~2006-10-04 0:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 0:07 Manish Neema
2006-10-04 0:49 ` Alan Cox [this message]
2006-10-04 3:26 ` Willy Tarreau
2006-10-04 9:53 ` Jarek Poplawski
-- strict thread matches above, loose matches on Subject: below --
2006-10-04 14:24 Al Boldi
2006-10-04 5:44 Manish Neema
2006-10-03 22:07 Manish Neema
2006-10-03 23:35 ` Keith Mannthey
2006-10-04 0:33 ` Alan Cox
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=1159922954.17553.141.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Manish.Neema@synopsys.com \
--cc=kmannth@gmail.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
Powered by JetHome