From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx202.postini.com [74.125.245.202]) by kanga.kvack.org (Postfix) with SMTP id 4C8CD6B007B for ; Tue, 5 Feb 2013 05:08:10 -0500 (EST) Message-ID: <5110DA06.1000804@imgtec.com> Date: Tue, 5 Feb 2013 10:08:06 +0000 From: James Hogan MIME-Version: 1.0 Subject: Re: next-20130204 - bisected slab problem to "slab: Common constants for kmalloc boundaries" References: <510FE051.7080107@imgtec.com> <0000013ca6a87485-3f013e82-046c-4374-86d5-67fb85a085f9-000000@email.amazonses.com> In-Reply-To: <0000013ca6a87485-3f013e82-046c-4374-86d5-67fb85a085f9-000000@email.amazonses.com> Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Christoph Lameter Cc: linux-next , linux-kernel , Pekka Enberg , Matt Mackall , linux-mm@kvack.org, Stephen Warren On 04/02/13 19:22, Christoph Lameter wrote: > On Mon, 4 Feb 2013, James Hogan wrote: > >> I've hit boot problems in next-20130204 on Meta: > > Meta is an arch that is not in the tree yet? How would I build for meta? Yes (well, it's in -next now, so merging the for-next branch of git://github.com/jahogan/metag-linux.git would add Meta support, which at the point of your commit produces no conflicts). It sounds like Stephen Warren has hit the same problem (in the configuration I'm using ARCH_DMA_MINALIGN was also 64, but in another configuration that worked, ARCH_DMA_MINALIGN was 8 (see arch/metag/include/asm/cache.h). For the record though, to cross compile, you'd need to build a meta2_defconfig of the buildroot at git://github.com/img-meta/metag-buildroot.git. Cheers James -- 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