Date: Sun, 24 Aug 2014 10:56:58 -0600 From: Tom Everett <tom@khubla.com> To: Ian Lepore <ian@freebsd.org> Cc: "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Subject: Re: wandboard SMP panic Message-ID: <CAB3ij4D9QoBCr__2Jrfkpx7cK9DC756CpM009JwLKriOJxpFcg@mail.gmail.com> In-Reply-To: <1408896148.1150.62.camel@revolution.hippie.lan> References: <53F93895.6060905@0x544745.com> <20140824110530.042dfecf@bender.lan> <1408896148.1150.62.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
I'm upgrading the crochet build for Wandboard to use u-boot 2014.04. Previously it was using a 2013 u-boot. I did have to upgrade the dtc to a more modern version so that uboot-2014-04 would compile. Could that have caused it? The boot command I'm using is: *setenv fdt_file wandboard-quad.dtb;fatload mmc 0:1 88000000 ubldr;bootelf 88000000;* On Sun, Aug 24, 2014 at 10:02 AM, Ian Lepore <ian@freebsd.org> wrote: > On Sun, 2014-08-24 at 11:05 +0100, Andrew Turner wrote: > > On Sat, 23 Aug 2014 18:57:57 -0600 > > Tom Everett <tom@0x544745.com> wrote: > > > > > > > > Hello everyone. I am seeing a new panic booting Wandboard: > > > > > > Loaded DTB from file 'wandboard-quad.dtb'. > > > > > > > > > Kernel entry at 0x12000100... > > > > > > > > > Kernel args: (null) > > > > > > > > > KDB: debugger backends: ddb > > > KDB: current backend: ddb > > > Copyright (c) 1992-2014 The FreeBSD Project. > > > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > > > 1994 The Regents of the University of California. All rights reserved. > > > FreeBSD is a registered trademark of The FreeBSD Foundation. > > > FreeBSD 11.0-CURRENT #0 r270430M: Sat Aug 23 17:24:21 MDT 2014 > > > > > > tom@bernice > :/storage/home/tom/crochet/crochet-freebsd/work/obj/arm.armv6/storage/home/tom/crochet/src/FreeBSDHead/head/sys/IMX6 > > > arm > > > FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) > > > 20140512 CPU: Cortex A9-r2 rev 10 (Cortex-A core) > > > Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 > > > Security_Ext WB disabled EABT branch prediction enabled > > > LoUU:2 LoC:1 LoUIS:2 > > > Cache level 1: > > > 32KB/32B 4-way data cache WB Read-Alloc Write-Alloc > > > 32KB/32B 4-way instruction cache Read-Alloc > > > real memory = 2147483648 (2048 MB) > > > avail memory = 2093891584 (1996 MB) > > > WARNING: Some AP's failed to start > > > FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs > > > random device not loaded; using insecure entropy > > > panic: Built bad topology at 0xc2510fb4. CPU mask (f) != (1) > > > cpuid = 0 > > > KDB: enter: panic > > > [ thread pid 0 tid 100000 ] > > > Stopped at $d: ldrb r15, [r15, r15, ror r15]! > > > db> > > > > I had a similar problem. It turned out to be a caching issue in U-Boot. > > It appears to not correctly flush the dcache. You can try to run > > "dcache off ; dcache flush" before entering ubldr. If this fails you > > will need to build a version of U-Boot with the dcache disabled. > > > > Andrew > > That's interesting... how are y'all launching ubldr, with a 'go' > command? It's been my experience that the bootelf and bootm commands > manage the cache correctly, but go doesn't. You can launch ubldr with > bootelf (it has proper elf headers) but you can't launch the kernel > directly that way. But the stock u-boot might not have bootelf. > > -- Ian > > > -- A better world shall emerge based on faith and understanding - Douglas MacArthur
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAB3ij4D9QoBCr__2Jrfkpx7cK9DC756CpM009JwLKriOJxpFcg>