From owner-freebsd-stable Thu Jul 13 9:26:49 2000 Delivered-To: freebsd-stable@freebsd.org Received: from medianstrip.net (medianstrip.net [206.113.38.30]) by hub.freebsd.org (Postfix) with ESMTP id 344E037C4C9 for ; Thu, 13 Jul 2000 09:26:41 -0700 (PDT) (envelope-from msr@elision.org) Received: by medianstrip.net (Postfix, from userid 1000) id 2646658E6; Thu, 13 Jul 2000 12:26:35 -0400 (EDT) Date: Thu, 13 Jul 2000 12:26:35 -0400 From: mike ryan To: freebsd-stable@freebsd.org Subject: Re: vmware2 and xfree86-4.0.1 Message-ID: <20000713122635.A67937@medianstrip.net> Mail-Followup-To: freebsd-stable@freebsd.org References: <200007131544.LAA21770@tangerine.uucom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200007131544.LAA21770@tangerine.uucom.com>; from mwhalen@uucom.com on Thu, Jul 13, 2000 at 11:44:17AM -0400 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jul 13, 2000 at 11:44:17AM -0400, Matthew Whalen wrote: > > I have a new machine that I'm trying to configure. It's very similar > to my regular home machine (PIII 700 vs K7 700). They both run > 4.0-stable (home was build last about 1 month ago, new machine yesterday). > I have xf86 4 on this new machine, and 3 at home. > > My vmware on the new machine dies cathing with a SIGSEGV and "Abort trap" > being printed to the screen. I know that vmware doesn't officially support > XF86 4, but this doesn't really sound a lot like an Xserver problem > to me. There isn't much in the vmware log to note. Has anyone tried > vmware2 with XF86 4 yet? If so, did you get the same result? Is there > something else going on? i've had the same result. i'm also running 4.0-stable built within the last few days and xfree86 4.0.1, on a sony vaio z505hs laptop. on my system at least, there appears to be a correlation with disk modes -- virtual machines configured with raw disks abort on boot, virtual machines with virtual disks work fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message