From owner-freebsd-current@FreeBSD.ORG Fri Dec 23 23:49:15 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 E9E0A16A41F for ; Fri, 23 Dec 2005 23:49:15 +0000 (GMT) (envelope-from jasone@freebsd.org) Received: from lh.synack.net (lh.synack.net [204.152.188.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id B248643D72 for ; Fri, 23 Dec 2005 23:49:07 +0000 (GMT) (envelope-from jasone@freebsd.org) Received: by lh.synack.net (Postfix, from userid 100) id 8EFEA5E48D8; Fri, 23 Dec 2005 15:49:07 -0800 (PST) Received: from [192.168.168.203] (moscow-cuda-gen2-68-64-60-20.losaca.adelphia.net [68.64.60.20]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by lh.synack.net (Postfix) with ESMTP id A053C5E48B4; Fri, 23 Dec 2005 15:49:04 -0800 (PST) In-Reply-To: <20051223094018.GA25562@soaustin.net> References: <20051223094018.GA25562@soaustin.net> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <69D03F43-D467-4AD2-92AB-378F5CF4C00F@freebsd.org> Content-Transfer-Encoding: 7bit From: Jason Evans Date: Fri, 23 Dec 2005 15:49:01 -0800 To: Mark Linimon X-Mailer: Apple Mail (2.746.2) X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on lh.synack.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-current@freebsd.org Subject: Re: New malloc ready, take 42 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 23 Dec 2005 23:49:16 -0000 On Dec 23, 2005, at 1:40 AM, Mark Linimon wrote: > On Fri, Dec 23, 2005 at 01:14:08AM -0800, Jason Evans wrote: >> * Claus Guttesen and Devon O'Dell reported issues in kldxref and X on >> amd64 [ ... ] Apparently, we are on the cusp of the transition to >> using >> [latest xorg], so for now the workaround on amd64 is to use xorg- >> server- >> snap, with the expectation that soon the standard xorg-server port >> will be upgraded. > > I think it's fair to ask if anyone has attempted to find out if > there are > similar problems with XFree86 on either i386 or amd64. I don't > know if > there is any appreciable install base for the latter but AFAICT > there still > is for the former. > > At least we ought to know yea or nay before making the switch, IMHO. I just checked XFree86-4 on i386, and it works fine. I already returned the amd64 machine I was borrowing, so I can't check that. My expectation is that XFree86 has the same issue as xorg on amd64. Thanks, Jason