From owner-freebsd-hardware@FreeBSD.ORG Mon Sep 24 19:15:46 2007 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 437BB16A418; Mon, 24 Sep 2007 19:15:46 +0000 (UTC) (envelope-from kris@FreeBSD.org) Received: from weak.local (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx1.freebsd.org (Postfix) with ESMTP id 4DFC713C45B; Mon, 24 Sep 2007 19:15:43 +0000 (UTC) (envelope-from kris@FreeBSD.org) Message-ID: <46F80CE0.6010609@FreeBSD.org> Date: Mon, 24 Sep 2007 21:15:44 +0200 From: Kris Kennaway User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728) MIME-Version: 1.0 To: Ivan Voras References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Kernel panic on PowerEdge 1950 under certain stress load X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Sep 2007 19:15:46 -0000 Ivan Voras wrote: > Benjie Chen wrote: > >> Kernel panic is at 0xC066C731, which from nm shows it's in mtx_lock_spin >> c066c7b4 T _mtx_lock_spin >> c066c85c T _mtx_unlock_sleep >> >> So this could mean that independent stress tests will not result in >> panic if >> there aren't enough concurrency to cause the problem. > > When you get a kernelbacktrace, see if it's the same as the one > mentioned here: > http://lists.freebsd.org/pipermail/freebsd-current/2007-September/076932.html Surely it cannot be since it involves a different function ;-) Kris