From owner-freebsd-fs@FreeBSD.ORG Tue Oct 22 17:09:00 2013 Return-Path: Delivered-To: freebsd-fs@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 ESMTP id EAB4C858; Tue, 22 Oct 2013 17:09:00 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0796A28B0; Tue, 22 Oct 2013 17:08:59 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id UAA28756; Tue, 22 Oct 2013 20:08:49 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VYfRp-000NTd-6R; Tue, 22 Oct 2013 20:08:49 +0300 Message-ID: <5266B0E9.3040206@FreeBSD.org> Date: Tue, 22 Oct 2013 20:07:53 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.0.1 MIME-Version: 1.0 To: J David , Konstantin Belousov Subject: Re: 9.2 + ZFS + i386 = panic: pmap_enter: attempted pmap_enter on 4MB page References: <20131015164537.GH3865@kib.kiev.ua> <525D7784.5000808@rice.edu> <20131016060010.GO3865@kib.kiev.ua> <20131017070949.GA3865@kib.kiev.ua> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-fs@freebsd.org" , alc@FreeBSD.org, Alan Cox X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Oct 2013 17:09:01 -0000 on 22/10/2013 15:46 J David said the following: > On Sun, Oct 20, 2013 at 9:02 AM, J David wrote: >> The "attempted pmap_enter on 4MB page" panic occurred again. > > Since a machine that crashes 3-4x a day is not useful, we have > captured a few viable core images for this panic and have now set it > to vm.pmap.pg_ps_enabled=0 in the hopes of stopping the crashes. > > If there is anything else we can do to aid the debugging, please let us know. Both panics you posted actually happened because of bad pointer dereference in ZFS. It appears that for some reason trap_pfault does not just call panic right there as it should, but instead attempts to "fault in" a corresponding page. All in all, these look like a memory corruption of some sort (or use after free). -- Andriy Gapon