linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Haren Myneni <hmyneni@gmail.com>
Cc: srikar@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, aneesh.kumar@linux.vnet.ibm.com,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: mm: BUG_ON with NUMA_BALANCING (kernel BUG at include/linux/swapops.h:131!)
Date: Thu, 14 May 2015 10:33:04 +0100	[thread overview]
Message-ID: <20150514093304.GS2462@suse.de> (raw)
In-Reply-To: <CACgMoiK61mKYFpfhhK51uvkvFHK3k+Dz4peMnbeW7-npDu4XBQ@mail.gmail.com>

On Wed, May 13, 2015 at 01:17:54AM -0700, Haren Myneni wrote:
> Hi,
> 
>  I am getting BUG_ON in migration_entry_to_page() with 4.1.0-rc2
> kernel on powerpc system which has 512 CPUs (64 cores - 16 nodes) and
> 1.6 TB memory. We can easily recreate this issue with kernel compile
> (make -j500). But I could not reproduce with numa_balancing=disable.
> 

Is this patched in any way? I ask because line 134 on 4.1.0-rc2 does not
match up with a BUG_ON. It's close to a PageLocked check but I want to
be sure there are no other modifications.

Otherwise, when was the last time this worked? Was 4.0 ok? As it can be
easily reproduced, can the problem be bisected please?

-- 
Mel Gorman
SUSE Labs

  reply	other threads:[~2015-05-14  9:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-13  8:17 mm: BUG_ON with NUMA_BALANCING (kernel BUG at include/linux/swapops.h:131!) Haren Myneni
2015-05-14  9:33 ` Mel Gorman [this message]
2015-05-14 15:48   ` Haren Myneni
2015-05-18  7:32     ` Haren Myneni
2015-05-18  8:11       ` Mel Gorman
2015-05-18  8:18         ` Haren Myneni

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=20150514093304.GS2462@suse.de \
    --to=mgorman@suse.de \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=hmyneni@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=srikar@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).