Re: wait_for_sysfs messages (more debugging info)

[Jeff <jtw@gwi.net>]

Kay Sievers wrote:
> On Sat, Oct 16, 2004 at 04:40:51AM +0200, Kay Sievers wrote:
> 
>>On Fri, Oct 15, 2004 at 10:00:47PM -0400, Jeff wrote:
>>
>>>Kay Sievers wrote:
>>>
>>>>On Fri, 2004-10-15 at 01:42 +0200, Kay Sievers wrote:
>>>>
>>>>
>>>>>On Thu, Oct 14, 2004 at 07:21:18PM -0400, Jeff wrote:
>>>>>
>>>>>
>>>>>>Sorry to double post but thought with the more verbose debugging this 
>>>>>>might help you more:
>>>>>>Oct 14 16:04:00 [wait_for_sysfs] either wait_for_sysfs (udev 038) needs 
>>>>>>an update
>>>>>>to handle the device '/class/vc/vcs2' properly (4) or the sysfs-support 
>>>>>>of your de
>>>>>>vice's driver needs to be fixed, please report to 
>>>>>><linux-hotplug-devel@lists.sourc
>>>>>>eforge.net>
>>>>>
>>>>>Seems like you have the /etc/hotplug.d/default/00-wait_for_sysfs.hotplug
>>>>>symlink still installed. Removing this will cut the messages to the
>>>>>half but not solve the problem, sorry. We are working on it, but currently
>>>>>have absolutely no idea what's going wrong here.
>>>>
>>>>
>>>>Sorry for the confusion. It seems that the kernel emits two events for
>>>>every device, which is wrong. It's not a second symlink as I pointed out
>>>>to you first.
>>>>
>>>>Thanks,
>>>>Kay
>>>>
>>>>
>>>>
>>>
>>>Just an update-039 fixes the majority of the vcs messages. I've rebooted 
>>>a few times and now only get 1-3 of the messages. Example:
>>>
>>>Oct 15 21:46:28 [wait_for_sysfs] either wait_for_sysfs (udev 039) needs 
>>>an updat
>>>e to handle the device '/class/vc/vcs8' properly (3) or the 
>>>sysfs-support of you
>>>r device's driver needs to be fixed, please report to 
>>><linux-hotplug-devel@lists
>>>.sourceforge.net>
>>>
>>>Always (3)'s now, no (4)'s (not that I'm really sure what that signifies).
>>
>>Ok, we need to cover the case, we can open the device but can't read
>>anything, cause it's gone in the meantime.
>>
>>Here is a fix and it replaces the magic numbers with meaningful text.
> 
> 
> Here is a better version. We return successful in the case, that the
> advertised device does not appear within the timeout or goes completely
> away while waiting for the attributes. All magic numbers should be
> readable as a string now.
> 
> This hopefully fixes the last vc errors.
> 
> Thanks,
> Kay

K, first patch produced a couple of device unavailables & a slew of no 
device symlinks. Second patch-no messages at all :)

Thank god, if I have to reboot again I'm going to puke.

Thanks,

Jeff

-- 
"Experience is a good school but the fees are high." Heinrich Heine


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
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