From owner-freebsd-arm@FreeBSD.ORG  Tue Nov 12 16:45:48 2013
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 45C10CDA
 for <freebsd-arm@FreeBSD.org>; Tue, 12 Nov 2013 16:45:48 +0000 (UTC)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 1D6302B71
 for <freebsd-arm@FreeBSD.org>; Tue, 12 Nov 2013 16:45:47 +0000 (UTC)
Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52]
 helo=damnhippie.dyndns.org)
 by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256)
 (Exim 4.72) (envelope-from <ian@FreeBSD.org>)
 id 1VgH5w-000OdL-69; Tue, 12 Nov 2013 16:45:40 +0000
Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240])
 by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id rACGja4D070956;
 Tue, 12 Nov 2013 09:45:36 -0700 (MST) (envelope-from ian@FreeBSD.org)
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 24.8.230.52
X-Report-Abuse-To: abuse@dyndns.com (see
 http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse
 reporting information)
X-MHO-User: U2FsdGVkX1/IPUEI8Dptg2So+dID3t/R
Subject: Re: FreeBSD on HardKernel's ODROID platform
From: Ian Lepore <ian@FreeBSD.org>
To: George Mitchell <george+freebsd@m5p.com>
In-Reply-To: <52820D9C.8060707@m5p.com>
References: <106622132.66623.1384225190003.JavaMail.mail@webmail07>
 <20131112073941.GA19103@mail.bsdpad.com>  <52820D9C.8060707@m5p.com>
Content-Type: text/plain; charset="us-ascii"
Date: Tue, 12 Nov 2013 09:45:35 -0700
Message-ID: <1384274735.31172.299.camel@revolution.hippie.lan>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port 
Content-Transfer-Encoding: 7bit
Cc: freebsd-arm@FreeBSD.org
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.16
Precedence: list
List-Id: Porting FreeBSD to the StrongARM Processor <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Nov 2013 16:45:48 -0000

On Tue, 2013-11-12 at 06:14 -0500, George Mitchell wrote:
> On 11/12/13 02:39, Ruslan Bukin wrote:
> > [...]
> > We suspect that uboot sets incorrect values for cpu clocks
> > and/or voltage regulators. In result we have prefetch abort
> > after first interrupt received.
> > [...]
> 
> Could this be connected to the persistent prefetch abort problem I've
> been having in my Raspberry Pi?                    -- George Mitchell

I suspected the same thing on my wandboard with the wrong-endian
prefetch abort problem, and noticed that u-boot was violating some of
the imx6 rules for voltage regulation, so with great hopes for a fix I
added some code to the freebsd early kernel init to increase the voltage
slightly and get all 3 regulators in range with each other according to
what the manual said... it didn't help.

-- Ian