From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs udev 039
Date: Mon, 18 Oct 2004 14:44:52 +0000 [thread overview]
Message-ID: <20041018144452.GC6821@vrfy.org> (raw)
In-Reply-To: <1098110291.8746.3.camel@localhost>
On Mon, Oct 18, 2004 at 02:38:11PM +0000, Sylvain BERTRAND wrote:
> Was told to send those log messages to this mailing list...
> Do not hesitate to contact me for information on my system.
>
> Oct 18 16:17:30 zeus wait_for_sysfs[6352]: either wait_for_sysfs (udev
> 039) needs an update to handle the device '/class/vc/vcsa5' properly (3)
> or the sysfs-support of your device's driver needs to be fixed, please
> report to <linux-hotplug-devel@lists.sourceforge.net>
It is caused by the fact, that the vc devices are creating events for every
open() and close(), as this seems to happen multiple times on bootup for every
device, it sometimes just disappeares before we can wait for it. This if hopefully
fixed with the next version.
Thanks,
Kay
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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
prev parent reply other threads:[~2004-10-18 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 14:38 wait_for_sysfs udev 039 Sylvain BERTRAND
2004-10-18 14:44 ` Kay Sievers [this message]
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=20041018144452.GC6821@vrfy.org \
--to=kay.sievers@vrfy.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).