[udev/vcs] tons of creating/removing /dev/vcs* during boot

linux

[udev/vcs] tons of creating/removing /dev/vcs* during boot

Postby Edgar Toernig » Wed, 14 Sep 2005 00:20:17 GMT

Hi,

switching from SuSE's 2.6.11.4 to vanilla 2.6.13 I noticed
that I get tons of these lines in the log during boot:

udev[2124]: configured rule in '/etc/udev/rules.d/50-udev.rules[98]' ...
udev[2121]: creating device node '/dev/vcs5'
udev[2124]: creating device node '/dev/vcsa3'
udev[2140]: configured rule in '/etc/udev/rules.d/50-udev.rules[98]' ...
udev[2144]: configured rule in '/etc/udev/rules.d/50-udev.rules[98]' ...
udev[2140]: creating device node '/dev/vcs3'
udev[2144]: creating device node '/dev/vcsa6'
udev[2147]: removing device node '/dev/vcs6'
udev[2149]: configured rule in '/etc/udev/rules.d/50-udev.rules[98]' ...
udev[2158]: removing device node '/dev/vcs4'
udev[2157]: removing device node '/dev/vcsa3'
udev[2149]: creating device node '/dev/vcsa5'
udev[2172]: configured rule in '/etc/udev/rules.d/50-udev.rules[98]' ....
udev[2171]: removing device node '/dev/vcsa2'
udev[2172]: creating device node '/dev/vcs5'

It's caused by various loadkeys, setleds, etc performed early in an
init script.  It seems, that every open/close of a tty generates
a hotplug event for the appropriate vcs/vcsa device.  It stops at
the moment gettys are spawned.

Looking at the 2.6.11.4 source of drivers/char/vc_screen.c I see
that hotplug events are explicitly disabled for the vcs and vcsa
devices (not sure whether this was done by SuSE).  In 2.6.13 all
of that code is gone, including the class_simple that was used to
disable hotplug events.

How can I avoid all of these hotplug events?  Best would be of
course to generate only a single event at the same time the
tty device is create.  But I could also live with no hotplug
events for vcs* at all.

Ciao, ET.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to  XXXX@XXXXX.COM 
More majordomo info at   http://www.**--****.com/ 
Please read the FAQ at   http://www.**--****.com/ 

Re: [udev/vcs] tons of creating/removing /dev/vcs* during boot

Postby Greg KH » Wed, 14 Sep 2005 15:00:09 GMT



Yes, this was a SUSE change, that's never been in mainline.


Well, consider it "never present" instead of gone :)


Why do you want to?  You need them in order to create the proper device
node for the virtual terminal, right?

And, if you use the latest versions of udev, no hotplug events need
cause a program execute, udev can watch the hotplug netlink socket and
just act on it, _very_ quickly.  So quickly you will not even care I
bet...


That's what you are seeing.  And then watching as it's being destroyed.
And then created.  And then destroyed.  And so on (virtual ttys are
{*filter*} at times..)


You would not be able to use them if you use udev then :(

Seriously, try the latest udev, with the netlink socket, and see if it
still matters anymore.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to  XXXX@XXXXX.COM 
More majordomo info at   http://www.**--****.com/ 
Please read the FAQ at   http://www.**--****.com/ 

Re: [udev/vcs] tons of creating/removing /dev/vcs* during boot

Postby Andreas Jellinghaus » Wed, 14 Sep 2005 22:20:12 GMT



wait a second, the kernel code opens /dev/console before running
init. so that should trigger that first hotplug event. and if
init is a process that does not close stdin/out/err, there should
not be any additional hotplug event, right?

I know for sure that some gentoo machine created > 3000 hotplug
events during bootup. I'm note sure if the init closed stdin/out/err,
and that installation was replaced by debian anyway, but it sure
killed the machine, if I hadn't disabled hotplugging (3000 bash
processes need more ram than a normal machine has).

init strarts processes and those sure have stdin/out/err open,
so they can write to the console. so I somehow doubt it closes
and opens those all the time, but I haven't checked the code.
so I wonder: is or was there any bug in the kernel where hundreds
or thousands of hotplug requests are created, simply because
processed are executed? 

it is a fact I saw thousands of hotplug events during a boot sequence.
I'd like to know why that happened, and whether it would happen again.
rm -rf /sbin/hotplug and switching to udevd is once option to solve
the problem, but not an explanation why it happened in the first place.

Regards, Andreas
p.a. I don't use udevd, but my initramfs disables hotplug and
the last initscript enables it again. also works ok.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to  XXXX@XXXXX.COM 
More majordomo info at   http://www.**--****.com/ 
Please read the FAQ at   http://www.**--****.com/ 

Similar Threads:

1./dev/vcs or /dev/tty local colormap retrieving

2.udev and /dev/sda1 not found during boot (it's there right after boot)

3.udev and /dev/sda1 not found during boot (it's there right after boot)

4./dev/vcs: stuck with dimensions <255?

5.Creating a redundant server and VCS

Hi,

I'm planning to create a redundant server with following services, so
that in case one server fails, my another server can serve, and also
share load with other server:

* ISC dhcpd
* BIND
* Postfix
* NFS4
* MySQL
* Apache httpd 2.2
* Puppet
* OpenLDAP
* Subversion (or any other VCS (version control system), currently not
running any)

I've never done such thing in past, so can somebody tell me what
solutions (FOSS) are available ?

Is it possible to create a Pentium 4 (or Pentium D or Core 2 Duo)
based redunant server(s) for a Xeon based server ?

I'm not running any SAN or NAS box, so I want storage to reside on
redunant servers and also kept in sync. So, is clustering filesystems
e.g. GFS, recommended for such application ?

I'm not planning to run any compute cluster.

I'm planning to build this with Debian "Etch" or CentOS 5 with SELinux
enabled in enforcing mode. All my clients are running Fedora 7
(SELinux in enforcing mode).

I'm also considering installing a VCS for collaborative editing of
documents (not source code) by users to avoid having redundant,
sometimes out-of-sync copies of the same documents. So is running a
VCS for such recommended.

Thanks in advance
Ashish Shukla

6. vc: create vcs(a) devices for consoles

7. RocketIO simulation w ISE6.2iSP3 and VCS-7.1.1 under Linux

8. VCs regain interest in open source



Return to linux

 

Who is online

Users browsing this forum: No registered users and 10 guest