From owner-freebsd-hackers@FreeBSD.ORG Sun Jul 1 15:57:32 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 161FD1065672 for ; Sun, 1 Jul 2012 15:57:32 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id DDAF28FC0C for ; Sun, 1 Jul 2012 15:57:31 +0000 (UTC) Received: by pbbro2 with SMTP id ro2so7118020pbb.13 for ; Sun, 01 Jul 2012 08:57:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=zNnkOVOMNVXg9apIQccztFFItoUZ+wQKcsxBr306G0s=; b=yxQX2j5X+s+D1y3awSHhmQ4azVv0ksSmyfZJKXND8OkYk1E9BgbaG2fNnif2RQ72mP hNBnz8SMB9MFR4bVKLtg2M/hFQYWnma6Pg+148nWm7nGIlj4tlz0nzg7yuEkuJU0AbTd zqnI90ViUiLj7m23qGBmXwQDlrm3zXzu63w2mo7iABQYYZHMOwoA0yqqpRk0+DTBQjlI fHiVrofUfuf0khHnQ6U4vPzO1V67+fkZBIp8gqgmCe5zaJZCz08nHOQcECQto9nKCxyx AqPv4mI8hBjkawq0Aqbhpud3N1PGg2xi0mromtZUoMGdqE/KuxHGqFIyvJn2JtAGWiFU u99w== MIME-Version: 1.0 Received: by 10.66.73.69 with SMTP id j5mr8645590pav.8.1341158251411; Sun, 01 Jul 2012 08:57:31 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.195.102 with HTTP; Sun, 1 Jul 2012 08:57:31 -0700 (PDT) In-Reply-To: <4FEE0D2F.4010808@rawbw.com> References: <4FEE0D2F.4010808@rawbw.com> Date: Sun, 1 Jul 2012 08:57:31 -0700 X-Google-Sender-Auth: BKZXnOTvqEmnMmSdff0SAA1lGw8 Message-ID: From: Adrian Chadd To: Yuri Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 01 Jul 2012 15:57:32 -0000 Ah! I'm not the only person seeing this. On 29 June 2012 13:16, Yuri wrote: > When I run dtrace script (attached) on 9.0 amd64 with kde4 I see a lot of > failed read(2) calls from the xorg socket /tmp/.X11-unix/X0 . > This can't be right in my opinion. This means that code keeps reading from > this socket and failing, instead of using select(2) or kquere(2). > Requests mostly come from kdeinit4 but some also from kwin, chrome and even > Xorg itself. > Rate of failure for read(2) calls is ~2500/sec systemwide. > > This is of course not a deadly problem. > But is this situation considered to be normal? I haven't yet done digging to see if poll() is returning the xorg socket as being ready. I think that's worth doing. And it's a huge problem for battery consumption. :) Adrian