From owner-freebsd-stable@FreeBSD.ORG Tue Jun 8 16:24:15 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6729E1065679 for ; Tue, 8 Jun 2010 16:24:15 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 38E888FC1F for ; Tue, 8 Jun 2010 16:24:15 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id E0E0946C1F; Tue, 8 Jun 2010 12:24:14 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 3A70C8A021; Tue, 8 Jun 2010 12:24:14 -0400 (EDT) From: John Baldwin To: freebsd-stable@freebsd.org Date: Tue, 8 Jun 2010 11:48:06 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201006081148.06315.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 08 Jun 2010 12:24:14 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: pluknet Subject: Re: mfiutil create .. leads to deadlock in 6-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Jun 2010 16:24:15 -0000 On Tuesday 08 June 2010 5:30:30 am pluknet wrote: > hi, > > I faced w/ subj. issue on IBM ServeRAID M5015 (LSISAS2108 SAS2.0 6Gbps). > > As I can see, lockup is caused by sleeping on sx lock after Giant was acquired. > Can r160217 help me or am I go the wrong way? > from r160217: "Use a sleep mutex instead of an sx lock for the kernel > environment." Giant is special, it can be acquired both before and after sx locks because it is released while blocking on an sx lock. Are you sure that mfiutil is hung? The thread appears to be running rather than blocked on a lock. -- John Baldwin