From owner-freebsd-arm@FreeBSD.ORG Thu Jan 10 12:36:31 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 520BC486 for ; Thu, 10 Jan 2013 12:36:31 +0000 (UTC) (envelope-from roel@bouwman.net) Received: from smtp01.qsp.nl (smtp01.qsp.nl [193.254.214.162]) by mx1.freebsd.org (Postfix) with ESMTP id 1A43DAF8 for ; Thu, 10 Jan 2013 12:36:30 +0000 (UTC) Received: from smtp01.qsp.nl (localhost [127.0.0.1]) by smtp01.qsp.nl (Postfix) with ESMTP id 6C9E02A0C53 for ; Thu, 10 Jan 2013 13:36:28 +0100 (CET) Received: from nwg.bouwman.net (berl.bouwman.net [80.101.149.113]) by smtp01.qsp.nl (Postfix) with ESMTP for ; Thu, 10 Jan 2013 13:36:28 +0100 (CET) Received: by nwg.bouwman.net (Postfix, from userid 501) id BE97445179; Thu, 10 Jan 2013 13:36:05 +0100 (CET) Date: Thu, 10 Jan 2013 13:36:05 +0100 From: Roel Bouwman To: freebsd-arm@freebsd.org Subject: Re: FreeBSD/armv6z/clang on Raspberry Pi 512MB (with U-Boot + ubldr) Message-ID: <20130110123605.GC31212@shuttle.bouwman.net> References: <20130109205029.GB3090@shuttle.bouwman.net> <1E4F692C2E774A5C9ED66CE1A502C261@ad.peach.ne.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1E4F692C2E774A5C9ED66CE1A502C261@ad.peach.ne.jp> User-Agent: Mutt/1.4.2.3i X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 10 Jan 2013 12:36:31 -0000 Hi Daisuke, On Thu, Jan 10, 2013 at 06:23:10AM +0900, you (Daisuke Aoyama) wrote the following: > After recovery, download new kernel then replace old one. > > # fetch http://www.peach.ne.jp/archives/rpi/kernel/kernel-20130110.gz This kernel has exactly the same issue: FreeBSD 10.0-CURRENT #0 r244906M: Thu Jan 10 05:49:56 JST 2013 aoyama@fbs.local:/usr/obj-rpi-clang/arm.armv6/usr/src/sys/RPI-B-test13 arm ... Starting file system checks: ** SU+J Recovering /dev/mmcsd0s2a ** Reading 8388608 byte journal from inode 4. ** Building prid 65 (fsck_ufs), uid 0: exited on signal 11 ecovery table. panic: Bad link elm 0xc10e3dc8 next->prev != elm KDB: enter: panic [ thread pid 65 tid 100049 ] Stopped at breakpoint: ldrb r15, [r15, r15, ror r15]! db> bt Tracing pid 65 tid 100049 td 0xc2fca620 end() at 0xd49ab9a8 scp=0xd49ab9a8 rlv=0xc03c8208 (db_trace_self+0x14) rsp=0xd49ab99c rfp=0xc04e6d14 Bad frame pointer: 0xc04e6d14 I'll just leave DMA disabled for now. Regards, Roel.