From owner-freebsd-arm@FreeBSD.ORG  Fri Jan 16 18:48:53 2015
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: freebsd-arm@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CF56D6BA
 for <freebsd-arm@freebsd.org>; Fri, 16 Jan 2015 18:48:53 +0000 (UTC)
Received: from mwork.nabble.com (mwork.nabble.com [162.253.133.43])
 by mx1.freebsd.org (Postfix) with ESMTP id BAA62D8E
 for <freebsd-arm@freebsd.org>; Fri, 16 Jan 2015 18:48:53 +0000 (UTC)
Received: from msam.nabble.com (unknown [162.253.133.85])
 by mwork.nabble.com (Postfix) with ESMTP id D3A9810C2F1F
 for <freebsd-arm@freebsd.org>; Fri, 16 Jan 2015 10:48:49 -0800 (PST)
Date: Fri, 16 Jan 2015 11:48:47 -0700 (MST)
From: Scott Ellis <scott@jumpnowtek.com>
To: freebsd-arm@freebsd.org
Message-ID: <1421434127781-5981309.post@n5.nabble.com>
Subject: OMAP4 broken with r277215
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>
List-Post: <mailto:freebsd-arm@freebsd.org>
List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>,
 <mailto:freebsd-arm-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Jan 2015 18:48:53 -0000

I'm having problems booting systems built with r277215 on my
OMAP4 boards. I haven't tried any other ARM boards.

Systems built with r277214 are fine.

r277215 committed some changes to loader for Xen multiboot support.

I'm pretty sure the panic is coming from uboot_vm_translate() in
sys/boot/uboot/lib/copy.c

Rebuilding with some debugging now to track down the caller, but
maybe someone has already fixed this.

The boot hangs like this

U-Boot SPL 2014.10 (Jan 16 2015 - 07:01:57)
OMAP4430 ES2.3
reading u-boot.img
reading u-boot.img


U-Boot 2014.10 (Jan 16 2015 - 07:01:57)

CPU  : OMAP4430 ES2.3
Board: duovero
I2C:   ready
DRAM:  1 GiB
WARNING: Caches not enabled
MMC:   OMAP SD/MMC: 0
reading u-boot.env

** Unable to read "u-boot.env" from mmc0:1 **
Using default environment

Net:   smc911x-0
Warning: smc911x-0 using MAC address from net device

reading uEnv.txt
** Unable to read file uEnv.txt **
Hit any key to stop autoboot:  0
Booting from: mmc 0 ubldr
reading ubldr
262362 bytes read in 26 ms (9.6 MiB/s)
## Starting application at 0x88000074 ...
Consoles: U-Boot console
Compatible U-Boot API signature found @bef562a8

FreeBSD/armv6 U-Boot loader, Revision 1.2
(root@fbsd, Fri Jan 16 11:59:13 EST 2015)

DRAM: 1024MB
MMC Device 1 not found
MMC Device 1 not found
Number of U-Boot devices: 2
U-Boot env: loaderdev='mmc 0'
Found U-Boot device: disk
  Checking unit=0 slice=<auto> partition=<auto>... good.
/
/boot/kernel/kernel data=0x618688+0x43978 syms=[0x4+0x5f030+0x4+0x5a3d5]
panic: Address offset 0x40000001 bigger than size 0x40000000

--> Press a key on the console to reboot <--





--
View this message in context: http://freebsd.1045724.n5.nabble.com/OMAP4-broken-with-r277215-tp5981309.html
Sent from the freebsd-arm mailing list archive at Nabble.com.