From: Dhaval Giani <dhaval@linux.vnet.ibm.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
htejun@gmail.com, gregkh@suse.de,
Srivatsa Vaddagiri <vatsa@linux.vnet.ibm.com>,
Balbir Singh <balbir@in.ibm.com>,
maneesh@linux.vnet.ibm.com, lkml <linux-kernel@vger.kernel.org>,
stable@kernel.org, linux-mm@kvack.org
Subject: Re: 2.6.22-stable causes oomkiller to be invoked
Date: Fri, 28 Dec 2007 15:41:09 +0530 [thread overview]
Message-ID: <20071228101109.GB5083@linux.vnet.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712271119030.30555@schroedinger.engr.sgi.com> <Pine.LNX.4.64.0712261258050.16862@schroedinger.engr.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Thu, Dec 27, 2007 at 11:22:34AM -0800, Christoph Lameter wrote:
> On Thu, 27 Dec 2007, Dhaval Giani wrote:
>
> > anything specific you are looking for? I still hit the oom.
>
> Weird.... WTH is this? You run an unmodified upstream tree? Can you add a
> printk in quicklist_trim that shows
>
Hi,
I am running 2.6.24-rc5-mm1 here.
> A) that it is called
>
> B) what the control values q->nr_pages and min_pages are?
>
Trying to print these using printks renders the system unbootable. With
help from RAS folks around me, managed to get a systemtap script,
probe kernel.statement("quicklist_trim@mm/quicklist.c:56")
{
printf(" q->nr_pages is %d, min_pages is %d ----> %s\n",
$q->nr_pages, $$
min_pages, execname());
}
we managed to get your required information. Last 10,000 lines are
attached (The uncompressed file comes to 500 kb).
Hope it helps.
Thanks,
--
regards,
Dhaval
[-- Attachment #2: systp.out.1.bz2 --]
[-- Type: application/x-bzip2, Size: 7600 bytes --]
next prev parent reply other threads:[~2007-12-28 10:12 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 12:33 2.6.22-stable causes oomkiller to be invoked Dhaval Giani
2007-12-13 13:23 ` Dhaval Giani
2007-12-13 15:18 ` Dhaval Giani
2007-12-13 16:29 ` Greg KH
2007-12-13 16:46 ` Dhaval Giani
2007-12-13 17:54 ` Dhaval Giani
2007-12-14 14:41 ` Tejun Heo
2007-12-14 15:47 ` Dhaval Giani
2007-12-14 15:54 ` Tejun Heo
2007-12-14 16:16 ` Dhaval Giani
2007-12-14 17:50 ` Andrew Morton
2007-12-14 18:28 ` Dhaval Giani
2007-12-14 23:05 ` Andrew Morton
2007-12-15 3:52 ` Dhaval Giani
2007-12-15 6:00 ` Andrew Morton
2007-12-15 10:44 ` Dhaval Giani
[not found] ` <20071217045904.GB31386@linux.vnet.ibm.com>
[not found] ` <Pine.LNX.4.64.0712171143280.12871@schroedinger.engr.sgi.com>
[not found] ` <20071217120720.e078194b.akpm@linux-foundation.org>
[not found] ` <Pine.LNX.4.64.0712171222470.29500@schroedinger.engr.sgi.com>
2007-12-21 4:45 ` Dhaval Giani
2007-12-26 21:01 ` Christoph Lameter
[not found] ` <Pine.LNX.4.64.0712271119030.30555@schroedinger.engr.sgi.com>
2007-12-28 10:11 ` Dhaval Giani [this message]
2008-01-02 20:45 ` Christoph Lameter
2008-01-02 21:54 ` Christoph Lameter
2008-01-03 3:59 ` Dhaval Giani
2008-01-03 4:16 ` Dhaval Giani
2008-01-03 21:04 ` Christoph Lameter
2008-01-07 20:04 ` Christoph Lameter
2008-01-08 4:33 ` Dhaval Giani
2007-12-30 14:01 ` Ingo Molnar
2007-12-30 19:24 ` Dhaval Giani
2008-01-02 20:48 ` Christoph Lameter
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=20071228101109.GB5083@linux.vnet.ibm.com \
--to=dhaval@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@in.ibm.com \
--cc=clameter@sgi.com \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=maneesh@linux.vnet.ibm.com \
--cc=stable@kernel.org \
--cc=vatsa@linux.vnet.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).