Date: Thu, 29 Mar 2012 15:16:15 -0500 (CDT) From: Joe Greco <jgreco@ns.sol.net> To: hselasky@c2i.net (Hans Petter Selasky) Cc: freebsd-hackers@freebsd.org, Adrian Chadd <adrian@freebsd.org>, Mark Felder <feld@feld.me>, freebsd-questions@freebsd.org Subject: Re: Please help me diagnose this crazy VMWare/FreeBSD 8.x crash Message-ID: <201203292016.q2TKGFmA083082@aurora.sol.net> In-Reply-To: <201203291755.36651.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201203292016.q2TKGFmA083082>