From owner-freebsd-current@FreeBSD.ORG Wed Jun 12 22:54:25 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8E12DBF0; Wed, 12 Jun 2013 22:54:25 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 7A32518FE; Wed, 12 Jun 2013 22:54:25 +0000 (UTC) Received: from Alfreds-MacBook-Pro-9.local (c-67-180-208-218.hsd1.ca.comcast.net [67.180.208.218]) by elvis.mu.org (Postfix) with ESMTPSA id 639B61A3C1D; Wed, 12 Jun 2013 15:54:24 -0700 (PDT) Message-ID: <51B8FC19.2050309@mu.org> Date: Wed, 12 Jun 2013 15:54:17 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: Peter Wemm Subject: Re: zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS? References: <20130612223024.00003980@unknown> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Alexander Leidinger , Dimitry Andric , current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jun 2013 22:54:25 -0000 On 6/12/13 3:10 PM, Peter Wemm wrote: > On Wed, Jun 12, 2013 at 1:39 PM, Dimitry Andric wrote: >> On Jun 12, 2013, at 22:30, Alexander Leidinger wrote: >>> I try to update from a pre-clang world (r242511M) to "now" (r251618M). >>> The resulting kernel boots, but while starting some jails (with ezjail >>> from ports, so fairly late in the boot process) I get a kernel panic >>> (IIRC zfs trying to access page 0). >> If you are running on i386, it might be a stack overflow? Try >> increasing the stack a little, it might help in that case. >> > For i386 I'd be more inclined to suspect KVA exhaustion. > > For non-PAE, as a shot in the dark, increase > options KVA_PAGES=384 > .. the default is 256 for PAE. that increases kernel KVA from 1GB to 1.5GB. > > For a PAE system, this number is multipled by 2, so a corresponding > change is 512 -> 768. > > This is just a shot in the dark. If this is amd64, then never mind, > KVA_PAGES is meaningless there. Is there some way we can get a pps ratelimited (or even one-time) message when the kva is almost exhausted? Could that help people? -- Alfred Perlstein VP Software Engineering, iXsystems