linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: balbir@linux.vnet.ibm.com
Cc: Balbir Singh <balbir@in.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: 2.6.23-rc4-mm1 memory controller BUG_ON()
Date: Thu, 13 Sep 2007 13:54:09 -0700	[thread overview]
Message-ID: <1189716849.17236.1712.camel@localhost> (raw)
In-Reply-To: <46E99BDE.9000602@linux.vnet.ibm.com>

On Fri, 2007-09-14 at 01:51 +0530, Balbir Singh wrote:
> Dave Hansen wrote:
> > Looks like somebody is holding a lock while trying to do a
> > mem_container_charge(), and the mem_container_charge() call is doing
> an
> > allocation.  Naughty.
> > 
> > I'm digging into it a bit more, but thought I'd report it, first.
> > 
> 
> Hi, Dave,
> 
> Thanks for reporting this. I sent out a patch to fix this problem
> (suggested by Nick Piggin). The patch is available at
> 
> http://lkml.org/lkml/2007/9/12/113
> 
> Could you try the patch and check if the problem goes away? 

Balbir and I had a chat about this on IRC.  Those patches don't seem to
fix it.  But, I'm getting Balbir hooked up with the kvm instance that I
ran this in along with my .config.

-- Dave

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2007-09-13 20:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 19:34 Dave Hansen
2007-09-13 19:51 ` Dave Hansen
2007-09-13 20:24   ` Balbir Singh
2007-09-13 20:21 ` Balbir Singh
2007-09-13 20:54   ` Dave Hansen [this message]
2007-09-14  8:49     ` Balbir Singh

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=1189716849.17236.1712.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@in.ibm.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.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