From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs for USB key
Date: Thu, 18 Nov 2004 20:00:00 +0000 [thread overview]
Message-ID: <1100808000.7238.69.camel@localhost.localdomain> (raw)
In-Reply-To: <419CF351.2050608@rkcomputing.co.uk>
On Thu, 2004-11-18 at 19:09 +0000, Rob Kirkbride wrote:
> When I plug in my USB key I get the following :-
>
> wait_for_sysfs[8695]: either wait_for_sysfs (udev 039) needs an update
> to handle the device
> '/devices/pci0000:00/0000:00:10.0/0000:02:00.0/usb1/1-2/1-2.1/1-2.1.1/1-2.1.1:1.0'
> properly (no bus device link) or the
> sysfs-support of your device's driver needs to be fixed, please report
> to <linux-hotplug-devel@lists.sourceforge.net>
>
> This is with Fedora Core 3, patched with the 678_FC3 kernel,
> hotplug-2004_04_01-8.
>
> Can I configure something to stop it, or does this need adding to some
> sort of config?
No, unfortunately not with an unmodified package. Some people
reported this and is seems like a kernel bug. Can you confirm,
that /sys/bus/usb/devices/* is empty? This is probably causing
the failure.
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8
_______________________________________________
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-11-18 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 19:09 wait_for_sysfs for USB key Rob Kirkbride
2004-11-18 20:00 ` Kay Sievers [this message]
2004-11-18 21:11 ` Rob Kirkbride
2004-11-18 21:47 ` Kay Sievers
2004-11-19 8:05 ` Rob Kirkbride
2004-11-19 17:24 ` David Zeuthen
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=1100808000.7238.69.camel@localhost.localdomain \
--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).