From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fossil lockups: anyone seen this?
In-Reply-To: Your message of "Tue, 28 Oct 2003 22:55:29 MST."
             <Pine.LNX.4.44.0310282254040.23763-100000@maxroach.lanl.gov>
From: "Russ Cox" <rsc@swtch.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <22972.1067435487.1@t40.swtch.com>
Message-Id: <E1AEqjV-0005yY-5S@t40.swtch.com>
Date: Wed, 29 Oct 2003 08:51:27 -0500
Topicbox-Message-UUID: 7a86b1fa-eacc-11e9-9e20-41e7f4b1d025

> I can't 'mk CONF=pccpu' without fossil locking up in vmware. No real
> symptoms to speak of, just a lockup. Vmware does go into "halt and catch
> fire" mode, eating 99% of cpu.

And you think this is Plan 9's fault because?

Seriously, can you do ^t ^t p?  Does it show fossil
using lots of CPU?  Maybe it really is a VMware bug.

If you're running VMware 4, I would not be surprised.
They were a lot more interested in features than
robustness.  Also if you're running on top of Linux,
since then you've got that problem twice.  :-(

Russ