System is flooded with failed read(2) calls: Resource temporarily unavailable (errno=35) coming from xorg unix socket

[Adrian Chadd]

Ah! I'm not the only person seeing this.

On 29 June 2012 13:16, Yuri <yuri at rawbw.com> 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