All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Thorlton <athorlton@sgi.com>
To: Mel Gorman <mgorman@suse.de>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: mm, numa: test segfaults, only when NUMA balancing is on
Date: Mon, 4 Nov 2013 14:03:46 -0600	[thread overview]
Message-ID: <20131104200346.GA3066@sgi.com> (raw)
In-Reply-To: <20131104145828.GA1218@suse.de>

On Mon, Nov 04, 2013 at 02:58:28PM +0000, Mel Gorman wrote:
> On Wed, Oct 16, 2013 at 10:54:29AM -0500, Alex Thorlton wrote:
> > Hi guys,
> > 
> > I ran into a bug a week or so ago, that I believe has something to do
> > with NUMA balancing, but I'm having a tough time tracking down exactly
> > what is causing it.  When running with the following configuration
> > options set:
> > 
> 
> Can you test with patches
> cd65718712469ad844467250e8fad20a5838baae..0255d491848032f6c601b6410c3b8ebded3a37b1
> applied? They fix some known memory corruption problems, were merged for
> 3.12 (so alternatively just test 3.12) and have been tagged for -stable.

I just finished testing with 3.12, and I'm still seeing the same issue.
This is actually a bit strange to me, because, when I tested with
3.12-rc5 a while back, everything seemed to be ok (see previoues e-mail
in this thread, to Bob Liu).  I guess, embarrasingly enough, I must have
been playing with a screwed up config that day, and managed to somehow
avoid the problem...  Either way, it appears that we still have a
problem here.

I'll poke around a bit more on this in the next few days and see if I
can come up with any more information.  In the meantime, let me know if
you have any other suggestions.

Thanks,

- Alex

> 
> Thanks.
> 
> -- 
> Mel Gorman
> SUSE Labs

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Alex Thorlton <athorlton@sgi.com>
To: Mel Gorman <mgorman@suse.de>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: mm, numa: test segfaults, only when NUMA balancing is on
Date: Mon, 4 Nov 2013 14:03:46 -0600	[thread overview]
Message-ID: <20131104200346.GA3066@sgi.com> (raw)
In-Reply-To: <20131104145828.GA1218@suse.de>

On Mon, Nov 04, 2013 at 02:58:28PM +0000, Mel Gorman wrote:
> On Wed, Oct 16, 2013 at 10:54:29AM -0500, Alex Thorlton wrote:
> > Hi guys,
> > 
> > I ran into a bug a week or so ago, that I believe has something to do
> > with NUMA balancing, but I'm having a tough time tracking down exactly
> > what is causing it.  When running with the following configuration
> > options set:
> > 
> 
> Can you test with patches
> cd65718712469ad844467250e8fad20a5838baae..0255d491848032f6c601b6410c3b8ebded3a37b1
> applied? They fix some known memory corruption problems, were merged for
> 3.12 (so alternatively just test 3.12) and have been tagged for -stable.

I just finished testing with 3.12, and I'm still seeing the same issue.
This is actually a bit strange to me, because, when I tested with
3.12-rc5 a while back, everything seemed to be ok (see previoues e-mail
in this thread, to Bob Liu).  I guess, embarrasingly enough, I must have
been playing with a screwed up config that day, and managed to somehow
avoid the problem...  Either way, it appears that we still have a
problem here.

I'll poke around a bit more on this in the next few days and see if I
can come up with any more information.  In the meantime, let me know if
you have any other suggestions.

Thanks,

- Alex

> 
> Thanks.
> 
> -- 
> Mel Gorman
> SUSE Labs

  reply	other threads:[~2013-11-04 20:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 15:54 BUG: mm, numa: test segfaults, only when NUMA balancing is on Alex Thorlton
2013-10-16 15:54 ` Alex Thorlton
2013-10-17 11:30 ` Bob Liu
2013-10-17 11:30   ` Bob Liu
2013-10-18  0:33   ` Alex Thorlton
2013-10-18  0:33     ` Alex Thorlton
2013-11-04 14:58 ` Mel Gorman
2013-11-04 14:58   ` Mel Gorman
2013-11-04 20:03   ` Alex Thorlton [this message]
2013-11-04 20:03     ` Alex Thorlton
2013-11-06 13:10     ` Mel Gorman
2013-11-06 13:10       ` Mel Gorman
2013-11-07 21:48       ` Alex Thorlton
2013-11-07 21:48         ` Alex Thorlton
2013-11-08 11:20         ` Mel Gorman
2013-11-08 11:20           ` Mel Gorman
2013-11-08 14:08           ` Mel Gorman
2013-11-08 14:08             ` Mel Gorman
2013-11-08 22:13           ` Alex Thorlton
2013-11-08 22:13             ` Alex Thorlton
2013-11-12 21:29             ` Alex Thorlton
2013-11-12 21:29               ` Alex Thorlton
2013-11-15  0:09               ` Mel Gorman
2013-11-15  0:09                 ` Mel Gorman
2013-11-15 14:45                 ` Mel Gorman
2013-11-15 14:45                   ` Mel Gorman
2013-11-22 21:28                   ` Alex Thorlton
2013-11-22 21:28                     ` Alex Thorlton
2013-11-22 23:05                     ` Mel Gorman
2013-11-22 23:05                       ` Mel Gorman
2013-11-23  0:09                       ` Mel Gorman
2013-11-23  0:09                         ` Mel Gorman
2013-11-27 23:58                         ` Alex Thorlton
2013-11-27 23:58                           ` Alex Thorlton
2013-11-07 21:52 ` Alex Thorlton
2013-11-07 21:52   ` Alex Thorlton

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=20131104200346.GA3066@sgi.com \
    --to=athorlton@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    /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.