From owner-freebsd-hackers@FreeBSD.ORG Mon Jul 2 23:14:30 2012 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4952C1065678; Mon, 2 Jul 2012 23:14:30 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 2A3838FC0C; Mon, 2 Jul 2012 23:14:30 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id q62NEJ67065442; Mon, 2 Jul 2012 16:14:22 -0700 (PDT) (envelope-from yuri@rawbw.com) Message-ID: <4FF22B46.4000301@rawbw.com> Date: Mon, 02 Jul 2012 16:14:14 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120702 Thunderbird/13.0.1 MIME-Version: 1.0 To: Adrian Chadd References: <4FEE0D2F.4010808@rawbw.com> <4FF0AEE1.5040607@rawbw.com> <4FF0C352.6010805@rawbw.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-hackers@freebsd.org Subject: Re: System is flooded with failed read(2) calls: Resource temporarily unavailable (errno=35) coming from xorg unix socket X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jul 2012 23:14:30 -0000 > Ok, so something is really really odd here. Are you able to dig deeper > into what the socket code in xorg is doing wrong? It'd certainly be > nice to fix all of this stuff up. > > Thanks so much for digging into this! It's been annoying me, but I've > just been ridiculously busy trying to bring up some more Atheors wifi > chipset support in FreeBSD. Now it is clear what is happening. Xlib routinely calls read one more time during every X-protocol call one extra time, kinda just in case. And such calls always fail with EAGAIN, unless disconnect or socket error happens to happen at this time. This essentially about doubles the number of system calls that any X app makes. Yuri