From owner-freebsd-fs@FreeBSD.ORG Tue Feb 2 18:18:48 2010 Return-Path: Delivered-To: freebsd-fs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 15ACA1065670; Tue, 2 Feb 2010 18:18:48 +0000 (UTC) (envelope-from julian@elischer.org) Received: from utility-0.aerioconnect.net (outu.internet-mail-service.net [216.240.47.244]) by mx1.freebsd.org (Postfix) with ESMTP id C253B8FC0C; Tue, 2 Feb 2010 18:18:47 +0000 (UTC) Received: from idiom.com (mx0.idiom.com [216.240.32.160]) by utility-0.aerioconnect.net (8.13.1/8.13.1) with ESMTP id o12HcCdw019434; Tue, 2 Feb 2010 09:38:12 -0800 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id C3A692D601B; Tue, 2 Feb 2010 09:38:11 -0800 (PST) Message-ID: <4B686324.2090308@elischer.org> Date: Tue, 02 Feb 2010 09:38:44 -0800 From: Julian Elischer User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Andriy Gapon References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> In-Reply-To: <4B682F29.90505@icyb.net.ua> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, Stephane LAPIE , freebsd-hardware@freebsd.org Subject: Re: [zfs][hardware] Reproducible kernel panic in 8.0-STABLE X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Feb 2010 18:18:48 -0000 Andriy Gapon wrote: > on 02/02/2010 15:32 Stephane LAPIE said the following: >> I have a case of kernel panic that can be consistently reproduced, and >> which I guess is related to the hardware I'm using (Marvell controllers, >> check my pciconf -lv output below). >> >> The kernel panic message is always, consistently, the following : >> >> Sleeping thread (tid 100021, pid 0) owns a non-sleepable lock > > I probably won't be able to help you, but to kickstart debugging could you please > run 'procstat -t 0' and determine what kernel thread has tid 100021 on your system? or in the kernel debugger after the panic, do: bt you DO have options kdb and ddb right? (I never leave home without them)