From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id 2E1F0DE15F for ; Tue, 4 Mar 2008 07:44:50 +1100 (EST) Subject: Re: [BUG/RFC/PATCH] drm: Fix for non-coherent DMA PowerPC From: Benjamin Herrenschmidt To: Gerhard Pircher In-Reply-To: <20080303195117.7040@gmx.net> References: <20071125234254.B4405DDE49@ozlabs.org> <20080302110505.175270@gmx.net> <1204490829.15052.482.camel@pasglop> <20080302223012.90210@gmx.net> <1204498569.15052.488.camel@pasglop> <20080303195117.7040@gmx.net> Content-Type: text/plain Date: Tue, 04 Mar 2008 07:44:11 +1100 Message-Id: <1204577051.21545.12.camel@pasglop> Mime-Version: 1.0 Cc: airlied@linux.ie, linuxppc-dev@ozlabs.org, dri-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org Reply-To: benh@kernel.crashing.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Mon, 2008-03-03 at 20:51 +0100, Gerhard Pircher wrote: > > Remove the GFP_HIGHMEM from the above. It looks like our cache > > flushing isn't going to work for highmem, it would need some > > kmap's for that. > Yes, it looks like this was the problem. No kernel oops anymore. > The machine locks up anyway (which is a well known hardware problem). > It doesn't lock up with CPPIOMode=true, but probably only because the > initialization of DRI fails with "BAD cp_mode (f0000000)!". Damn, I wonder why you insist trying to make that machine work :-) The hardware is just totally busted. Ben.