From owner-freebsd-emulation Thu Feb 17 19:12:33 2000 Delivered-To: freebsd-emulation@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by hub.freebsd.org (Postfix) with ESMTP id 077BA37B598; Thu, 17 Feb 2000 19:12:29 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ive6ha.dialup.mindspring.com [165.247.26.42]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id WAA16688; Thu, 17 Feb 2000 22:12:26 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id WAA00494; Thu, 17 Feb 2000 22:12:19 -0500 (EST) (envelope-from vsilyaev) Date: Thu, 17 Feb 2000 22:12:19 -0500 From: "Vladimir N. Silyaev" To: nsayer@FreeBSD.ORG Cc: emulation@FreeBSD.ORG Subject: Re: Weird AMD panics caused by VMware?! Message-ID: <20000217221219.A448@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-emulation@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > My machine here at the office gets these a _lot_ whenever I'm running > vmware: [skipped] >This machine also seems to hang a lot, but it could be that the hangs >are just these happening behind X so I can't see them. As you wrote below, you are have another box. So just try to use serial console (that will be provide a possibility to always see a panic message), also will be a right thing to compile kernel with DDB, that will provide some more information. > They always happen with amd as the current process. They frequently > happen when >vmware is running. They never happen at other times. The FreeBSD vmmon has a 'historical' bug - it's clear 'GS' register. But I was never encounter problem with them. And more I was so impressed by the fact that I was never encountered any vmware(vmmon) related problem. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-emulation" in the body of the message