From owner-freebsd-arm@FreeBSD.ORG  Mon Jun 16 07:33:19 2014
Return-Path: <owner-freebsd-arm@FreeBSD.ORG>
Delivered-To: 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 ESMTPS id 1C45985B;
 Mon, 16 Jun 2014 07:33:19 +0000 (UTC)
Received: from mail.turbocat.net (mail.turbocat.net
 [IPv6:2a01:4f8:d16:4514::2])
 (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id CC44820CD;
 Mon, 16 Jun 2014 07:33:18 +0000 (UTC)
Received: from laptop015.home.selasky.org
 (cm-176.74.213.204.customer.telag.net [176.74.213.204])
 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.turbocat.net (Postfix) with ESMTPSA id 205011FE045;
 Mon, 16 Jun 2014 09:33:18 +0200 (CEST)
Message-ID: <539E9DD4.4080001@selasky.org>
Date: Mon, 16 Jun 2014 09:33:40 +0200
From: Hans Petter Selasky <hps@selasky.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Alan Cox <alc@rice.edu>, Ian Lepore <ian@FreeBSD.org>
Subject: Re: RPI-B VM panic
References: <539170AA.2000109@selasky.org> <5396947A.1060601@selasky.org>	
 <5396A0D1.80309@selasky.org> <5396AF63.6040209@selasky.org>	
 <8BA66A45-E08A-475D-A1FA-5047E862681E@rice.edu>	
 <5398B6EA.9030408@selasky.org>	
 <A9433B36-C15C-455E-AB80-3999596936F9@rice.edu>	
 <5398BFD9.60502@selasky.org>	
 <7390A211-C949-4079-B3DA-BF23798B8992@rice.edu>	
 <539942C0.5010706@selasky.org> <5399DF7F.4010501@rice.edu>	
 <5399E349.5050600@selasky.org>
 <1402594327.20883.216.camel@revolution.hippie.lan>
 <5399E660.5050207@selasky.org> <5399E901.1080805@selasky.org>
 <5399FB57.8090102@rice.edu> <539A140F.6020107@selasky.org>
 <539B2BE8.2090005@rice.edu>
In-Reply-To: <539B2BE8.2090005@rice.edu>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "arm@freebsd.org" <arm@FreeBSD.org>
X-BeenThere: freebsd-arm@freebsd.org
X-Mailman-Version: 2.1.18
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: Mon, 16 Jun 2014 07:33:19 -0000

>
> This output shows that according to the object's list of pages there is
> already a page allocated at pindex 4 (or "off=0x4" above).  If this list
> is correct, and not itself corrupted, then we shouldn't be making a call
> to vm_page_alloc() to allocate another page at the same pindex.
>
> Whether it is this list of pages that is corrupted or not, this means
> that the object's list of pages (shown above) and its radix tree of
> pages are out of sync.
>
> I'm curious to know what mpred is when the assertion fails.  That will
> tell us something about the state of the radix tree.
>
> I've also modified ddb's "show object" to provide an additional bit of
> information.  However, it would be really nice if "show object"
> displayed the state of the radix tree.
>
>

This patch makes no change.

--HPS