Bug 305

Summary:	Udev 137 or higher compiled with uclibc seems to fail because of ppoll() system call
Product:	uClibc	Reporter:	Mickaël <mickb>
Component:	Other	Assignee:	unassigned
Status:	RESOLVED FIXED
Severity:	critical	CC:	uclibc-cvs
Priority:	P5
Version:	0.9.30.1
Target Milestone:	---
Hardware:	PC
OS:	Linux
Host:		Target:	i686-pc-linux-uclibc
Build:

Description Mickaël 2009-04-24 08:52:44 UTC

From version 137, udev makes use of ppoll instead of signal pipes. Since this change, Udev still compiles correctly over uclibc, but crashes at execution and returns an error related to ppoll() system call.

This point has been raised deeply in a forum thread, and uclibc is highly suspected to be the origin of the problem:

http://lists.impactlinux.com/pipermail/firmware-impactlinux.com/2009-April/000166.html

Personally, I confirm that udev 136 compiles and works perfectly, but I encounter the same symptom with version 137 and higher, on Linux 2.6.28.9. Cross-compilation toolchain: GCC 4.3.2, binutils 2.19

Comment 1 Bernhard Reutner-Fischer 2009-07-05 20:23:22 UTC

Please provide a small, self-contained testcase that exhibits the problem.

Comment 2 Mike Frysinger 2009-07-20 11:20:06 UTC

presumably you are hitting the bug fixed by commit f82635e74a7e174f71f955eaa4f5dc788e596cc0