Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 4 Mar 2007 01:05:53 -0500
From:      Yoshihiro Ota <ota@j.email.ne.jp>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        Randall Stewart <rrs@cisco.com>, Scott Robbins <scottro@nyc.rr.com>, "Stephane E. Potvin" <sepotvin@FreeBSD.org>, brooks@FreeBSD.org, current@FreeBSD.org
Subject:   Re: HEADS UP: UNIX domain socket locking changes merged to CVS HEAD
Message-ID:  <20070304010553.4c288aa6.ota@j.email.ne.jp>
In-Reply-To: <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> <20070303221906.I60688@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 3 Mar 2007 22:21:16 +0000 (GMT)
Robert Watson <rwatson@FreeBSD.org> wrote:

> 
> 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

I changed to uipc_usrreq.c 1.199 to 1.196 and I already had unpcb.h 1.11.  After rebooting, the problem still remains.

The below is what I got from ktrace/kdump run on uipc_usrreq.c@1.199.  I think I started seeing this problem on last Sat. or Sun day.

It seems that when I kill kinput2, canna dies together so that when I see like this:

$ sh /usr/local/etc/rc.d/canna.sh stop
Cannot connect with cannaserver "unix".

% ktrace -f ktrace.out 

  1274 kinput2  RET   poll 1
  1274 kinput2  CALL  poll(0x88450fb0,0x2,0)
  1274 kinput2  RET   poll 1
  1274 kinput2  CALL  poll(0x88450fb0,0x2,0)
  1274 kinput2  RET   poll 1

%grep poll ktrace.txt | wc
  621264 2795688 22986795



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070304010553.4c288aa6.ota>