From owner-freebsd-arm@FreeBSD.ORG Thu Jun 12 17:28:22 2014 Return-Path: Delivered-To: arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DD5ECBA2 for ; Thu, 12 Jun 2014 17:28:22 +0000 (UTC) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (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 97E982452 for ; Thu, 12 Jun 2014 17:28:22 +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 B97ED1FE026; Thu, 12 Jun 2014 19:28:19 +0200 (CEST) Message-ID: <5399E349.5050600@selasky.org> Date: Thu, 12 Jun 2014 19:28:41 +0200 From: Hans Petter Selasky User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Alan Cox , "arm@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> <5398BFD9.60502@selasky.org> <7390A211-C949-4079-B3DA-BF23798B8992@rice.edu> <539942C0.5010706@selasky.org> <5399DF7F.4010501@rice.edu> In-Reply-To: <5399DF7F.4010501@rice.edu> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 Jun 2014 17:28:22 -0000 On 06/12/14 19:12, Alan Cox wrote: > On 06/12/2014 01:03, Hans Petter Selasky wrote: >> On 06/11/14 22:47, Alan Cox wrote: >>> >>> On Jun 11, 2014, at 3:45 PM, Hans Petter Selasky wrote: >>> >>>> On 06/11/14 22:20, Alan Cox wrote: >>>>> >>>>> On Jun 11, 2014, at 3:07 PM, Hans Petter Selasky wrote: >>>>> >>>>>> kernel: file format elf32-littlearm >>>>>> >>>>> >>>>> Then this problem is unrelated to the one that I just fixed. It's >>>>> also not a problem that I've seen before. >>>> >>>> It is happening after your recent patches to -current, optimising >>>> the "page ordering". Happens every now and then during boot when >>>> stack is growing looks like. >>> >>> More precisely, which commit is that? >>> >> >>> commit 7d20e37fb658b0e2cd7f3c13dac8022e0e866a21 >>> Author: alc >>> Date: Sun May 12 16:50:18 2013 +0000 >>> >>> Refactor vm_page_alloc()'s interactions with >>> vm_reserv_alloc_page() and >>> vm_page_insert() so that (1) vm_radix_lookup_le() is never called >>> while the >>> free page queues lock is held and (2) vm_radix_lookup_le() is >>> called at most >>> once. This change reduces the average time that the free page >>> queues lock >>> is held by vm_page_alloc() as well as vm_page_alloc()'s average >>> overall >>> running time. >>> >>> Sponsored by: EMC / Isilon Storage Division >>> >> >> > > That's not exactly a recent commit. It was 13 months ago. And, this > code is exercised by all page allocations except for page table pages > and uma_small_alloc(). > > What this assertion is telling us is that somewhere else we have screwed > up the vm object to which we are now trying to allocate a page. > > Try the attached patch. It will provide additional information the next > time that the assertion fails. > Here you go: > panic: vm_page_insert_after: msucc 0xc0993e50 (0) doesn't succeed pindex 4 > object 0xc1a2b140 type 0 > KDB: enter: panic > [ thread pid 18 tid 100052 ] > Stopped at $d: ldrb r15, [r15, r15, ror r15]! > db> --HPS