From owner-freebsd-emulation@FreeBSD.ORG Fri Jun 13 07:16:28 2003 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C1A8737B401 for ; Fri, 13 Jun 2003 07:16:28 -0700 (PDT) Received: from plab.ku.dk (plab.ku.dk [130.225.107.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id B10B643FB1 for ; Fri, 13 Jun 2003 07:16:26 -0700 (PDT) (envelope-from tolid@plab.ku.dk) Received: from plab.ku.dk (localhost [127.0.0.1]) by plab.ku.dk (8.12.9/8.12.5) with ESMTP id h5DEGO3Z009373 for ; Fri, 13 Jun 2003 16:16:24 +0200 (CEST) (envelope-from tolid@plab.ku.dk) Received: (from root@localhost) by plab.ku.dk (8.12.9/8.12.9/Submit) id h5DEGOim009372 for freebsd-emulation@freebsd.org.KAV; Fri, 13 Jun 2003 16:16:24 +0200 (CEST) Received: from plab.ku.dk (localhost [127.0.0.1]) by plab.ku.dk (8.12.9/8.12.5) with ESMTP id h5DEGO3Z009364; Fri, 13 Jun 2003 16:16:24 +0200 (CEST) (envelope-from tolid@plab.ku.dk) Received: (from tolid@localhost) by plab.ku.dk (8.12.9/8.12.9/Submit) id h5DEGOdU009363; Fri, 13 Jun 2003 16:16:24 +0200 (CEST) Date: Fri, 13 Jun 2003 16:16:24 +0200 From: Anatoliy Dmytriyev To: freebsd-stable@freebsd.org Message-ID: <20030613141624.GA8326@plab.ku.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.4i X-Operating-System: FreeBSD 4.8-STABLE Organization: The Protein Laboratory, University of Copenhagen cc: freebsd-emulation@freebsd.org cc: freebsd-questions@freebsd.org Subject: vmware2 VMware Workstation PANIC: BUG F(571):1607 bugNr=2302 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 14:16:29 -0000 Hello, all! Suddenly, after upgrading of my FreeBSD-Stable box I got message from VMWare: VMware Workstation PANIC: BUG F(571):1607 bugNr=2302. Anybody can help me to fix this bug? (I tryed back to 4.8-release but it didn't help ...) Best regards, Anatoliy Dmytriyev