From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Thu, 07 Oct 2004 19:15:21 +0000 Subject: Re: wait_for_sysfs errors Message-Id: <20041007191521.GA22090@kroah.com> List-Id: References: <20041007015347.7fc6588c@Luna.local> In-Reply-To: <20041007015347.7fc6588c@Luna.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-hotplug@vger.kernel.org On Thu, Oct 07, 2004 at 02:57:19PM -0400, Jeff wrote: > On Thu, 7 Oct 2004 10:47:15 -0700 > Greg KH wrote: > > > On Thu, Oct 07, 2004 at 01:53:47AM -0400, Jeff wrote: > > > You asked for it: > > > > Thanks for the info, I'll be adding these devices to the wait_for_sysfs > > program, so it doesn't spit out these messages for you anymore. > > > > greg k-h > > > > Thank you GKH. After reading some posts on the list I'm assuming this > is for tweaking udev to avoid some of the timing issues that have been > known to happen (well I know I've had a few but only a sporadic i2c > device on an older 2.6.5 kernel of late)? Just curious... Yes, the wait_for_sysfs program, puts all of the logic for how and what we need to wait for when a device is added to sysfs. I fixed up the i2c devices, but I'm having a problem with the vcs devices, sometimes it works for me, and other times it doesn't. Oh well, back to debugging... thanks, greg k-h ------------------------------------------------------- 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