From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: timeout in wait_for_sysfs
Date: Mon, 22 Nov 2004 15:15:56 +0000 [thread overview]
Message-ID: <1101136556.7195.84.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.44.0411212321580.22258-100000@kurage.nimh.nih.gov>
On Mon, 2004-11-22 at 07:35 -0500, Tom Holroyd wrote:
> On Mon, 22 Nov 2004, Kay Sievers wrote:
>
> > On Sun, 2004-11-21 at 23:22 -0500, Tom Holroyd wrote:
> > > 2.6.9-1.678_FC3, yum-updated as of 11/20, including new udev and kernel.
> > > Nov 21 23:10:08 kaiba wait_for_sysfs[3967]: either wait_for_sysfs (udev 039) needs an update to handle the device '/block/sda' 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>
> >
> > Other users reported the same problem here. You may try:
> > eject <device>
> >
> > before you unplug the device.
>
> OK, I su'ed (eject didn't work otherwise), and said
> 'eject /media/NO_NAME' -- it unmounted, and I unplugged it,
> then plugged it back in.
>
> Same error as before.
You may try "eject /dev/sda". Some people reported that this was
working.
> > Do you have anything running which has files opened on the device,
> > something like fam?
>
> No; it doesn't let me unmount it if I do.
>
> I found that if I rmmod the usb_storage, and scsi modules, then
> it does NOT give me the error when I plug it in the second time.
> It didn't automount right away, though. I think the disk-mounter
> panel applet mounted it about 10 seconds later...
>
> Yeah, all I need to remove is usb_storage, and when I plug it in
> again it's fine. Automounts OK too if the scsi modules are still
> in there.
Yes, seems like a kernel bug. There is currently no fix for it. You may
look here:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x136255
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
prev parent reply other threads:[~2004-11-22 15:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 4:22 timeout in wait_for_sysfs Tom Holroyd
2004-11-22 6:10 ` Kay Sievers
2004-11-22 12:35 ` Tom Holroyd
2004-11-22 15:15 ` 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=1101136556.7195.84.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).