From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: wait_for_sysfs() "class specific file unavailable" messages
Date: Thu, 02 Dec 2004 18:47:38 +0000 [thread overview]
Message-ID: <1102013259.6127.9.camel@localhost.localdomain> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C12E808@xbl3.ma.emulex.com>
On Thu, 2004-12-02 at 11:04 -0500, James.Smart@Emulex.Com wrote:
> In testing our FC adapters with the latest kernel, we are seeing the following wait_for_sysfs() messages from udev:
>
> Dec 1 10:03:20 xeon1 wait_for_sysfs[13843]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/fc_host/host35' properly (class specific file unavailable) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
> Dec 1 10:03:20 xeon1 wait_for_sysfs[13846]: either wait_for_sysfs (udev 039) needs an update to handle the device '/class/fc_transport/target35:0:0' properly (class specific file unavailable) or the sysfs-support of your device's driver needs to be fixed, please report to <linux-hotplug-devel@lists.sourceforge.net>
>
> In looking through the 046 udev sources - I think it implies that udev doesn't recognize the fc_transport or fc_host classes. I know fc_host is new. Additionally, there are some other transports being added to scsi that are not accounted for as well - spi_transport and spi_host (and fc_remote_ports is pending).
>
> I assume this is solved by adding the following lines to udev_sysfs.c:
> { .subsystem = "fc_transport", .file = NULL },
> { .subsystem = "fc_host", .file = NULL },
{ .subsystem = "fc_transport",»·.file = "port_id" }
is already in my tree and will be show up soon with the next sync.
What does "ls -l /class/fc_host/host35" print? We may wait for a
specific file, if there is one.
Thanks,
Kay
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
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-12-02 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-02 16:04 wait_for_sysfs() "class specific file unavailable" messages for /class/fc_host and /class/fc_transpo James.Smart
2004-12-02 18:47 ` Kay Sievers [this message]
2004-12-02 22:20 ` wait_for_sysfs() "class specific file unavailable" messages for /class/fc_host and /class/fc_tra Greg KH
2004-12-10 15:05 ` wait_for_sysfs() "class specific file unavailable" messagesfor /class/fc_host and /class/fc_tran James.Smart
2004-12-10 21:05 ` wait_for_sysfs() "class specific file unavailable" messagesfor Kay Sievers
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=1102013259.6127.9.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.