mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mahmood Naderan <nt_mahmood@yahoo.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: running of out memory => kernel crash
Date: Tue, 9 Aug 2011 00:17:39 -0700 (PDT)	[thread overview]
Message-ID: <1312874259.89770.YahooMailNeo@web111704.mail.gq1.yahoo.com> (raw)
In-Reply-To: <1db776d865939be598cdb80054cf5d93.squirrel@xenotime.net>

>Do you have any kernel log panic/oops/Bug messages?
 
Actually, that happened for one my diskless nodes 10 days ago.
What I saw on the screen (not the logs), was 
"running out of memory.... kernel panic....."

I have not defined any swap partition for diskless nodes. Only the server 
has such partition. 

If you think that is an odd behavior, please let me know what will happen 
exactly when an application needs more memory but there is no room 
left and swap is disabled.
  

// Naderan *Mahmood;


----- Original Message -----
From: Randy Dunlap <rdunlap@xenotime.net>
To: Mahmood Naderan <nt_mahmood@yahoo.com>; linux-mm@kvack.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Sent: Tuesday, August 9, 2011 11:36 AM
Subject: Re: running of out memory => kernel crash

On Mon, August 8, 2011 11:53 pm, Mahmood Naderan wrote:
> Hi
> I have noticed that when the swap is disabled
>
> (either via swapoff or not defining any swap partition),
>
> then running out of memory can cause a kernel panic. 
>
> I wonder why the hungry application won't be killed
>
> upon a request for a resource that is not available?
> In that case, the problematic application will be killed
> only but what we see now is that the whole system is
> crashed.

Do you have any kernel log panic/oops/Bug messages?

[adding linux-mm mailing list]


-- 
~Randy

  reply	other threads:[~2011-08-09  7:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-09  6:53 Mahmood Naderan
2011-08-09  7:06 ` Randy Dunlap
2011-08-09  7:17   ` Mahmood Naderan [this message]
2011-08-09 16:03     ` David Rientjes
2011-08-10  8:14       ` Mahmood Naderan
2011-08-11  4:09         ` David Rientjes
2011-08-11  7:07           ` Mahmood Naderan
2011-08-11  7:13             ` David Rientjes
2011-08-11  8:02               ` Mahmood Naderan
2011-08-11 12:47                 ` Denys Vlasenko
2011-08-11 15:13                   ` Mahmood Naderan
2011-08-11 17:38                     ` Denys Vlasenko
2011-08-17  8:50                       ` Mahmood Naderan
2011-08-18  2:18                       ` Pavel Ivanov
2011-08-18 12:44                         ` Denys Vlasenko
2011-08-18 14:26                           ` Pavel Ivanov
2011-08-18 22:25                             ` Denys Vlasenko
2011-08-19 19:21                               ` David Rientjes
2011-08-19 19:29                             ` Bryan Donlan
2011-08-19 21:19                               ` Chris Friesen
2011-08-19 21:38                                 ` 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=1312874259.89770.YahooMailNeo@web111704.mail.gq1.yahoo.com \
    --to=nt_mahmood@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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®