From: Angel Sotirov <angel@devbg.piranko.com>
To: linux-hotplug@vger.kernel.org
Subject: infinitely many events 2.6.23
Date: Tue, 16 Oct 2007 22:30:28 +0000 [thread overview]
Message-ID: <47153B84.5020609@devbg.piranko.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Since upgrading to 2.6.23, udev-116. there are infinitely events
trying to add and remove the same virtual console.
UEVENT[1192572769.073098] remove /devices/virtual/vc/vcs10 (vc)
UEVENT[1192572769.073171] remove /devices/virtual/vc/vcsa10 (vc)
UEVENT[1192572769.865255] add /devices/virtual/vc/vcs10 (vc)
UEVENT[1192572769.865303] add /devices/virtual/vc/vcsa10 (vc)
UEVENT[1192572769.865808] remove /devices/virtual/vc/vcs10 (vc)
UEVENT[1192572769.865857] remove /devices/virtual/vc/vcsa10 (vc)
UEVENT[1192572773.527231] add /devices/virtual/vc/vcs10 (vc)
UEVENT[1192572773.527278] add /devices/virtual/vc/vcsa10 (vc)
any idea what could be triggering this ?
Angel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
iD8DBQFHFTuDhgSIDFxSFd0RAli6AJ90IBw5j62LbISRR62zHEEsnlBGAwCg0srr
bvIoYbAX6JWhw5K73Qne7po=r4NU
-----END PGP SIGNATURE-----
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-10-16 22:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 22:30 Angel Sotirov [this message]
2007-10-18 17:43 ` infinitely many events 2.6.23 Kay Sievers
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=47153B84.5020609@devbg.piranko.com \
--to=angel@devbg.piranko.com \
--cc=linux-hotplug@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.