From owner-freebsd-current@FreeBSD.ORG Thu Aug 27 11:58:54 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 94624106568B for ; Thu, 27 Aug 2009 11:58:54 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward1.yandex.ru (forward1.yandex.ru [77.88.46.6]) by mx1.freebsd.org (Postfix) with ESMTP id 4CF5F8FC3A for ; Thu, 27 Aug 2009 11:58:54 +0000 (UTC) Received: from smtp5.yandex.ru (smtp5.yandex.ru [77.88.47.12]) by forward1.yandex.ru (Yandex) with ESMTP id BDBA9146829B; Thu, 27 Aug 2009 15:58:52 +0400 (MSD) Received: from [127.0.0.1] (ns.kirov.so-cdu.ru [77.72.136.145]) by smtp5.yandex.ru (Yandex) with ESMTPSA id 8C1927980F3; Thu, 27 Aug 2009 15:56:07 +0400 (MSD) Message-ID: <4A9674F8.10605@yandex.ru> Date: Thu, 27 Aug 2009 15:58:48 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: "b. f." References: In-Reply-To: Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit X-Yandex-TimeMark: 1251374167 X-Yandex-Spam: 1 X-Yandex-Front: smtp5.yandex.ru Cc: freebsd-current@FreeBSD.org Subject: Re: problems with XFCE on 9.0-CURRENT 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: Thu, 27 Aug 2009 11:58:54 -0000 b. f. wrote: >> #0 0x28df034f in poll () from /lib/libc.so.7 >> #1 0x28d52c42 in poll () from /lib/libthr.so.3 > > I'm guessing that this is due to the recent polling revisions: > > http://svn.freebsd.org/changeset/base/195423 > http://svn.freebsd.org/changeset/base/196460 > > For more information, see the related discussion on svn-src-all@ . It > looks like additional changes will be made when the committers reach a > consensus on what to do, and these additional changes may solve your > problem. In the meantime, if you have a kernel more recent than > r196460 and your problem exists when using it, you could try reverting > one or both of these revisions. You should probably bring this to the Thank you. I updated my kernel and it seems it is fixed in r196556. -- WBR, Andrey V. Elsukov