From owner-freebsd-stable@FreeBSD.ORG Thu Jan 29 12:06:49 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 E14791065718 for ; Thu, 29 Jan 2009 12:06:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from out4.smtp.messagingengine.com (out4.smtp.messagingengine.com [66.111.4.28]) by mx1.freebsd.org (Postfix) with ESMTP id 8EC918FC12 for ; Thu, 29 Jan 2009 12:06:48 +0000 (UTC) (envelope-from bms@FreeBSD.org) Received: from compute1.internal (compute1.internal [10.202.2.41]) by out1.fastmail.fm (Postfix) with ESMTP id AED6D26289B; Thu, 29 Jan 2009 07:06:47 -0500 (EST) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute1.internal (MEProxy); Thu, 29 Jan 2009 07:06:47 -0500 X-Sasl-enc: L8Jaf6YNvIDZNO+pZrygh/KgBbxqxh6TYdTelLYKMfCf 1233230807 Received: from empiric.lon.incunabulum.net (82-35-112-254.cable.ubr07.dals.blueyonder.co.uk [82.35.112.254]) by mail.messagingengine.com (Postfix) with ESMTPSA id DAB9134C32; Thu, 29 Jan 2009 07:06:46 -0500 (EST) Message-ID: <49819BD5.5040709@FreeBSD.org> Date: Thu, 29 Jan 2009 12:06:45 +0000 From: "Bruce M. Simpson" User-Agent: Thunderbird 2.0.0.19 (X11/20090126) MIME-Version: 1.0 To: Alex Goncharov References: <6B7ABE80-35AB-4C44-B5A4-200E10DCC3AC@airwired.net> In-Reply-To: X-Enigmail-Version: 0.95.6 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dan Allen , freebsd-stable@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Unhappy Xorg upgrade 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: Thu, 29 Jan 2009 12:07:21 -0000 Alex Goncharov wrote: > I hate to say this, but the new X (as exists in the current FreeBSD > ports) sucks and gets in the way of work big time. > > There are definitely issues with xorg-7.4 at the moment. The root issue seems to be that USB mice simply don't work for me, and running Xorg appears to destabilise the 7-STABLE USB stack in some way which I just don't understand. The condition isn't recoverable without a reboot. I am the only person who's reported these symptoms in any great detail yet. I spent a lot of time yesterday debugging with rnoland@ the USB problem I've been having. He sent me a patch, however, it doesn't solve the problem. My understanding is that a lot has changed in this Xorg release to do with input drivers, specifically mouse -- and that platform specific code got shuffled off out of the server itself, and into the drivers. Good from an academic software engineering point of view, but if this is the cause, not good from a regression point of view. Whilst bisecting all the conditions, and tracing it back to this upgrade is easy to do, I can't readily identify the causal relationship -- I don't know what's going on which has broken Xorg for me in this way, and haven't seen anything like this before. Since upgrading, I've seen stability problems with hald enabled. I have had to turn off hald mode on both my laptop and desktop 7-STABLE machines, as it can totally hang the machine, no DDB break, etc. Scanning SVN, nothing appears to have changed in the 7-STABLE train in terms of USB, moused, the ums driver, or anything else. A ktrace of the moused process bound to ums0 goes dead (no I/O, no syscalls) after X is started. One theory is that somehow the mouse driver ioctls which are passed to ums, are somehow hosing USB, although why that would be, I don't understand. ums currently doesn't have driver instrumentation in that path. I pulled a fairly detailed IRC log of my collaborative debugging session with Robert, please ping me if you need details of this. thanks BMS