From owner-freebsd-stable@FreeBSD.ORG Fri Jul 3 11:23:05 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C8581065676 for ; Fri, 3 Jul 2009 11:23:05 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 208B88FC14 for ; Fri, 3 Jul 2009 11:23:04 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lstewart-laptop.caia.swin.edu.au (host86-150-124-14.range86-150.btcentralplus.com [86.150.124.14]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n63B2UXU089959 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Jul 2009 21:02:35 +1000 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4A4DE53D.2010704@freebsd.org> Date: Fri, 03 Jul 2009 12:02:21 +0100 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.22 (X11/20090626) MIME-Version: 1.0 To: Dominic Fandrey References: <4A4DD9E9.6080206@bsdforen.de> In-Reply-To: <4A4DD9E9.6080206@bsdforen.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=0.8 required=5.0 tests=AWL,BAYES_40,RCVD_IN_PBL, RDNS_DYNAMIC,SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-stable@freebsd.org Subject: Re: good old intel troubles X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jul 2009 11:23:05 -0000 Dominic Fandrey wrote: > Now that the intel driver is stable and performs well, again, it's > time to start complainig about all the things that still do not work. > > This is basically going to the console and back. Well, it actually > works but X will entirely lock up unless the mouse is in motion. > It's not hard to imagine that this is really bad. With violent mouse > movement I can get glxgears to render 0.3 frames per second. > That's it. 1 frame every 3 seconds. > > Back on the console everything is fine, so it's really just X > misbehaving. No scheduling issue or the like. > These issues have been recently addressed in 8-CURRENT. I assume some MFCs will happen at some point. Cheers, Lawrence