From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail202.messagelabs.com (mail202.messagelabs.com [216.82.254.227]) by kanga.kvack.org (Postfix) with ESMTP id 39DBB6B0132 for ; Mon, 21 Sep 2009 05:53:57 -0400 (EDT) Message-ID: <4AB74D16.8050802@kernel.org> Date: Mon, 21 Sep 2009 18:53:26 +0900 From: Tejun Heo MIME-Version: 1.0 Subject: Re: [PATCH 1/3] slqb: Do not use DEFINE_PER_CPU for per-node data References: <1253302451-27740-1-git-send-email-mel@csn.ul.ie> <1253302451-27740-2-git-send-email-mel@csn.ul.ie> <84144f020909200145w74037ab9vb66dae65d3b8a048@mail.gmail.com> <4AB5FD4D.3070005@kernel.org> <4AB5FFF8.7000602@cs.helsinki.fi> <4AB6508C.4070602@kernel.org> <4AB739A6.5060807@in.ibm.com> <20090921084248.GC12726@csn.ul.ie> <4AB740A6.6010008@kernel.org> <20090921094406.GI12726@csn.ul.ie> In-Reply-To: <20090921094406.GI12726@csn.ul.ie> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Mel Gorman Cc: Sachin Sant , Pekka Enberg , Nick Piggin , Christoph Lameter , heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, Andrew Morton , Benjamin Herrenschmidt List-ID: Hello, Mel Gorman wrote: > On Mon, Sep 21, 2009 at 06:00:22PM +0900, Tejun Heo wrote: >> Hello, >> >> Mel Gorman wrote: >>>>> Can you please post full dmesg showing the corruption? >>> There isn't a useful dmesg available and my evidence that it's within the >>> pcpu allocator is a bit weak. >> I'd really like to see the memory layout, especially how far apart the >> nodes are. >> > > Here is the console log with just your patch applied. The node layouts > are included in the log although I note they are not far apart. What is > also important is that the exact location of the bug is not reliable > although it's always in accessing the same structure. This time it was a > bad data access. The time after that, a BUG_ON triggered when locking a > spinlock in the same structure. The third time, it locked up silently. > Forth time, it was a data access error but a different address and so > on. One likely possibility is something accessing wrong percpu offset. Can you please attach .config? Thanks. -- tejun -- 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