From owner-freebsd-arm@FreeBSD.ORG Tue Nov 12 23:41:41 2013 Return-Path: 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 8CACF904; Tue, 12 Nov 2013 23:41:41 +0000 (UTC) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 481B121D5; Tue, 12 Nov 2013 23:41:41 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id rACNfYWa042986; Tue, 12 Nov 2013 18:41:39 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <5282BCAE.1000707@m5p.com> Date: Tue, 12 Nov 2013 18:41:34 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: FreeBSD on HardKernel's ODROID platform References: <106622132.66623.1384225190003.JavaMail.mail@webmail07> <20131112073941.GA19103@mail.bsdpad.com> <52820D9C.8060707@m5p.com> <1384274735.31172.299.camel@revolution.hippie.lan> In-Reply-To: <1384274735.31172.299.camel@revolution.hippie.lan> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Tue, 12 Nov 2013 18:41:39 -0500 (EST) 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Nov 2013 23:41:41 -0000 On 11/12/13 11:45, Ian Lepore wrote: > 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 > Too bad, but thanks for checking. Any other progress on the problem? -- George