From: Alex Murray <alexander.murray@student.adelaide.edu.au>
To: linux-hotplug@vger.kernel.org
Subject: Error Messages on boot-up
Date: Sun, 10 Oct 2004 23:49:03 +0000 [thread overview]
Message-ID: <1097451423.8894.2.camel@enigma> (raw)
here is an except of my log during boot
I am getting a whole bunch of error (presumably from udev):
..........
Oct 11 09:01:31 enigma syslog-ng[6781]: syslog-ng version 1.6.5 starting
Oct 11 09:01:34 enigma cron[7791]: (CRON) STARTUP (fork ok)
Oct 11 09:01:34 enigma init: Activating demand-procedures for 'A'
Oct 11 09:01:34 enigma wait_for_sysfs[5687]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcs4' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:35 enigma wait_for_sysfs[5787]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcs7' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:35 enigma wait_for_sysfs[6128]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcs7' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:35 enigma wait_for_sysfs[6159]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcs8' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:35 enigma wait_for_sysfs[6214]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcs10' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:35 enigma wait_for_sysfs[6227]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcsa9' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:35 enigma wait_for_sysfs[6228]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcsa10' properly, please
report to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:39 enigma wait_for_sysfs[7530]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcsa9' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:39 enigma wait_for_sysfs[7544]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcs10' properly, please report
to <linux-hotplug-devel@lists.sourceforge.net>
Oct 11 09:01:39 enigma wait_for_sysfs[7561]: error: wait_for_sysfs needs
an update to handle the device '/class/vc/vcsa11' properly, please
report to <linux-hotplug-devel@lists.sourceforge.net>
from here the log is as normal.
Cheers
-------------------------------------------------------
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
next reply other threads:[~2004-10-10 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-10 23:49 Alex Murray [this message]
2004-10-11 22:55 ` Error Messages on boot-up Greg KH
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=1097451423.8894.2.camel@enigma \
--to=alexander.murray@student.adelaide.edu.au \
--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).