From owner-freebsd-arm@FreeBSD.ORG Thu Jan 10 01:14:36 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6B6FACE8 for ; Thu, 10 Jan 2013 01:14:36 +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 23DA0BE7 for ; Thu, 10 Jan 2013 01:14:35 +0000 (UTC) Received: from smtp01.qsp.nl (localhost [127.0.0.1]) by smtp01.qsp.nl (Postfix) with ESMTP id B0DA02A0C7D for ; Thu, 10 Jan 2013 02:14:33 +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 02:14:33 +0100 (CET) Received: by nwg.bouwman.net (Postfix, from userid 501) id A1D0045179; Thu, 10 Jan 2013 02:14:22 +0100 (CET) Date: Thu, 10 Jan 2013 02:14:22 +0100 From: Roel Bouwman To: freebsd-arm@freebsd.org Subject: Re: FreeBSD/armv6z/clang on Raspberry Pi 512MB (with U-Boot + ubldr) Message-ID: <20130110011422.GC3090@shuttle.bouwman.net> References: <20130109205029.GB3090@shuttle.bouwman.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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 01:14:36 -0000 Gianni, On Wed, Jan 09, 2013 at 10:00:15PM +0100, you (Giovanni Trematerra) wrote the following: > Could you show the backtrace? Somewhat after the fact, as Daisuke has also experienced the same issue and already posted the solution. But to be complete: panic: Bad link elm 0xc10fcbd0 next->prev != elm KDB: enter: panic [ thread pid 65 tid 100049 ] Stopped at $d: ldrb r15, [r15, r15, ror r15]! db> bt Tracing pid 65 tid 100049 td 0xc2fe8620 end() at 0xd49bf814 scp=0xd49bf814 rlv=0xc04054c4 (db_trace_thread+0x34) rsp=0xd49bf7f8 rfp=0xc053d728 Bad frame pointer: 0xc053d728 Booting with PIO (hw.bcm2835.sdhci.pio=1) solved the issue: Starting file system checks: ** SU+J Recovering /dev/mmcsd0s2a ** Reading 8388608 byte journal from inode 4. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. ** 271 journal records in 19968 bytes for 43.43% utilization ** Freed 50 inodes (0 dirs) 20 blocks, and 208 frags. ***** FILE SYSTEM MARKED CLEAN ***** Thanks! Roel.