Re: udev 034 wait_for_sysfs message

[Greg KH <greg@kroah.com>]

Hm, this is really odd:

On Tue, Oct 12, 2004 at 06:45:12PM -0400, Todd Musall wrote:
> On Tue, 2004-10-12 at 14:59 -0700, Greg KH wrote:
> > On Tue, Oct 12, 2004 at 05:48:25PM -0400, Todd Musall wrote:
> > > On Tue, 2004-10-12 at 17:29 -0400, Todd Musall wrote:
> > > > On Tue, 2004-10-12 at 10:07 -0700, Greg KH wrote:
> > > > > On Mon, Oct 11, 2004 at 09:43:32PM -0400, Todd Musall wrote:
> > > > > > On Mon, 2004-10-11 at 15:37 -0700, Greg KH wrote:
> > > > > > > On Sun, Oct 10, 2004 at 05:10:50PM -0400, Todd Musall wrote:
> > > > > > > > wait_for_sysfs[21259]: error: wait_for_sysfs needs an update to handle
> > > > > > > > the device '/devices/pci0000:00/0000:00:14.2/usb5/5-4/5-4.2/5-4.2:1.0'
> > > > > > > > properly, please report to <linux-hotplug-devel@lists.sourceforge.net>
> > > > > > > 
> > > > > > > Can you send us the output of:
> > > > > > > 	ls -l /sys/devices/pci0000:00/0000:00:14.2/usb5/5-4/5-4.2/5-4.2:1.0
> > > > > > > 
> > > > > > > so we can see what needs to be fixed?
> > > > > > > 
> > > > > > 
> > > > > > [~]$ ls -l /sys/devices/pci0000:00/0000:00:14.2/usb5/5-4/5-4.2/5-4.2:1.0
> > > > > > total 0
> > > > > > -rw-r--r--  1 root root 4096 Oct 11 21:36 detach_state
> > > > > > drwxr-xr-x  3 root root    0 Oct 11 21:36 host6
> > > > > > drwxr-xr-x  2 root root    0 Oct 11 21:36 power

There are a lot of files missing here.

But yet, they show up here:

> > > > |-- 5-4.2
> > > > |   |-- 5-4.2:1.0
> > > > |   |   |-- bAlternateSetting
> > > > |   |   |-- bInterfaceClass
> > > > |   |   |-- bInterfaceNumber
> > > > |   |   |-- bInterfaceProtocol
> > > > |   |   |-- bInterfaceSubClass
> > > > |   |   |-- bNumEndpoints
> > > > |   |   |-- detach_state
> > > > |   |   |-- host7
> > > > |   |   |   |-- 7:0:0:0
> > > > |   |   |   |   |-- block -> ../../../../../../../../../block/sda
> > > > |   |   |   |   |-- delete
> > > > |   |   |   |   |-- detach_state
> > > > |   |   |   |   |-- device_blocked
> > > > |   |   |   |   |-- max_sectors
> > > > |   |   |   |   |-- model
> > > > |   |   |   |   |-- power
> > > > |   |   |   |   |   `-- state
> > > > |   |   |   |   |-- queue_depth
> > > > |   |   |   |   |-- rescan
> > > > |   |   |   |   |-- rev
> > > > |   |   |   |   |-- scsi_level
> > > > |   |   |   |   |-- state
> > > > |   |   |   |   |-- timeout
> > > > |   |   |   |   |-- type
> > > > |   |   |   |   `-- vendor
> > > > |   |   |   |-- detach_state
> > > > |   |   |   `-- power
> > > > |   |   |       `-- state
> > > > |   |   |-- iInterface
> > > > |   |   `-- power
> > > > |   |       `-- state
> > > > |   |-- bConfigurationValue
> > > > |   |-- bDeviceClass
> > > > |   |-- bDeviceProtocol
> > > > |   |-- bDeviceSubClass
> > > > |   |-- bMaxPower
> > > > |   |-- bNumConfigurations
> > > > |   |-- bNumInterfaces
> > > > |   |-- bcdDevice
> > > > |   |-- bmAttributes
> > > > |   |-- detach_state
> > > > |   |-- devnum
> > > > |   |-- idProduct
> > > > |   |-- idVendor
> > > > |   |-- manufacturer
> > > > |   |-- maxchild
> > > > |   |-- power
> > > > |   |   `-- state
> > > > |   |-- product
> > > > |   |-- serial
> > > > |   |-- speed
> > > > |   `-- version

And then:

> wait_for_sysfs[23395]: error: wait_for_sysfs needs an update to handle
> the device '/devices/pci0000:00/0000:00:14.2/usb5/5-4/5-4.2/5-4.2:1.0'
> properly (8), please report to <linux-hotplug-
> devel@lists.sourceforge.net>
> 
> The error message seems the same except for '... properly (8)'.  '(8)'
> isn't in 034.

The (8) shows us that the program was trying to look for a bus specific
file.  In this case, it should have found the bNumEndpoints file in that
directory, as that file sure looks like it is there.

Hm, I think I know what's happening.  Can you grab the udev-036 tarball
(I'm guessing you're using gentoo, right?  If so, it's in your
/usr/portage/distfiles directory.)

Take that tarball and uncompress it somewhere and go into the udev-036
directory it creates.  Then do the following:
	make spotless
	make USE_LOG=true DEBUG=true wait_for_sysfs

then copy the wait_for_sysfs program it creates to /sbin/wait_for_sysfs,
and yank out that device and plug it in again.  Could you then send us
the log messages that produces (it should be a lot of them.)

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