From owner-freebsd-hardware@FreeBSD.ORG  Tue Apr  1 18:19:02 2014
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
Delivered-To: freebsd-hardware@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id C7462B7B;
 Tue,  1 Apr 2014 18:19:02 +0000 (UTC)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com
 [IPv6:2607:f8b0:4002:c07::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 7E35094E;
 Tue,  1 Apr 2014 18:19:02 +0000 (UTC)
Received: by mail-yk0-f180.google.com with SMTP id 19so4929689ykq.11
 for <multiple recipients>; Tue, 01 Apr 2014 11:19:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=MV3+6bu2kHxjFVXLPqT4l9lT9ibMhn7Ct4l/6fYYbSc=;
 b=rWXyJiYDuvm7d6pB7wLbO/t034GuloXIOhVfqzrGPUNDJQnQrfI/dFHvScOo2FBc8H
 eI2xSdWEXfHmhu2iI0QYJeH0xb0imOp75/R9QEtcTEUb7AJZn4ltmRbT9REuHOgVZT7U
 ej71XdgwjvJ2IwSn1KIcOdLW7+kbo/yt04PLaVH12CKVbwu9nbr0Q2DglpYo7+EfHy1X
 cKMqyct3AtxMyE8VtiCn7Grpp2aCmMUKirWh5wv67gyv/LLiVvy8y8qcUADwmSA2oV72
 c8tiHI0K5eGYf3v7SrY6Q5qZ30KLm5vrD0Hf4eTv0HiIZzW/WvJv8BbnI/YHtGrVO6hE
 fEww==
MIME-Version: 1.0
X-Received: by 10.236.179.162 with SMTP id h22mr13922815yhm.107.1396376341776; 
 Tue, 01 Apr 2014 11:19:01 -0700 (PDT)
Received: by 10.170.95.212 with HTTP; Tue, 1 Apr 2014 11:19:01 -0700 (PDT)
In-Reply-To: <533A5F65.7020800@FreeBSD.org>
References: <CAPp9OrnFL-bNbocA++UqSb+W79QHr5=q_ZFQdod3N8SZ8=iOFQ@mail.gmail.com>
 <53391F6C.9070208@FreeBSD.org>
 <CAPp9Orm0V91pbCS=Yygd1zuFkcq6pAWbxosWSAz8jUWGX3bxEg@mail.gmail.com>
 <533A5F65.7020800@FreeBSD.org>
Date: Tue, 1 Apr 2014 20:19:01 +0200
Message-ID: <CAPp9Or=Rugd0c1dGoqTtTVSFy79-4yDDTiBpinFkXJa7t1hGng@mail.gmail.com>
Subject: Re: ZFS panic: spin lock held too long
From: Idwer Vollering <vidwer@gmail.com>
To: freebsd-fs@freebsd.org, freebsd-hardware@freebsd.org
Content-Type: text/plain; charset=UTF-8
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-hardware>, 
 <mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware/>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
 <mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 18:19:02 -0000

Adding freebsd-hardware@

2014-04-01 8:40 GMT+02:00 Andriy Gapon <avg@freebsd.org>:
> So, this thread is stuck waiting on some CPU(s) doing TLB shootdown.
> This must mean that that CPU is stuck doing something.
> I can not provide exact instructions on how to find out which CPU is stuck and
> what it is doing, but you could try to start with examining output of 'thread
> apply all bt'.

Inline output was over 200KB big, twice, so here is the output from
'thread apply all bt':

http://ra.openbios.org/~idwer/freebsd/vmcore.0.kgdb_out
http://ra.openbios.org/~idwer/freebsd/vmcore.1.kgdb_out