From owner-freebsd-arm@FreeBSD.ORG Tue Oct 29 04:18:19 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id CA413861 for ; Tue, 29 Oct 2013 04:18:19 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A08CE262A for ; Tue, 29 Oct 2013 04:18:19 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id lf10so8118121pab.20 for ; Mon, 28 Oct 2013 21:18:13 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=ES3axEnIxztgo+xC/e9yJF5uC3PbbuS6+w1UWTN6I4s=; b=MNlzqzlMb65lXtA+D3Q+9IDehT8yIta+kQ5rVy8LzxImfJ39fYVGAIZOdbwc7ZpLud DmsV7D6/j6u7oc5dXP5G9/EPJWE5Yqa88ARu5Suh+8ivLcP+w0sUsTLTHzkkOjVdWRL9 XbjgpekHePMWMcPDiw9mZVJu78+ArgXnj7kqWdiHooGJRYaeU/ytQKJPR58o08gGjLYq G+5woL0gUvw4O6o0Olo/kySVHHavnUtCR2mTCkQ6eQfVYIrygT37ISMckkJYMisGk07K BqxaveVVArjl4AfVTfjcP2HpcHUew4/cQACTYFH7/nwUDZn5x6uC8jnIwg+Jg2iTO12d FCwQ== X-Gm-Message-State: ALoCoQmD5quiEfOWU+8w0hWqEqpi/28fpfUf+8P+q/oFwCnjHO5x059DQMHycidGtbmXBxy0A0OX X-Received: by 10.66.102.9 with SMTP id fk9mr29297443pab.41.1383020293043; Mon, 28 Oct 2013 21:18:13 -0700 (PDT) Received: from [192.168.43.193] (ma60536d0.tmodns.net. [208.54.5.166]) by mx.google.com with ESMTPSA id fe5sm32137091pbc.32.2013.10.28.21.18.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Oct 2013 21:18:11 -0700 (PDT) Sender: Tim Kientzle Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) Subject: Re: About CB cant boot with FreeBSD errors From: Tim Kientzle In-Reply-To: Date: Mon, 28 Oct 2013 21:18:02 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: John Elder X-Mailer: Apple Mail (2.1510) Cc: freebsd-arm 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: Tue, 29 Oct 2013 04:18:19 -0000 I fixed an instance of this a couple of months ago. I'm away from my usual dev machine right now, but the previous break was fixed here: http://svnweb.freebsd.org/base?view=3Drevision&revision=3D253636 Check that vm_map_zinit() still has a memset() in your copy of that file. I'm also not sure why _vm_map_init() doesn't need to clear the system_mtx or lock fields=85 Hmmm... Tim On Oct 27, 2013, at 9:53 PM, John Elder = wrote: > My system now is: > root@arm:~ # uname -a > FreeBSD arm 10.0-BETA1 FreeBSD 10.0-BETA1 #0 r256420: Sun Oct 13 = 01:43:07 > UTC 2013 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >=20 >=20 >=20 > On Mon, Oct 28, 2013 at 12:49 PM, John Elder = wrote: >=20 >> Hi, >> I have done under this webpage( >> https://wiki.freebsd.org/FreeBSD/arm/Cubieboard). >> But when I power on the CB, this show: >>=20 >> sun4i#fatload mmc 0 0x40200000 kernel; go 0x40200100 >> reading kernel >>=20 >> 4835069 bytes read >> ## Starting application at 0x40200100 ... >> KDB: debugger backends: ddb >> KDB: current backend: ddb >> Copyright (c) 1992-2013 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 10.0-CURRENT #0: Sun Oct 27 18:38:54 CST 2013 >> root@arm:/usr/obj/arm.armv6/usr/src/sys/CUBIEBOARD arm >> FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 >> panic: lock "vm map (user)" 0xc06eb050 already initialized >> KDB: enter: panic >> [ thread pid 0 tid 0 ] >> Stopped at 0xc03598f0: ldrb r15, [r15, r15, ror r15]! >> db> >>=20 >> What should I do to solve this problem? >>=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org"