From owner-freebsd-current@FreeBSD.ORG Tue Aug 17 18:00:38 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5081816A4CF for ; Tue, 17 Aug 2004 18:00:38 +0000 (GMT) Received: from green.homeunix.org (pcp04371970pcs.nrockv01.md.comcast.net [69.140.223.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id D997143D5F for ; Tue, 17 Aug 2004 18:00:31 +0000 (GMT) (envelope-from green@green.homeunix.org) Received: from green.homeunix.org (green@localhost [127.0.0.1]) by green.homeunix.org (8.13.1/8.13.1) with ESMTP id i7HHxwMK036190; Tue, 17 Aug 2004 13:59:58 -0400 (EDT) (envelope-from green@green.homeunix.org) Received: (from green@localhost) by green.homeunix.org (8.13.1/8.13.1/Submit) id i7HHxjoP036189; Tue, 17 Aug 2004 13:59:45 -0400 (EDT) (envelope-from green) Date: Tue, 17 Aug 2004 13:59:45 -0400 From: Brian Fundakowski Feldman To: Rob MacGregor Message-ID: <20040817175945.GP980@green.homeunix.org> References: <20040817142818.GO980@green.homeunix.org> <200408171533.i7HFXMw1025005@the-macgregors.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408171533.i7HFXMw1025005@the-macgregors.org> User-Agent: Mutt/1.5.6i cc: current@freebsd.org Subject: Re: lnc0 in VmWare doesn't work X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Aug 2004 18:00:38 -0000 On Tue, Aug 17, 2004 at 04:33:23PM +0100, Rob MacGregor wrote: > On Tuesday, August 17, 2004 3:28 PM, Brian Fundakowski Feldman > danced on the keyboard and produced: > > Why aren't you reading what I posted? If lnc doesn't work, > > it's probably > > because there's some extra constraint on the usable memory range that > > is incorrectly specified in the driver. You should try to get VMWare > > to give you information on that, since you're a customer. > > Ah, my bad. I did read what you posted, but saw another post that reported a > breakage, but didn't appear to reference VMWare. > > Having a closer look, it *does* reference VMWare. I'll go flag the bug up on > their boards. Sorry. Thanks; Occam's razor says that this is almost certainly due to the fact that the new contigmalloc allocates from the top instead of the bottom of the range you give it. -- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\