Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly

[Csan <csani@lme.linux.hu>]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1252", Size: 7402 bytes --]

Idézés Kay Sievers <kay.sievers@vrfy.org>:

> On Thu, Oct 28, 2004 at 03:02:16AM +0200, Csan wrote:
> > This one is a USB bluetooth dongle (XüMicro, XBT-DG1 Class 2). It used to
> work
> > and hotplug with no problems up to some time ago. I don't know since when
> it
> > doesn't.
> 
> I don't think, that this is related to udev. Did yo try an older kernel?

Yes. Older kernels and the bluetooth dongle worked fine as much as I can recall.
Actually, I have to correct myself in that the problem seems to be gone after a
reboot now...
Since then the bluetooth dongle has been operational and fully functional.
However, I still get these messages in the syslog on insertion.
Here's the full relevant syslog exceprt:

Oct 28 03:51:49 csanote kernel: usb 3-1: new full speed USB device using address 2
Oct 28 03:51:54 csanote wait_for_sysfs[3967]: either wait_for_sysfs (udev 040)
needs an update to handle the device '/devices/pci0000:00/0000:00:1d.1/usb3/3-1'
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>
Oct 28 03:51:54 csanote wait_for_sysfs[3969]: either wait_for_sysfs (udev 040)
needs an update to handle the device
'/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-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>
Oct 28 03:51:54 csanote wait_for_sysfs[3971]: either wait_for_sysfs (udev 040)
needs an update to handle the device
'/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1' 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>
Oct 28 03:51:54 csanote wait_for_sysfs[3973]: either wait_for_sysfs (udev 040)
needs an update to handle the device
'/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.2' 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>
Oct 28 03:51:56 csanote usb.agent[3982]:      hci_usb: loaded successfully
Oct 28 03:51:56 csanote usb.agent[3986]:      hci_usb: already loaded
Oct 28 03:51:56 csanote usb.agent[4008]:      hci_usb: already loaded
Oct 28 03:51:56 csanote kernel: Bluetooth: HCI USB driver ver 2.7
Oct 28 03:51:56 csanote kernel: usbcore: registered new driver hci_usb
Oct 28 03:51:56 csanote hcid[3547]: HCI dev 0 registered
Oct 28 03:51:56 csanote hcid[3547]: HCI dev 0 up
Oct 28 03:51:56 csanote hcid[3547]: Starting security manager 0
Oct 28 03:52:01 csanote wait_for_sysfs[4078]: either wait_for_sysfs (udev 040)
needs an update to handle the device '/class/bluetooth/hci0' 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>

I tried digging back in the rotated syslogs to see if anything is saved that
could help and I found the following:

Oct 22 00:17:48 csanote hcid[3623]: Bluetooth HCI daemon
Oct 22 00:17:48 csanote ntpd[3620]: frequency initialized 27.767 PPM from
/var/lib/ntp/ntp.drift
Oct 22 00:17:48 csanote kernel: Bluetooth: Core ver 2.6
Oct 22 00:17:48 csanote kernel: NET: Registered protocol family 31
Oct 22 00:17:48 csanote kernel: Bluetooth: HCI device and connection manager
initialized
Oct 22 00:17:48 csanote kernel: Bluetooth: HCI socket layer initialized
Oct 22 00:17:48 csanote kernel: Bluetooth: L2CAP ver 2.3
Oct 22 00:17:48 csanote kernel: Bluetooth: L2CAP socket layer initialized
Oct 22 00:17:48 csanote sdpd[3632]: Bluetooth SDP daemon 
Oct 22 00:17:48 csanote kernel: Bluetooth: RFCOMM ver 1.3
Oct 22 00:17:48 csanote kernel: Bluetooth: RFCOMM socket layer initialized
Oct 22 00:17:48 csanote kernel: Bluetooth: RFCOMM TTY layer initialized
Oct 22 00:17:48 csanote udev: creating device node '/dev/rfcomm0'
Oct 22 00:17:48 csanote udev: creating device node '/dev/rfcomm1'

by the way, I checked what packages have been upgraded since the 22nd and among
others the udev itself was upgraded. Could that be related? I could give you a
list of the upgraded packages if you need it.

> > '/devices/pci0000:00/0000:00:1d.1/usb3/3-1' properly (no bus device
> > '/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0' properly (no bus
> device
> > '/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1' properly (no bus
> device
> > '/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.2' properly (no bus
> device
> 
> I don't have that errors here, but we've had several reports of that. I
> don't
> know why libsysfs is unable the determine the "bus" value. Could you please
> post the output of:
> 
>   ls -l /sys/bus/usb/devices

# ls -l /sys/bus/usb/devices
-r--r--r--  1 root root 0 2004-10-29 01:10 /sys/bus/usb/devices

And the relevant section from /sys/bus/usb/devices:
---- cut here ----

T:  Bus\x03 Lev\x01 Prnt\x01 Port\0 Cnt\x01 Dev#=  3 Spd\x12  MxCh= 0
D:  Ver= 1.10 Clsà(unk. ) Sub\x01 Prot\x01 MxPSd #Cfgs=  1
P:  Vendor
12 ProdID\001 Rev= 5.25
C:* #Ifs= 3 Cfg#= 1 AtrÀ MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 3 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E:  Ad(I) Atr\x03(Int.) MxPS=  16 Ivl=1ms
E:  Ad\x02(O) Atr\x02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad‚(I) Atr\x02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=   0 Ivl=1ms
E:  Adƒ(I) Atr\x01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=   9 Ivl=1ms
E:  Adƒ(I) Atr\x01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  17 Ivl=1ms
E:  Adƒ(I) Atr\x01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  25 Ivl=1ms
E:  Adƒ(I) Atr\x01(Isoc) MxPS=  25 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  33 Ivl=1ms
E:  Adƒ(I) Atr\x01(Isoc) MxPS=  33 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Clsà(unk. ) Sub\x01 Prot\x01 Driver=hci_usb
E:  Ad\x03(O) Atr\x01(Isoc) MxPS=  49 Ivl=1ms
E:  Adƒ(I) Atr\x01(Isoc) MxPS=  49 Ivl=1ms
I:  If#= 2 Alt= 0 #EPs= 0 Clsþ(app. ) Sub\x01 Prot\0 Driver=(none)

---- cut here ----

> > '/class/bluetooth/hci0' properly (no bus
> 
> Hmm, I know nothing about bluetooth, but the one built-in into my notebook
> does not create these errors on activation. It is also the missing bus-link
> and therefore seems to be related to the other errors.

Which "other errors" are you refering to? :)

Thanks.

Regs,
Csan  alias  János Holányi
Debian Group leader - Association of Hungarian Linux Users
URL: http://www.lme.hu/  Email: csani AT lme.linux.hu
gpg --keyserver hkp://pgp.mit.edu --recv-keys 82CBB661



-------------------------------------------------------
This Newsletter Sponsored by: Macrovision 
For reliable Linux application installations, use the industry's leading
setup authoring tool, InstallShield X. Learn more and evaluate 
today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/
_______________________________________________
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