public inbox for gentoo-alpha@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrew Gaylard <ag@computer.org>
To: gentoo-alpha@lists.gentoo.org
Subject: Re: [gentoo-alpha] udev-208 eats CPU
Date: Wed, 12 Feb 2014 19:48:00 +0200	[thread overview]
Message-ID: <52FBB3D0.3070209@computer.org> (raw)
In-Reply-To: <CAEdQ38GdS=86EN-CUQwKJWuXzshW-nyV=Yec2vRMTY_i55HtWA@mail.gmail.com>

On 01/19/14 01:20, Matt Turner wrote:
> On Sun, Jan 12, 2014 at 12:33 PM, Andrew Gaylard <ag@computer.org> wrote:
>> Hi,
>>
>> I have just upgraded to the latest build of udev (208) on my Alpha box.
>> It appears to run at 100% of CPU.  When I enable debugging, I get these
>> lines in /var/log/messages:
>>
>>      unable to receive ctrl connection: Function not implemented
>>
>> This appears to be due to the lack of the accept4 call.
>>
>> However, my kernel is gentoo-sources-3.10.7 and my glibc is 2.17,
>> so I'd expect this call to be there.... Right?
> Yes, as Alan said accept4 has been supported in the kernel since v3.2.
>
> I'm running udev-208 on a couple of alphas without trouble, so this
> problem should be fixable.
>
> Is it possible that your glibc was built against linux-headers older
> than v3.2? Seems unlikely, but it's probably the first thing I'd
> check.
Yup, you were right.  I had sys-kernel/linux-headers 2.6.<something>.
Upgrading that to 3.9 and then rebuilding glibc and udev fixed it.

Thanks!

I'm a bit puzzled why "emerge -uva @system"  and "emerge -uva @world"
didn't automatically upgrade linux-headers.  I had to explicitly request it.
But hey, it's working now...:)

-- 
Andrew Gaylard



  reply	other threads:[~2014-02-12 17:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 20:33 [gentoo-alpha] udev-208 eats CPU Andrew Gaylard
2014-01-13  8:13 ` [gentoo-alpha] " Andrew Gaylard
2014-01-14  1:53   ` Alan Young
2014-01-18 23:20 ` [gentoo-alpha] " Matt Turner
2014-02-12 17:48   ` Andrew Gaylard [this message]
2014-02-12 20:15     ` [gentoo-alpha] " Måns Rullgård
2014-02-14  9:27       ` Andrew Gaylard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52FBB3D0.3070209@computer.org \
    --to=ag@computer.org \
    --cc=gentoo-alpha@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox