Date: Wed, 12 Jun 2013 22:39:53 +0200 From: Dimitry Andric <dim@freebsd.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: current@freebsd.org Subject: Re: zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS? Message-ID: <E9E313A1-AEA5-4926-86A2-6CEF0E7EB388@freebsd.org> In-Reply-To: <20130612223024.00003980@unknown> References: <20130612223024.00003980@unknown>
next in thread | previous in thread | raw e-mail | index | archive | help
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. In any case, please try to get a backtrace. > Before I try to get some time to debug this, I would like to know if > there are some known incompatibilities with my make.conf settings. = With > gcc I used successfully this: > ---snip--- > COPTFLAGS=3D -O2 -pipe > CPUTYPE?=3Dcore2 > ---snip--- >=20 > With those settings I first did a buildworld, then a buildkernel with > the r251618 sources. >=20 > Are there some known issues with those settings? If yes, any = suggestions > what I should use instead? If not, would it be beneficial to try with > different settings (which ones)? "-O2 -pipe" is the default setting, so it should work. I personally also always use CPUTYPE core2, and I have never seen any panics. Then again, I do not usually use jails intensively... -Dimitry
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E9E313A1-AEA5-4926-86A2-6CEF0E7EB388>