Date: Thu, 10 Jan 2013 02:14:22 +0100 From: Roel Bouwman <roel@bouwman.net> 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> In-Reply-To: <CACfq093Mhu3-Ru=uNpXGVr5raxKJ74h25u3qY7-DZV31pra4Tg@mail.gmail.com> References: <20130109205029.GB3090@shuttle.bouwman.net> <CACfq093Mhu3-Ru=uNpXGVr5raxKJ74h25u3qY7-DZV31pra4Tg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130110011422.GC3090>