From: Sachin Sant <sachinp@in.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linuxppc-dev@ozlabs.org, linux-next@vger.kernel.org
Subject: Re: Next July 29 : Hugetlb test failure (OOPS free_hugepte_range)
Date: Wed, 05 Aug 2009 21:03:44 +0530 [thread overview]
Message-ID: <4A79A658.8000105@in.ibm.com> (raw)
In-Reply-To: <E0A64FA0-C835-4361-A203-E9CB5377599C@kernel.crashing.org>
Kumar Gala wrote:
>
> On Jul 29, 2009, at 10:04 AM, Sachin Sant wrote:
>
>> While executing hugetlb tests against today's Next tree on
>> a Power 6 box came across following OOPS.
>
> out of interest what tests are you running for hugetlb?
The one maintained at : http://libhugetlbfs.ozlabs.org/ which points
to the sourceforge libhugetlbfs project.
Latest release can be downloaded from sourceforge using
http://sourceforge.net/projects/libhugetlbfs/files/
I am using version 2.5
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: Sachin Sant <sachinp@in.ibm.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linuxppc-dev@ozlabs.org
Subject: Re: Next July 29 : Hugetlb test failure (OOPS free_hugepte_range)
Date: Wed, 05 Aug 2009 21:03:44 +0530 [thread overview]
Message-ID: <4A79A658.8000105@in.ibm.com> (raw)
In-Reply-To: <E0A64FA0-C835-4361-A203-E9CB5377599C@kernel.crashing.org>
Kumar Gala wrote:
>
> On Jul 29, 2009, at 10:04 AM, Sachin Sant wrote:
>
>> While executing hugetlb tests against today's Next tree on
>> a Power 6 box came across following OOPS.
>
> out of interest what tests are you running for hugetlb?
The one maintained at : http://libhugetlbfs.ozlabs.org/ which points
to the sourceforge libhugetlbfs project.
Latest release can be downloaded from sourceforge using
http://sourceforge.net/projects/libhugetlbfs/files/
I am using version 2.5
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
next prev parent reply other threads:[~2009-08-05 15:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 7:36 linux-next: Tree for July 29 Stephen Rothwell
2009-07-29 15:04 ` Next July 29 : Hugetlb test failure (OOPS free_hugepte_range) Sachin Sant
2009-07-29 15:04 ` Sachin Sant
2009-07-30 12:25 ` Sachin Sant
2009-07-30 12:30 ` Benjamin Herrenschmidt
2009-08-05 10:43 ` Sachin Sant
2009-08-06 3:52 ` Benjamin Herrenschmidt
2009-08-06 4:40 ` Sachin Sant
2009-08-05 14:35 ` Kumar Gala
2009-08-05 14:35 ` Kumar Gala
2009-08-05 15:33 ` Sachin Sant [this message]
2009-08-05 15:33 ` Sachin Sant
2009-07-30 12:05 ` [PATCH] next-20090730 lguest build breaks with pfn_pmd() Kamalesh Babulal
[not found] ` <20090730120533.GB4955-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2009-07-30 23:19 ` Rusty Russell
2009-07-30 23:19 ` Rusty Russell
2009-07-31 18:03 ` Randy Dunlap
2009-08-03 8:28 ` [RESEND-PATCH] " Kamalesh Babulal
2009-08-03 23:21 ` [PATCH] " Rusty Russell
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=4A79A658.8000105@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=galak@kernel.crashing.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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.