Bug 215378 - udev eats 100% of cpu when adding 32+ ttys.
Summary: udev eats 100% of cpu when adding 32+ ttys.
Status: CLOSED DUPLICATE of bug 215379
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: udev
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Harald Hoyer
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2006-11-13 18:53 UTC by Scott Kilau
Modified: 2007-11-30 22:07 UTC (History)
0 users

Clone Of:
Last Closed: 2006-11-14 13:36:41 UTC

Attachments (Terms of Use)

Description Scott Kilau 2006-11-13 18:53:47 UTC
Description of problem:
udev eats 100% of cpu for 5+ minutes when adding 32+ ttys using 

Version-Release number of selected component (if applicable):

Latest "up2date" for everything on ES 4.

How reproducible:

Every time.

Steps to Reproduce:
1. Add a driver to system that registers 32 ttys using the tty_register_device
() call in kernel.

2. With or without a "rule" for those devices in /etc/udev/rules.d, it doesn't 

Actual results:

System will literally be bogged down for 5-10 minutes, system hasn't panic'ed, 
but is horribly unresponsive for those 5-10 minutes.

An "uptime" will report load averages past 100!!!
A "ps -ef" (when it eventually responses) shows 100's and 100's of:

/bin/sh /sbin/hotplug tty
/etc/hotplug.d/default/20-hal.hotplug tty

Expected results:

Very minimal cpu usage.

The most important thing here is that under Fedora Core 4, 5 and 6,
this isn't a problem at all!

It works absolutely perfect uder FC 4, 5 and 6!

Additional info:

The udev version that appears to be in use on RH Enterprise 4 is "039".

This is *very* *very* old compared to FC 4, 5 or 6.
udev is currently up to "100" or so now!

I am guessing that something in "udev" has changed in newer versionf of udev 
that makes things work a lot crisper.

Why is udev not being kept up on RH 4?

Comment 1 Harald Hoyer 2006-11-14 13:36:41 UTC

*** This bug has been marked as a duplicate of 215379 ***

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