From owner-freebsd-hackers@FreeBSD.ORG Thu Mar 29 20:16:25 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 311C7106567E; Thu, 29 Mar 2012 20:16:25 +0000 (UTC) (envelope-from jgreco@aurora.sol.net) Received: from mail1.sol.net (mail1.sol.net [206.55.64.72]) by mx1.freebsd.org (Postfix) with ESMTP id E9B978FC08; Thu, 29 Mar 2012 20:16:24 +0000 (UTC) Received: from aurora.sol.net (IDENT:jgreco@aurora.sol.net [206.55.70.98]) by mail1.sol.net (8.14.4/8.14.4/SNNS-1.04) with ESMTP id q2TKGGFX053716; Thu, 29 Mar 2012 15:16:16 -0500 (CDT) Received: (from jgreco@localhost) by aurora.sol.net (8.14.3/8.14.3/Submit) id q2TKGFmA083082; Thu, 29 Mar 2012 15:16:15 -0500 (CDT) From: Joe Greco Message-Id: <201203292016.q2TKGFmA083082@aurora.sol.net> To: hselasky@c2i.net (Hans Petter Selasky) Date: Thu, 29 Mar 2012 15:16:15 -0500 (CDT) In-Reply-To: <201203291755.36651.hselasky@c2i.net> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org, Adrian Chadd , Mark Felder , freebsd-questions@freebsd.org 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 20:16:25 -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? That doesn't seem to fit. Why would a perfectly functional VM suddenly develop this problem when given a slow underlying datastore (fits so far) but then the problem *remains* when returned to a fast local datastore, even on a different host and architecture? And why wouldn't the other VM's running alongside develop the same problem? > What does "wmstat -i" output? No idea, we reloaded the VM months ago. ... JG -- Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net "We call it the 'one bite at the apple' rule. Give me one chance [and] then I won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN) With 24 million small businesses in the US alone, that's way too many apples.