From: Sachin Sant <sachinp@in.ibm.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [OOPS] hugetlbfs tests with 2.6.30-rc8-git1
Date: Fri, 05 Jun 2009 21:18:50 +0530 [thread overview]
Message-ID: <4A293E62.4090700@in.ibm.com> (raw)
In-Reply-To: <20090605150429.GA29614@csn.ul.ie>
Mel Gorman wrote:
> That patch fixes a different problem. The assertion shouldn't have been
> made for hugetlbfs regions. I can only assume we are not triggering the
> same problem. According to your .config, DEBUG_VM is not even set so
> this is some other problem.
>
> Do you know what line triggered the problem? Eric Munson is currently
> investigating this as I'm chasing down another bug but my understanding is that
> right now he can't reproduce the problem. How reproducible is this for you?
I cannot recreate this consistently. Sometimes i am able to recreate ,
but it's random. I have
seen this problem on 2 out of 4 power boxes.
Here are last few lines from the hugetlbfs test run.
get_huge_pages (32): PASS
get_huge_pages (64): PASS
quota (32): PASS
quota (64): PASS
counters (32): PASS
counters (64): PASS
mmap-gettest 10 20 (32): PASS
mmap-gettest 10 20 (64): PASS
mmap-cow 19 20 (32): PASS
mmap-cow 19 20 (64): PASS
set shmmax limit to 335544320
shm-fork 10 10 (32): PASS
shm-fork 10 10 (64): PASS
shm-fork 10 20 (32):
shm-fork was executed when the oops occurred.
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-06-05 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 11:29 [OOPS] hugetlbfs tests with 2.6.30-rc8-git1 Sachin Sant
2009-06-05 15:04 ` Mel Gorman
2009-06-05 15:48 ` Sachin Sant [this message]
2009-06-05 20:17 ` Benjamin Herrenschmidt
2009-06-06 19:51 ` Sachin Sant
2009-06-14 11:38 ` Sachin Sant
2009-06-15 0:56 ` Michael Ellerman
2009-06-15 1:38 ` Stephen Rothwell
2009-06-15 13:00 ` Sachin Sant
2009-06-15 21:26 ` Benjamin Herrenschmidt
2009-06-16 1:30 ` Benjamin Herrenschmidt
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=4A293E62.4090700@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.