From owner-freebsd-current@FreeBSD.ORG  Sat Jun 29 12:02:39 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 F255371E;
 Sat, 29 Jun 2013 12:02:38 +0000 (UTC) (envelope-from mm@FreeBSD.org)
Received: from mail.vx.sk (mail.vx.sk [IPv6:2a01:4f8:150:6101::4])
 by mx1.freebsd.org (Postfix) with ESMTP id B613F1329;
 Sat, 29 Jun 2013 12:02:38 +0000 (UTC)
Received: from core.vx.sk (localhost [127.0.0.2])
 by mail.vx.sk (Postfix) with ESMTP id E4F64235F7;
 Sat, 29 Jun 2013 14:02:37 +0200 (CEST)
X-Virus-Scanned: amavisd-new at mail.vx.sk
Received: from mail.vx.sk by core.vx.sk (amavisd-new, unix socket) with LMTP
 id C3Hl9DYrhKMP; Sat, 29 Jun 2013 14:02:36 +0200 (CEST)
Received: from [10.9.8.144] (chello085216226145.chello.sk [85.216.226.145])
 by mail.vx.sk (Postfix) with ESMTPSA id 86419235F0;
 Sat, 29 Jun 2013 14:02:36 +0200 (CEST)
Message-ID: <51CECCDB.7040904@FreeBSD.org>
Date: Sat, 29 Jun 2013 14:02:35 +0200
From: Martin Matuska <mm@FreeBSD.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130623 Thunderbird/17.0.7
MIME-Version: 1.0
To: Alexander Leidinger <Alexander@Leidinger.net>
Subject: Re: zfs kernel panic,
 known incompatibilities with clang & CPUTYPE/COPTFLAGS?
References: <20130612223024.00003980@unknown>
 <E9E313A1-AEA5-4926-86A2-6CEF0E7EB388@freebsd.org>
 <20130614230702.00006aa0@unknown>
 <20130624101517.GA9630@thebe.jupiter.sigsegv.be>
 <20130624220801.0000492c@unknown>
 <20130627215832.GA9470@thebe.jupiter.sigsegv.be>
 <20130629120122.000041c7@unknown>
In-Reply-To: <20130629120122.000041c7@unknown>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: Kristof Provost <kristof@sigsegv.be>, Dimitry Andric <dim@freebsd.org>,
 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
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jun 2013 12:02:39 -0000

On 2013-06-29 12:01, Alexander Leidinger wrote:
> On Thu, 27 Jun 2013 23:58:33 +0200
> Kristof Provost <kristof@sigsegv.be> wrote:
>
>> On 2013-06-24 22:08:01 (+0200), Alexander Leidinger
>> <Alexander@Leidinger.net> wrote:
>>> On Mon, 24 Jun 2013 12:15:18 +0200
>>> Kristof Provost <kristof@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).

Cheers,
mm