From: Dave Jones <davej@redhat.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Christoph Lameter <cl@linux.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sasha Levin <sasha.levin@oracle.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: bad page state in 3.13-rc4
Date: Thu, 19 Dec 2013 15:30:10 -0500 [thread overview]
Message-ID: <20131219203010.GB14519@redhat.com> (raw)
In-Reply-To: <20131219201158.GT11295@suse.de>
On Thu, Dec 19, 2013 at 08:11:58PM +0000, Mel Gorman wrote:
> Dave, was this a NUMA machine?
It's a dual core i5-4670T with hyperthreading.
> If yes, was CONFIG_NUMA_BALANCING set?
no.
> Dave, when this this
> bug start triggering? If it's due to a recent change in trinity, can you
> check if 3.12 is also affected? If not, can you check if the bug started
> happening somewhere around these commits?
Right now it can take hours for it to reproduce. Until I can narrow it down to
something repeatable, bisecting and trying old builds is going to be really time-consuming.
Given the other VM bugs that have Sasha and I have been finding since I added
the mmap reuse code to trinity, this is probably something else that has been
there for a while.
> A few bad state bugs have shown up on linux-mm recently but my impression
> was that they were related to rmap_walk changes currently in next. The
> initial log indicated that this was 3.13-rc4 but is it really 3.13-rc4 or
> are there any -next patches applied?
no, just rc4 (plus a handful of small patches to fix oopses etc that I've already
diagnosed). I'm glad Sasha spends time running this stuff on -next, because
there aren't enough hours in the day for me to look at the stuff I find
in Linus' tree without looking at what's coming next.
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>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Mel Gorman <mgorman@suse.de>
Cc: Christoph Lameter <cl@linux.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sasha Levin <sasha.levin@oracle.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: bad page state in 3.13-rc4
Date: Thu, 19 Dec 2013 15:30:10 -0500 [thread overview]
Message-ID: <20131219203010.GB14519@redhat.com> (raw)
In-Reply-To: <20131219201158.GT11295@suse.de>
On Thu, Dec 19, 2013 at 08:11:58PM +0000, Mel Gorman wrote:
> Dave, was this a NUMA machine?
It's a dual core i5-4670T with hyperthreading.
> If yes, was CONFIG_NUMA_BALANCING set?
no.
> Dave, when this this
> bug start triggering? If it's due to a recent change in trinity, can you
> check if 3.12 is also affected? If not, can you check if the bug started
> happening somewhere around these commits?
Right now it can take hours for it to reproduce. Until I can narrow it down to
something repeatable, bisecting and trying old builds is going to be really time-consuming.
Given the other VM bugs that have Sasha and I have been finding since I added
the mmap reuse code to trinity, this is probably something else that has been
there for a while.
> A few bad state bugs have shown up on linux-mm recently but my impression
> was that they were related to rmap_walk changes currently in next. The
> initial log indicated that this was 3.13-rc4 but is it really 3.13-rc4 or
> are there any -next patches applied?
no, just rc4 (plus a handful of small patches to fix oopses etc that I've already
diagnosed). I'm glad Sasha spends time running this stuff on -next, because
there aren't enough hours in the day for me to look at the stuff I find
in Linus' tree without looking at what's coming next.
Dave
next prev parent reply other threads:[~2013-12-19 22:08 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 4:07 bad page state in 3.13-rc4 Dave Jones
2013-12-19 4:07 ` Dave Jones
2013-12-19 4:40 ` Linus Torvalds
2013-12-19 4:40 ` Linus Torvalds
2013-12-19 15:41 ` Christoph Lameter
2013-12-19 15:41 ` Christoph Lameter
2013-12-19 20:11 ` Mel Gorman
2013-12-19 20:11 ` Mel Gorman
2013-12-19 20:30 ` Dave Jones [this message]
2013-12-19 20:30 ` Dave Jones
2013-12-19 15:53 ` Dave Jones
2013-12-19 15:53 ` Dave Jones
2013-12-19 17:07 ` Linus Torvalds
2013-12-19 17:07 ` Linus Torvalds
2013-12-19 17:17 ` Dave Jones
2013-12-19 17:17 ` Dave Jones
2013-12-19 18:11 ` Kent Overstreet
2013-12-19 18:11 ` Kent Overstreet
2013-12-19 18:29 ` Benjamin LaHaise
2013-12-19 18:29 ` Benjamin LaHaise
2013-12-19 18:35 ` Dave Jones
2013-12-19 18:35 ` Dave Jones
2013-12-19 19:19 ` Linus Torvalds
2013-12-19 19:19 ` Linus Torvalds
2013-12-19 19:26 ` Benjamin LaHaise
2013-12-19 19:26 ` Benjamin LaHaise
2013-12-19 19:45 ` Linus Torvalds
2013-12-19 19:45 ` Linus Torvalds
2013-12-19 19:53 ` Benjamin LaHaise
2013-12-19 19:53 ` Benjamin LaHaise
2013-12-19 20:02 ` Linus Torvalds
2013-12-19 20:11 ` Linus Torvalds
2013-12-19 20:31 ` Benjamin LaHaise
2013-12-19 20:31 ` Benjamin LaHaise
2013-12-19 20:31 ` Linus Torvalds
2013-12-19 20:31 ` Linus Torvalds
2013-12-19 20:42 ` Benjamin LaHaise
2013-12-19 20:42 ` Benjamin LaHaise
2013-12-19 20:24 ` Dave Jones
2013-12-19 20:24 ` Dave Jones
2013-12-19 23:38 ` Benjamin LaHaise
2013-12-19 23:38 ` Benjamin LaHaise
2013-12-20 1:00 ` Dave Jones
2013-12-20 1:00 ` Dave Jones
2013-12-21 23:06 ` [PATCHes - aio / migrate page, please review] " Benjamin LaHaise
2013-12-21 23:06 ` Benjamin LaHaise
2013-12-22 19:09 ` Linus Torvalds
2013-12-22 19:09 ` Linus Torvalds
2013-12-22 21:30 ` Dave Jones
2013-12-22 21:30 ` Dave Jones
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=20131219203010.GB14519@redhat.com \
--to=davej@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=sasha.levin@oracle.com \
--cc=torvalds@linux-foundation.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 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.