From owner-freebsd-arm@freebsd.org Tue May 3 03:21:39 2016 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4410BB2B994 for ; Tue, 3 May 2016 03:21:39 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [69.239.235.194]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0D0D01A71 for ; Tue, 3 May 2016 03:21:38 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id u433LdZD096935 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 3 May 2016 03:21:40 GMT (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id u433LcQY096934; Mon, 2 May 2016 20:21:38 -0700 (PDT) (envelope-from fbsd) Date: Mon, 2 May 2016 20:21:38 -0700 From: bob prohaska To: Ulrich Grey Cc: freebsd-arm@freebsd.org Subject: Re: CUBOX crashes during port build Message-ID: <20160503032138.GR71221@www.zefox.net> References: <20160502093349.bd3a2e060b81dbb8d65c5ee0@ulrich-grey.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160502093349.bd3a2e060b81dbb8d65c5ee0@ulrich-grey.de> User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 May 2016 03:21:39 -0000 On Mon, May 02, 2016 at 09:33:49AM +0200, Ulrich Grey wrote: > I am running 11-CURRENT r297692 (snapshot cubox-hummingboard 20160408). > After some hours building print/texlive-full the CUBOX crashed. > > Fatal kernel mode data abort: 'Translation Fault (L2)' on read Not sure it's related, but 'Translation fault (L2)' on read is probably the most common single crash message I've seen on RPI2. However, compiling software, even world builds, haven't triggered it in many months. > > trapframe: 0xfb57b778 > > FSR=00000007, FAR=0000004d, spsr=20000013 > > r0 =00000000, r1 =00000001, r2 =00000003, r3 =00000001 > > r4 =c460f370, r5 =c7bc0460, r6 =00000001, r7 =00000000 > > r8 =00000000, r9 =c26c4230, r10=00000000, r11=fb57b828 > > r12=c2937000, ssp=fb57b808, slr=c2521e30, pc =c2539504 > > On today's RPI2 crash it reported: root@www:~ # Fatal kernel mode data abort: 'Translation Fault (L2)' on read trapframe: 0xed518e10 FSR=00000007, FAR=00000000, spsr=00000013 r0 =00000000, r1 =00000000, r2 =00000000, r3 =00000000 r4 =00000000, r5 =00000000, r6 =00000000, r7 =00000000 r8 =00000000, r9 =00000000, r10=00000000, r11=00000000 r12=00000000, ssp=ed518ea0, slr=00000000, pc =00000000 [ thread pid 16417 tid 100099 ] Stopped at 0: address 0 is invalid *** error reading from address 0 *** KDB: reentering More output can be found at http://www.zefox.net/~fbsd/rpi2/crashes/crash_5_2_16/ Thanks for reading, I hope this is of interest. bob prohaska