From owner-freebsd-arm@FreeBSD.ORG Mon Mar 4 15:03:12 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 E5534396 for ; Mon, 4 Mar 2013 15:03:12 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by mx1.freebsd.org (Postfix) with ESMTP id C22F81ED7 for ; Mon, 4 Mar 2013 15:03:12 +0000 (UTC) Received: from c-24-8-232-202.hsd1.co.comcast.net ([24.8.232.202] helo=damnhippie.dyndns.org) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UCWuv-0003GS-Mp; Mon, 04 Mar 2013 15:03:05 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r24F32Ke091531; Mon, 4 Mar 2013 08:03:02 -0700 (MST) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.232.202 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+Kvzr9tZI9MoNhpD11NmNf Subject: Re: RasPi Panic: Address offset 0xC1526FF0 bigger than size 0x08000000 From: Ian Lepore To: Alie Tan In-Reply-To: References: Content-Type: text/plain; charset="us-ascii" Date: Mon, 04 Mar 2013 08:03:02 -0700 Message-ID: <1362409382.1195.227.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" 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: Mon, 04 Mar 2013 15:03:13 -0000 On Mon, 2013-03-04 at 20:06 +0800, Alie Tan wrote: > Hi, > > I got this panic below with RasPi 256MB: > panic: Address offset 0xC1526FF0 bigger than size 0x08000000 > > Any idea why? > > Regards, > Alie T If you're using a recently-compiled kernel but the ubldr on the msdos partition of your sdcard hasn't been updated recently, that would explain it. If so, just copy the latest ubldr onto the msdos partition. If you're using a build script that always rebuilds the whole sdcard image every time, this may be a different problem. -- Ian