From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f180.google.com (mail-qc0-f180.google.com [209.85.216.180]) by kanga.kvack.org (Postfix) with ESMTP id B8C7A6B0031 for ; Thu, 19 Dec 2013 17:08:27 -0500 (EST) Received: by mail-qc0-f180.google.com with SMTP id w7so1542466qcr.39 for ; Thu, 19 Dec 2013 14:08:27 -0800 (PST) Received: from mx1.redhat.com (mx1.redhat.com. [209.132.183.28]) by mx.google.com with ESMTP id cq5si1813567qcb.53.2013.12.19.14.08.23 for ; Thu, 19 Dec 2013 14:08:24 -0800 (PST) Date: Thu, 19 Dec 2013 15:30:10 -0500 From: Dave Jones Subject: Re: bad page state in 3.13-rc4 Message-ID: <20131219203010.GB14519@redhat.com> References: <20131219040738.GA10316@redhat.com> <20131219201158.GT11295@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131219201158.GT11295@suse.de> Sender: owner-linux-mm@kvack.org List-ID: To: Mel Gorman Cc: Christoph Lameter , Linus Torvalds , Sasha Levin , Joonsoo Kim , Andrew Morton , "Kirill A. Shutemov" , Hugh Dickins , Linux Kernel , linux-mm 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: email@kvack.org