Date: Wed, 12 Jun 2013 15:10:59 -0700 From: Peter Wemm <peter@wemm.org> To: Dimitry Andric <dim@freebsd.org> Cc: Alexander Leidinger <Alexander@leidinger.net>, current@freebsd.org Subject: Re: zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS? Message-ID: <CAGE5yCrPMNEmJ5dj2TcL5nsMMZApFsifLrXsctikYLZH23r1pw@mail.gmail.com> In-Reply-To: <E9E313A1-AEA5-4926-86A2-6CEF0E7EB388@freebsd.org> References: <20130612223024.00003980@unknown> <E9E313A1-AEA5-4926-86A2-6CEF0E7EB388@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 12, 2013 at 1:39 PM, Dimitry Andric <dim@freebsd.org> wrote: > On Jun 12, 2013, at 22:30, Alexander Leidinger <Alexander@Leidinger.net> 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. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV On IRC, talking about C++: <BigKnife> I think that it is a good thing I will never meet Bjarne on a street <BigKnife> cause really, I don't want to end up in prison or anything
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGE5yCrPMNEmJ5dj2TcL5nsMMZApFsifLrXsctikYLZH23r1pw>