From owner-freebsd-fs@FreeBSD.ORG Tue Oct 29 15:37:42 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 61979751 for ; Tue, 29 Oct 2013 15:37:42 +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 B2E712F6C for ; Tue, 29 Oct 2013 15:37:41 +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 RAA11919; Tue, 29 Oct 2013 17:37:39 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1VbBMR-0005dU-2U; Tue, 29 Oct 2013 17:37:39 +0200 Message-ID: <526FD60B.6000101@FreeBSD.org> Date: Tue, 29 Oct 2013 17:36:43 +0200 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 , "freebsd-fs@freebsd.org" Subject: Re: 9.2 + ZFS + i386 = panic: pmap_enter: attempted pmap_enter on 4MB page References: In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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, 29 Oct 2013 15:37:42 -0000 on 29/10/2013 15:48 J David said the following: > On Tue, Oct 15, 2013 at 11:17 AM, J David wrote: >> This machine was rock solid under 8.4, but since upgrading to 9.2 it >> has been a disaster. It crashes every few hours with "panic: >> pmap_enter: attempted pmap_enter on 4MB page." > > In the absence of a fix, the best workaround we have found for this > issue has been to set vm.pmap.pg_ps_enabled=0 in /boot/loader.conf. > And with that you are not getting any panic any more? What CPU do you have? Relevant lines from the beginning of dmesg will do. -- Andriy Gapon