From owner-freebsd-current@FreeBSD.ORG Sat Mar 3 22:21:17 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C15516A403; Sat, 3 Mar 2007 22:21:17 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.freebsd.org (Postfix) with ESMTP id 0C0DD13C48E; Sat, 3 Mar 2007 22:21:17 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 954B346CE5; Sat, 3 Mar 2007 17:21:16 -0500 (EST) Date: Sat, 3 Mar 2007 22:21:16 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Yoshihiro Ota In-Reply-To: <20070302234750.7b57c23c.ota@j.email.ne.jp> Message-ID: <20070303221906.I60688@fledge.watson.org> References: <20070226204916.C56223@fledge.watson.org> <45E5D589.3080202@FreeBSD.org> <20070228234754.Q13593@fledge.watson.org> <45E6178F.8040302@cisco.com> <20070301031907.GD94643@mail.scottro.net> <45E67908.9090707@cisco.com> <20070301090253.M13593@fledge.watson.org> <45E69EE3.9010407@cisco.com> <20070302005803.GC26188@mail.scottro.net> <45E82030.7000402@cisco.com> <20070302132436.GB46154@mail.scottro.net> <20070302234750.7b57c23c.ota@j.email.ne.jp> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Randall Stewart , Scott Robbins , "Stephane E. Potvin" , brooks@FreeBSD.org, current@FreeBSD.org Subject: Re: HEADS UP: UNIX domain socket locking changes merged to CVS HEAD 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: Sat, 03 Mar 2007 22:21:17 -0000 On Fri, 2 Mar 2007, Yoshihiro Ota wrote: > My X runs fine but I think I am still seeing this problem with diffrent > ports. > > They are japanese/Canna japanese/kinput2-canna. > > Canna uses "unix" domain socket to communicate and it still doesn't work. > Before, Canna reproted some "unix" domain socket error. Now, it doesn't > report such errors but "kinput2" stucks. > > Installing kinput2-cann will install Canna as well. You will need these 2 > entries to run Canna. > > canna_enable="YES" canna_flags="-u bin inet" > > Then, you need the following to allow to use kinput from X terminals. > > setenv XMODIFIERS '@im=kinput > > Once you start canna, run "kinput2" in one of the X terminals. Then, > kinput2 eats all CPU. Could you confirm that if you run the code precisely before the commits in question (i.e., back out to uipc_usrreq.c:1.196 and unpcb.h:1.22) the problem goes away completely? If so, could you try running ktrace on kinput2 and see if it's looping around any particular syscalls and getting an error repeatedly? It could be that an error is now (possibly incorrectly) being returned and that kinput2 is not handling that well. Robert N M Watson Computer Laboratory University of Cambridge