From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: FastTrak SX4 sata_sx4 problems
Date: Tue, 08 Mar 2005 00:04:27 +0000 [thread overview]
Message-ID: <1110240267.4669.10.camel@localhost.localdomain> (raw)
In-Reply-To: <422C3640.5090507@managerzone.com>
On Mon, 2005-03-07 at 12:08 +0100, Mattias Nilsson wrote:
> Hi
>
> I am trying to get a FastTrak SX4 running on my server.
> The machine detects the PCI device ok (pci-id 105a:6622), but when
> I try to load the sata_sx4 driver, the insmod command hangs for a
> very long time, and I get errors in /var/log/messages as per below.
>
> The card has been running fine in Windows before we reinstalled it with Linux.
> Currently we are running kernel 2.6.9-1.667smp
> Mar 7 11:56:12 grand wait_for_sysfs[2676]: either wait_for_sysfs (udev 039) needs an update to handle the device '/devices/pci0000:00/0000:00:1e.0/0000:02:03.0/host2/2:0:0: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 failure does not seems to be hotplug or udev related. To get rid of
the udev error messages, you may install the available udev update, but
this will not change the behavior of your driver.
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://ads.osdn.com/?ad_ide95&alloc_id\x14396&op=click
_______________________________________________
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
prev parent reply other threads:[~2005-03-08 0:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 11:08 FastTrak SX4 sata_sx4 problems Mattias Nilsson
2005-03-08 0:04 ` Kay Sievers [this message]
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=1110240267.4669.10.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).