From owner-freebsd-stable@FreeBSD.ORG Fri Sep 10 10:04:56 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 DD65D106566C for ; Fri, 10 Sep 2010 10:04:56 +0000 (UTC) (envelope-from free.bsd@webstyle.ch) Received: from zimbra.webstyle.ch (zimbra.webstyle.ch [212.103.68.7]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0478FC0C for ; Fri, 10 Sep 2010 10:04:56 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by zimbra.webstyle.ch (Postfix) with ESMTP id B237810C00A2; Fri, 10 Sep 2010 12:04:53 +0200 (CEST) X-Virus-Scanned: amavisd-new at zimbra.webstyle.ch Received: from zimbra.webstyle.ch ([127.0.0.1]) by localhost (zimbra.webstyle.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0ov+B3HuXqQ5; Fri, 10 Sep 2010 12:04:52 +0200 (CEST) Received: from [192.168.1.128] (unknown [212.60.63.146]) by zimbra.webstyle.ch (Postfix) with ESMTPA id 955BA10C00A0; Fri, 10 Sep 2010 12:04:52 +0200 (CEST) Message-ID: <4C8A02C2.9060704@webstyle.ch> Date: Fri, 10 Sep 2010 12:04:50 +0200 From: freebsd User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; de; rv:1.9.2.9) Gecko/20100825 Thunderbird/3.1.3 MIME-Version: 1.0 To: Kostik Belousov References: <4C89F014.1050601@webstyle.ch> <20100910092151.GO2465@deviant.kiev.zoral.com.ua> In-Reply-To: <20100910092151.GO2465@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: strange problem with FreeBSD 7.3 64bit 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: Fri, 10 Sep 2010 10:04:56 -0000 Am 10.09.2010 11:21, schrieb Kostik Belousov: > On Fri, Sep 10, 2010 at 10:45:08AM +0200, freebsd wrote: > It sounds like a deadlock, but the cause cannot be identified without > further diagnostic. It might be driver (ciss I assume), but may be quota > code, or even something else. > > Please follow the > http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-deadlocks.html > to obtain the required information. thanks for the quick answer. we've added the additional options to debug deadlocks. we'll have the required information in the timeframe of 1-2 weeks, since the testbox isn't that fast at generating the error. QUOTA most likely isn't the culprit, since 2 of the affected 6 boxes were running GENERIC w/o any modifications.