From owner-freebsd-arm@FreeBSD.ORG Fri Jan 24 01:01:05 2014 Return-Path: Delivered-To: freebsd-arm@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DFA9BCD2; Fri, 24 Jan 2014 01:01:05 +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 9519B1102; Fri, 24 Jan 2014 01:01:05 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id s0O10wnq058953; Thu, 23 Jan 2014 20:01:03 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <52E1BB4A.1040807@m5p.com> Date: Thu, 23 Jan 2014 20:00:58 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Ian Lepore Subject: Re: Raspberry Pi: still getting prefetch aborts References: <52BB73B4.5030000@m5p.com> <52D5D0F8.9050205@m5p.com> <1389794207.1230.27.camel@revolution.hippie.lan> <52D72ABC.4080502@m5p.com> In-Reply-To: <52D72ABC.4080502@m5p.com> 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]); Thu, 23 Jan 2014 20:01:04 -0500 (EST) Cc: "freebsd-arm@freebsd.org" X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jan 2014 01:01:05 -0000 On 01/15/14 19:41, George Mitchell wrote: > On 01/15/14 08:56, Ian Lepore wrote: >> [...] >> I've been consistantly unable to reproduce the userland crash you see on >> rpi, even though the tracebacks and all make it look a lot like the >> wrong-endian kernel crashes I see on Wandboard (although my gut tells me >> it's not really the same problem). My setup is a lot like yours, with >> nfs-mounted filesystems, but when I build ports that way it either works >> fine, or the port builds die for other reasons. >> >> -- Ian >> [...] It's definitely because my /usr/ports directory was NFS-mounted by the automounter. When I just do fixed NFS mounts via /etc/fstab, I don't get the prefetch aborts any more. Don't ask me why automounts vs. static mounts should make any difference here ... -- George