From owner-freebsd-arm@FreeBSD.ORG Thu Jun 12 18:44:09 2014 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 ESMTPS id 276BD104 for ; Thu, 12 Jun 2014 18:44:09 +0000 (UTC) Received: from mail-n.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail-n.franken.de", Issuer "Thawte DV SSL CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBD112BA6 for ; Thu, 12 Jun 2014 18:44:08 +0000 (UTC) Received: from [192.168.1.200] (p508F17FA.dip0.t-ipconnect.de [80.143.23.250]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTP id F17371C104649; Thu, 12 Jun 2014 20:44:04 +0200 (CEST) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: RPI-B VM panic From: Michael Tuexen In-Reply-To: <5399434D.2070008@selasky.org> Date: Thu, 12 Jun 2014 20:44:03 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <539170AA.2000109@selasky.org> <5398B50A.1070301@selasky.org> <5399434D.2070008@selasky.org> To: Hans Petter Selasky X-Mailer: Apple Mail (2.1878.2) Cc: freebsd-arm 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 18:44:09 -0000 On 12 Jun 2014, at 08:06, Hans Petter Selasky wrote: > On 06/11/14 22:51, Michael Tuexen wrote: >> On 11 Jun 2014, at 21:59, Hans Petter Selasky = wrote: >>=20 >>> On 06/06/14 09:41, Hans Petter Selasky wrote: >>>> Hi, >>>>=20 >>>> I'm seeing this with RPI-B: >>>>=20 >>>> panic: vm_page_insert_after: msucc doesn't succeed pindex >>>> KDB: enter: panic >>>> [ thread pid 18 tid 100052 ] >>>> Stopped at $d: ldrb r15, [r15, r15, ror r15]! >>>> db> >>>>=20 >>>>=20 >>>> Any ideas? >> Which revision are you using? What is triggering the panic? I could >> try to reproduce the problem. >>=20 >> I've used r267055 with reverted r266083 for a couple of days and >> it was running stable. It compiled a lot of ports including = wireshark. >>=20 >=20 > Hi, >=20 > I'm running -current with a patch reverted for the CPU counter. It = happens around growfs. The error is not constant. If I change the boot = timing by plugging more USB devices, then I sometimes can pass I haven't it experienced. I normally grow the filesystem from 1 GB to 16 = GB after installation and I have not connected any USP device. I'm normally = booting it using a serial cable, no monitor, no keyboard, no mouse attached. Best regards Michael > the point of error. I think the problem is related to the following = commit: >=20 >> commit 7d20e37fb658b0e2cd7f3c13dac8022e0e866a21 >> Author: alc >> Date: Sun May 12 16:50:18 2013 +0000 >>=20 >> 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. >>=20 >> Sponsored by: EMC / Isilon Storage Division >>=20 >=20 > Looks like we are trying to grow the stack and then the pages are not = in the expected order. >=20 > --HPS >=20