zfs kernel panic, known incompatibilities with clang & CPUTYPE/COPTFLAGS?

Martin Matuska mm at FreeBSD.org
Sat Jun 29 12:02:39 UTC 2013

On 2013-06-29 12:01, Alexander Leidinger wrote:
> On Thu, 27 Jun 2013 23:58:33 +0200
> Kristof Provost <kristof at sigsegv.be> wrote:
>> On 2013-06-24 22:08:01 (+0200), Alexander Leidinger
>> <Alexander at Leidinger.net> wrote:
>>> On Mon, 24 Jun 2013 12:15:18 +0200
>>> Kristof Provost <kristof at sigsegv.be> wrote:
>>>> For what it's worth, I'm running into exactly the same problem.
>>>> (amd64, stable/9). I have no custom settings in /etc/make.conf
>>>> or /etc/src.conf
>>> I had a short discussion with the maintainer of our
>>> stress-test-suite, he was able to create a test-case which triggers
>>> the problem.
>> I've been bisecting for a little bit, and while I'm not 100% sure yet,
>> there is one likely culprit right now: r249643.
>> It's an MFC with a number of ZFS changes relating to a refactoring of
>> the ioctl() interface. 
>> It is, unfortunately, also a rather large commit.
> Martin, the issue here is that starting a jail with a recent -current
> panics, if the jail has a dataset assigned to it during start (and
> the rc.d zfs scripts kicks in). At least in my case the jail contains an
> userland from before the change and the jail host a current userland.
> Any ideas / suggestions? pho@ has a test case for this.
> Bye,
> Alexander.
Hi Alexander,

some input would be great (at least the panic message - ideally from a
debug kernel).


More information about the freebsd-current mailing list