* Re: wait_for_sysfs for USB key
2004-11-18 19:09 wait_for_sysfs for USB key Rob Kirkbride
@ 2004-11-18 20:00 ` Kay Sievers
2004-11-18 21:11 ` Rob Kirkbride
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Kay Sievers @ 2004-11-18 20:00 UTC (permalink / raw)
To: linux-hotplug
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: wait_for_sysfs for USB key
2004-11-18 19:09 wait_for_sysfs for USB key Rob Kirkbride
2004-11-18 20:00 ` Kay Sievers
@ 2004-11-18 21:11 ` Rob Kirkbride
2004-11-18 21:47 ` Kay Sievers
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Rob Kirkbride @ 2004-11-18 21:11 UTC (permalink / raw)
To: linux-hotplug
Kay Sievers wrote:
>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.
>
>
>
No the directory has got several entries which looked they were created
when I was plugging in the key. Interestingly the first time I plug the
key in it works, it's only after I've unmounted and then try and mount
it again, then the above message appears and all USB activity stops and
the haldaemon goes into an uninterruptable sleep and only a reboot seems
to cure it. Disabling the daemon gives me back the old behaviour of
mounting the key manually and continues to work no matter how many times
I plug/unplug. As you say with the haldaemon locking up I wonder if its
a kernel bug.
Rob
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: wait_for_sysfs for USB key
2004-11-18 19:09 wait_for_sysfs for USB key Rob Kirkbride
2004-11-18 20:00 ` Kay Sievers
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
4 siblings, 0 replies; 6+ messages in thread
From: Kay Sievers @ 2004-11-18 21:47 UTC (permalink / raw)
To: linux-hotplug
On Thu, 2004-11-18 at 21:11 +0000, Rob Kirkbride wrote:
> Kay Sievers wrote:
>
> >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.
> >
> No the directory has got several entries which looked they were created
> when I was plugging in the key.
Ok, than it's a different issue. We've got reports for an empty bus
directory which obviously leads to this kind of message.
> Interestingly the first time I plug the
> key in it works, it's only after I've unmounted and then try and mount
> it again, then the above message appears and all USB activity stops and
> the haldaemon goes into an uninterruptable sleep and only a reboot seems
> to cure it.
What happens if you use "eject" after the umount? Does this work.
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: wait_for_sysfs for USB key
2004-11-18 19:09 wait_for_sysfs for USB key Rob Kirkbride
` (2 preceding siblings ...)
2004-11-18 21:47 ` Kay Sievers
@ 2004-11-19 8:05 ` Rob Kirkbride
2004-11-19 17:24 ` David Zeuthen
4 siblings, 0 replies; 6+ messages in thread
From: Rob Kirkbride @ 2004-11-19 8:05 UTC (permalink / raw)
To: linux-hotplug
> On Thu, 2004-11-18 at 21:11 +0000, Rob Kirkbride wrote:
>> Kay Sievers wrote:
>>
>> >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.
>> >>
>> >>
>> >
>
>> Interestingly the first time I plug the
>> key in it works, it's only after I've unmounted and then try and mount
>> it again, then the above message appears and all USB activity stops and
>> the haldaemon goes into an uninterruptable sleep and only a reboot seems
>> to cure it.
>
> What happens if you use "eject" after the umount? Does this work.
>
Yes! That actually works better. The daemon doesn't hang and the message
is not produced. It doesn't always remount properly, but I can always
manually mount it myself whereas if I don't do the eject then I have to do
a reboot to continue using the USB bus.
What does this point to? I was going to trace the daemon to see if I can
find out why it's going into an uninterruptable sleep.
Rob
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: wait_for_sysfs for USB key
2004-11-18 19:09 wait_for_sysfs for USB key Rob Kirkbride
` (3 preceding siblings ...)
2004-11-19 8:05 ` Rob Kirkbride
@ 2004-11-19 17:24 ` David Zeuthen
4 siblings, 0 replies; 6+ messages in thread
From: David Zeuthen @ 2004-11-19 17:24 UTC (permalink / raw)
To: linux-hotplug
On Thu, 2004-11-18 at 21:11 +0000, Rob Kirkbride wrote:
> As you say with the haldaemon locking up I wonder if its
> a kernel bug.
>
This is most likely a kernel bug; you may look at this Red Hat bug
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id\x136255
which provides a minimal program to reproduce it.
Thanks,
David
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 6+ messages in thread