From owner-freebsd-fs@FreeBSD.ORG Tue Feb 2 15:50:55 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 7DBAE1065670; Tue, 2 Feb 2010 15:50:55 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 901278FC16; Tue, 2 Feb 2010 15:50:54 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id RAA19204; Tue, 02 Feb 2010 17:50:50 +0200 (EET) (envelope-from avg@icyb.net.ua) Message-ID: <4B6849DA.5080303@icyb.net.ua> Date: Tue, 02 Feb 2010 17:50:50 +0200 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20091206) MIME-Version: 1.0 To: Stephane LAPIE References: <4B682972.6030604@darkbsd.org> <4B682F29.90505@icyb.net.ua> <4B6830CF.9070102@darkbsd.org> In-Reply-To: <4B6830CF.9070102@darkbsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-fs@freebsd.org, 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 15:50:55 -0000 on 02/02/2010 16:03 Stephane LAPIE said the following: > 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? > > Thanks for the tip. I will keep that one in mind, as I was wondering how > you looked up individual threads. > > # procstat -t 0 | grep 100021 > 0 100021 kernel thread taskq 1 92 sleep - > > Is that the "kernel task queue" handler ? This taskqueue "taskqueue_thread" which is used to schedule tasks in many places. I would guess that one of those tasks leaked a lock. Probably it's best to configure system for crashdumps to a reliable storage and then try to examine a dump with kgdb to see what lock we have here. -- Andriy Gapon