373575 – sys-fs/udev misbehaves when CONFIG_PRINTK=n

Bug 373575 - sys-fs/udev misbehaves when CONFIG_PRINTK=n

Summary: sys-fs/udev misbehaves when CONFIG_PRINTK=n

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	[OLD] Core system (show other bugs)
Hardware:	All Linux

Importance:	Normal minor (vote)
Assignee:	udev maintainers

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2011-06-30 11:14 UTC by Manuel Lauss
Modified:	2012-07-09 11:55 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Manuel Lauss 2011-06-30 11:14:58 UTC

I built kernels for embedded systems with CONFIG_PRINTK=n,
however udev-171-r1 doesn't like that:
in /etc/init.d/udev, function populate_dev(), the call "udevadm control --property=STARTUP=1" takes over a minute to complete, and subsequently no nodes are created (and system doesn't boot to a login prompt).

Enabling CONFIG_PRINTK=y resolves it, and I realize building a completely silent kernel isn't a particularly good idea, but still it would be nice if udev could cope with it.

Reproducible: Always

Comment 1 Manuel Lauss 2012-07-09 11:55:30 UTC

I'm marking this as resolved: on a current 3.5-rc git kernel,
udev-186 on all my test targets comes up fine with CONFIG_PRINTK=n set.