public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David John <davidjon@xenontk.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	linux-kernel@vger.kernel.org, Jonathan Miles <jon@cybus.co.uk>,
	penberg@cs.helsinki.fi
Subject: Re: OOM kernel behaviour
Date: Wed, 02 Dec 2009 10:54:20 +0530	[thread overview]
Message-ID: <4B15FA04.2020206@xenontk.org> (raw)
In-Reply-To: <20091202132026.5C55.A69D9226@jp.fujitsu.com>

On 12/02/2009 09:59 AM, KOSAKI Motohiro wrote:
> Proprietary module is loaded.

That's the Broadcom wireless wl driver. It isn't causing the problem.

> 
> Probably, some program in your system leaked memory.
> 

Is there some way to find out? I tried to analyse top and ps output
but there isn't anything that stands out.

Regards,
David.

  reply	other threads:[~2009-12-02  5:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 17:38 OOM kernel behaviour Jonathan Miles
2009-11-30 18:57 ` Christoph Lameter
2009-12-01  9:57   ` Jonathan Miles
2009-12-01 13:21     ` Jonathan Miles
2009-12-01 16:08     ` Christoph Lameter
2009-12-01 18:07       ` Jonathan Miles
2009-12-01 18:42         ` Christoph Lameter
2009-12-04 20:36         ` OOM kernel behaviour - 2.6.32 Jonathan Miles
2009-12-09 13:52           ` Jonathan Miles
2009-12-01 15:35 ` OOM kernel behaviour David John
2009-12-01 16:07   ` Christoph Lameter
2009-12-01 17:10     ` David John
2009-12-01 17:26       ` Christoph Lameter
2009-12-02 15:55         ` Mel Gorman
2009-12-07  5:34           ` David John
2009-12-07 14:59             ` Mel Gorman
2009-12-08  3:41               ` David John
2009-12-01 17:32       ` Christoph Lameter
2009-12-02  3:17         ` David John
2009-12-02  4:29       ` KOSAKI Motohiro
2009-12-02  5:24         ` David John [this message]
2009-12-02  5:31           ` KOSAKI Motohiro

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=4B15FA04.2020206@xenontk.org \
    --to=davidjon@xenontk.org \
    --cc=cl@linux-foundation.org \
    --cc=jon@cybus.co.uk \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /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