From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iy0-f179.google.com (mail-iy0-f179.google.com [209.85.210.179]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 0546EB70E3 for ; Thu, 3 Feb 2011 08:55:56 +1100 (EST) Received: by iye19 with SMTP id 19so445967iye.38 for ; Wed, 02 Feb 2011 13:55:54 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <1296682842.2349.730.camel@pasglop> References: <1296682842.2349.730.camel@pasglop> Date: Wed, 2 Feb 2011 15:55:53 -0600 Message-ID: Subject: Re: BootX From: kevin diggs To: Benjamin Herrenschmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: linuxppc-dev@lists.ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Ben, I know you are VERY busy. I appreciate your taking the time to reply. Since I'm am still using this thing I'll take a stab at trying to track it down. I just posted the FYI to see if I could trigger some thoughts (like your post). With a 4.3.5 compiled mesh, it fails a lot of early stuff like getting cache info? I don't remember the full list because it fails to find the root fs and does the reboot in 180 seconds thing (I still have in a back corner of my brain the serial console xmon boot stuff and will probably eventually try that). I am hopeful that since it (at least so far) always fails that it might not be THAT bad to track down. That coupled with some knowledge of what the compilers are doing differently can hopefully help track it down. Thanks! kevin On Wed, Feb 2, 2011 at 3:40 PM, Benjamin Herrenschmidt wrote: > > That's interesting... That driver is really nasty, we probably have a > bug in it that's exposed by optimizations done by more recent compilers > but it's not going to be trivial to figure out I'm afraid. I at least > have very dim memories of mesh and how it operates... > > One thing to be careful of with Mesh is that the DMA engine, while > supposedly cache coherent, has shown in the past to have issues when > DMA'ing to unaligned memory locations. This shouldn't be a problem with > normal block transfers but we may have to be careful with things like > inquiry, mode pages, sense requests etc... > > Ben. >