linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@us.ibm.com>
To: Sonny Rao <sonny@burdell.org>
Cc: linuxppc-dev@ozlabs.org, dwg@au1.ibm.com,
	libhugetlbfs-devel@lists.sourceforge.net
Subject: Re: 2.6.19: kernel BUG in hugepd_page at arch/powerpc/mm/hugetlbpage.c:58!
Date: Fri, 12 Jan 2007 13:12:06 -0800	[thread overview]
Message-ID: <20070112211206.GD4982@us.ibm.com> (raw)
In-Reply-To: <20070112204250.GA2290@kevlar.boston.burdell.org>

On 12.01.2007 [15:42:50 -0500], Sonny Rao wrote:
> On Fri, Jan 12, 2007 at 02:08:30PM -0600, Adam Litke wrote:
> > On Fri, 2007-01-12 at 14:57 -0500, Sonny Rao wrote:
> > > (Apologies if this is a re-post)
> > >
> > > Hi, I was running 2.6.19 and running some benchmarks using
> > > libhugetlbfs (1.0.1) and I can fairly reliably trigger this bug:
> >
> > Is this triggered by a libhugetlbfs test case?  If so, which one?
> 
> Ok so the testsuite all passed except for "slbpacaflush" which said
> "PASS (inconclusive)" ... not sure if that is expected or not.

Should be fine.

Thanks,
Nish

-- 
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center

  reply	other threads:[~2007-01-12 21:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12 19:57 2.6.19: kernel BUG in hugepd_page at arch/powerpc/mm/hugetlbpage.c:58! Sonny Rao
2007-01-12 20:08 ` Adam Litke
2007-01-12 20:30   ` Sonny Rao
2007-01-12 21:11     ` Nishanth Aravamudan
2007-01-12 21:28       ` Sonny Rao
2007-01-12 20:42   ` Sonny Rao
2007-01-12 21:12     ` Nishanth Aravamudan [this message]
2007-01-12 22:43     ` [Libhugetlbfs-devel] " David Gibson
2007-01-23  5:10       ` Sonny Rao
2007-01-23  6:18         ` David Gibson
2007-01-23 16:20           ` Adam Litke
2007-01-24  0:35             ` David Gibson
  -- strict thread matches above, loose matches on Subject: below --
2007-01-12 17:24 Sonny Rao

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=20070112211206.GD4982@us.ibm.com \
    --to=nacc@us.ibm.com \
    --cc=dwg@au1.ibm.com \
    --cc=libhugetlbfs-devel@lists.sourceforge.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sonny@burdell.org \
    /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).