From owner-freebsd-questions@FreeBSD.ORG Thu Mar 29 17:28:14 2012 Return-Path: Delivered-To: freebsd-questions@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 325601065676; Thu, 29 Mar 2012 17:28:14 +0000 (UTC) (envelope-from feld@feld.me) Received: from feld.me (unknown [IPv6:2607:f4e0:100:300::2]) by mx1.freebsd.org (Postfix) with ESMTP id D6CC28FC23; Thu, 29 Mar 2012 17:28:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=feld.me; s=blargle; h=In-Reply-To:Message-Id:From:Mime-Version:Date:References:Subject:Cc:To:Content-Type; bh=emgPWYOK+77W7Rja+EVBGyqjyN+hjs9k8BKIMxIlhjo=; b=bO7EWE/seVTeW1GmechDZq/17NAfHNLrl+I/ykU9LMCRz3nxT4TzzQz0cCYdujtnl2GvX3Rex74y3c/KHNLx7lwkQADMdzgLmnf7K31mecxWjYG/15GXrGcKxbd7CWhn; Received: from localhost ([127.0.0.1] helo=mwi1.coffeenet.org) by feld.me with esmtp (Exim 4.77 (FreeBSD)) (envelope-from ) id 1SDJ8u-000Jqv-Hg; Thu, 29 Mar 2012 12:28:13 -0500 Received: from feld@feld.me by mwi1.coffeenet.org (Archiveopteryx 3.1.4) with esmtpa id 1333042086-20726-20725/5/27; Thu, 29 Mar 2012 17:28:06 +0000 Content-Type: text/plain; charset=utf-8; format=flowed; delsp=yes To: freebsd-hackers@freebsd.org, freebsd-questions@FreeBSD.org References: Date: Thu, 29 Mar 2012 12:28:05 -0500 Mime-Version: 1.0 From: Mark Felder Message-Id: In-Reply-To: User-Agent: Opera Mail/11.62 (FreeBSD) X-SA-Score: -1.5 Cc: Mark Atkinson Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2012 17:28:14 -0000 On Thu, 29 Mar 2012 12:05:30 -0500, Mark Atkinson wrote: > > If this is an interrupt problem with disk i/o, then you might want to > look into (DDB(4)) > show intr > show intrcount > maybe > show allrman Thank you! I really don't know what things we should be running in DDB to diagnose this and we will try this upon the next crash.