From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 29 15:57:08 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2602A1065676; Thu, 29 Mar 2012 15:57:08 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.c2i.net [212.247.154.2]) by mx1.freebsd.org (Postfix) with ESMTP id 4254F8FC19; Thu, 29 Mar 2012 15:57:06 +0000 (UTC) X-T2-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop002.hselasky.homeunix.org) by mailfe01.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 258963190; Thu, 29 Mar 2012 17:56:59 +0200 From: Hans Petter Selasky To: freebsd-hackers@freebsd.org Date: Thu, 29 Mar 2012 17:55:36 +0200 User-Agent: KMail/1.13.5 (FreeBSD/8.3-PRERELEASE; KDE/4.4.5; amd64; ; ) References: <201203291549.q2TFnUc7080406@aurora.sol.net> In-Reply-To: <201203291549.q2TFnUc7080406@aurora.sol.net> X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@d2+AyewRX}mAm; Yp |U[@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y>Y}k1C4TfysrsUI -%GU9V5]iUZF&nRn9mJ'?&>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201203291755.36651.hselasky@c2i.net> Cc: freebsd-questions@freebsd.org, Adrian Chadd , Mark Felder , Joe Greco Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Mar 2012 15:57:08 -0000 On Thursday 29 March 2012 17:49:30 Joe Greco wrote: > > On Thursday 29 March 2012 15:42:42 Joe Greco wrote: > > > > Hi, > > > > Do both 32- and 64-bit versions of FreeBSD crash? > > We've only seen it happen on one virtual machine. That was a 32-bit > version. And it's not so much a crash as it is a "disk I/O hang". It almost sounds like the lost interrupt issue I've seen with USB EHCI devices, though disk I/O should have a retry timeout? What does "wmstat -i" output? --HPS