From: Jeff <jtw@gwi.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs messages (more debugging info)
Date: Sat, 16 Oct 2004 02:00:47 +0000 [thread overview]
Message-ID: <417080CF.7010402@gwi.net> (raw)
In-Reply-To: <416F09EE.9050205@gwi.net>
Kay Sievers wrote:
> On Fri, 2004-10-15 at 01:42 +0200, Kay Sievers wrote:
>
>>On Thu, Oct 14, 2004 at 07:21:18PM -0400, Jeff wrote:
>>
>>>Sorry to double post but thought with the more verbose debugging this
>>>might help you more:
>>>Oct 14 16:04:00 [wait_for_sysfs] either wait_for_sysfs (udev 038) needs
>>>an update
>>>to handle the device '/class/vc/vcs2' properly (4) or the sysfs-support
>>>of your de
>>>vice's driver needs to be fixed, please report to
>>><linux-hotplug-devel@lists.sourc
>>>eforge.net>
>>
>>Seems like you have the /etc/hotplug.d/default/00-wait_for_sysfs.hotplug
>>symlink still installed. Removing this will cut the messages to the
>>half but not solve the problem, sorry. We are working on it, but currently
>>have absolutely no idea what's going wrong here.
>
>
> Sorry for the confusion. It seems that the kernel emits two events for
> every device, which is wrong. It's not a second symlink as I pointed out
> to you first.
>
> Thanks,
> Kay
>
>
>
Just an update-039 fixes the majority of the vcs messages. I've rebooted
a few times and now only get 1-3 of the messages. Example:
Oct 15 21:46:28 [wait_for_sysfs] either wait_for_sysfs (udev 039) needs
an updat
e to handle the device '/class/vc/vcs8' properly (3) or the
sysfs-support of you
r device's driver needs to be fixed, please report to
<linux-hotplug-devel@lists
.sourceforge.net>
Oct 15 21:46:28 [wait_for_sysfs] either wait_for_sysfs (udev 039) needs
an updat
e to handle the device '/class/vc/vcsa8' properly (3) or the
sysfs-support of yo
ur device's driver needs to be fixed, please report to
<linux-hotplug-devel@list
s.sourceforge.net>
Oct 15 21:46:29 [wait_for_sysfs] either wait_for_sysfs (udev 039) needs
an updat
e to handle the device '/class/vc/vcs5' properly (3) or the
sysfs-support of you
r device's driver needs to be fixed, please report to
<linux-hotplug-devel@lists
.sourceforge.net>
Always (3)'s now, no (4)'s (not that I'm really sure what that signifies).
Thanks,
Jeff
--
"Experience is a good school but the fees are high." Heinrich Heine
-------------------------------------------------------
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 prev parent reply other threads:[~2004-10-16 2:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-14 23:21 wait_for_sysfs messages (more debugging info) Jeff
2004-10-15 2:53 ` Jesse Stockall
2004-10-16 2:00 ` Jeff [this message]
2004-10-16 2:40 ` Kay Sievers
2004-10-16 16:26 ` Kay Sievers
2004-10-16 18:48 ` Jeff
2004-10-17 0:45 ` Kay Sievers
2004-10-17 1:55 ` Jeff
2004-10-17 14:04 ` Jeff
2004-10-18 17:17 ` 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=417080CF.7010402@gwi.net \
--to=jtw@gwi.net \
--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).