From: Michael Geithe <warpy@gmx.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev-36
Date: Wed, 13 Oct 2004 20:40:57 +0000 [thread overview]
Message-ID: <200410132240.57652.warpy@gmx.de> (raw)
In-Reply-To: <200410131642.28947.warpy@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
Hi,
here is the output
ACTION=add DEVPATH=/class/vc/vcs3 /sbin/./wait_for_sysfs vc
wait_for_sysfs[29818]: main: class_device opened '/sys/class/vc/vcs3'
wait_for_sysfs[29818]: wait_for_class_device_attributes: looking at class 'vc'
for specific file 'dev'
wait_for_sysfs[29818]: wait_for_class_device_attributes: class 'vc' specific
file 'dev' found
wait_for_sysfs[29818]: main: no device symlink expected for 'vcs3',
wait_for_sysfs[29818]: main: result: waiting for sysfs successful
'/class/vc/vcs3'
> Hm, how fast is your processor on this machine? I'd think you shouldn't
> be seeing these messages anymore, unless you have a pretty slow box.
>
> > wait_for_sysfs[8588]: error: wait_for_sysfs needs an update to handle the
> > device '/class/i2c-dev/i2c-1' properly (6), please report to
> > <linux-hotplug-devel@lists.sourceforge.net>
>
> Can you send the output of 'tree /sys/class/i2c-dev/i2c-1' to us?
>
> thanks,
>
> greg k-h
and a reboot.
Attached -syslog
Thanks
--
Michael Geithe
[-- Attachment #2: syslog.tar.gz --]
[-- Type: application/x-tgz, Size: 25063 bytes --]
next prev parent reply other threads:[~2004-10-13 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 14:42 udev-36 Michael Geithe
2004-10-13 18:22 ` udev-36 Kay Sievers
2004-10-13 20:20 ` udev-36 Greg KH
2004-10-13 20:40 ` Michael Geithe [this message]
2004-10-13 21:42 ` udev-36 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=200410132240.57652.warpy@gmx.de \
--to=warpy@gmx.de \
--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).