From mboxrd@z Thu Jan 1 00:00:00 1970 From: Csan Date: Thu, 28 Oct 2004 23:41:32 +0000 Subject: Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly Message-Id: <1099006892.418183acdf77e@mail.utca.hu> List-Id: References: <1098925336.41804518e7430@mail.utca.hu> In-Reply-To: <1098925336.41804518e7430@mail.utca.hu> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org Id=E9z=E9s Kay Sievers : > On Thu, Oct 28, 2004 at 03:02:16AM +0200, Csan wrote: > > This one is a USB bluetooth dongle (X=C3=BCMicro, XBT-DG1 Class 2). It = used to > work > > and hotplug with no problems up to some time ago. I don't know since wh= en > it > > doesn't. >=20 > 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 re= call. Actually, I have to correct myself in that the problem seems to be gone aft= er 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 ad= dress 2 Oct 28 03:51:54 csanote wait_for_sysfs[3967]: either wait_for_sysfs (udev 0= 40) 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 Oct 28 03:51:54 csanote wait_for_sysfs[3969]: either wait_for_sysfs (udev 0= 40) 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 Oct 28 03:51:54 csanote wait_for_sysfs[3971]: either wait_for_sysfs (udev 0= 40) 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 Oct 28 03:51:54 csanote wait_for_sysfs[3973]: either wait_for_sysfs (udev 0= 40) 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 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 0= 40) needs an update to handle the device '/class/bluetooth/hci0' properly (no b= us device link) or the sysfs-support of your device's driver needs to be fixed, please report to 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=20 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 a= mong others the udev itself was upgraded. Could that be related? I could give yo= u 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 >=20 > 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 plea= se > post the output of: >=20 > 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=03 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=3D 3 Spd=12 MxCh=3D 0 D: Ver=3D 1.10 Cls=E0(unk. ) Sub=01 Prot=01 MxPSd #Cfgs=3D 1 P: Vendor 12 ProdID=0001 Rev=3D 5.25 C:* #Ifs=3D 3 Cfg#=3D 1 Atr=C0 MxPwr=3D 0mA I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=E0(unk. ) Sub=01 Prot=01 Driver=3Dhci_u= sb E: Ad=81(I) Atr=03(Int.) MxPS=3D 16 Ivl=3D1ms E: Ad=02(O) Atr=02(Bulk) MxPS=3D 64 Ivl=3D0ms E: Ad=82(I) Atr=02(Bulk) MxPS=3D 64 Ivl=3D0ms I: If#=3D 1 Alt=3D 0 #EPs=3D 2 Cls=E0(unk. ) Sub=01 Prot=01 Driver=3Dhci_u= sb E: Ad=03(O) Atr=01(Isoc) MxPS=3D 0 Ivl=3D1ms E: Ad=83(I) Atr=01(Isoc) MxPS=3D 0 Ivl=3D1ms I: If#=3D 1 Alt=3D 1 #EPs=3D 2 Cls=E0(unk. ) Sub=01 Prot=01 Driver=3Dhci_u= sb E: Ad=03(O) Atr=01(Isoc) MxPS=3D 9 Ivl=3D1ms E: Ad=83(I) Atr=01(Isoc) MxPS=3D 9 Ivl=3D1ms I: If#=3D 1 Alt=3D 2 #EPs=3D 2 Cls=E0(unk. ) Sub=01 Prot=01 Driver=3Dhci_u= sb E: Ad=03(O) Atr=01(Isoc) MxPS=3D 17 Ivl=3D1ms E: Ad=83(I) Atr=01(Isoc) MxPS=3D 17 Ivl=3D1ms I: If#=3D 1 Alt=3D 3 #EPs=3D 2 Cls=E0(unk. ) Sub=01 Prot=01 Driver=3Dhci_u= sb E: Ad=03(O) Atr=01(Isoc) MxPS=3D 25 Ivl=3D1ms E: Ad=83(I) Atr=01(Isoc) MxPS=3D 25 Ivl=3D1ms I: If#=3D 1 Alt=3D 4 #EPs=3D 2 Cls=E0(unk. ) Sub=01 Prot=01 Driver=3Dhci_u= sb E: Ad=03(O) Atr=01(Isoc) MxPS=3D 33 Ivl=3D1ms E: Ad=83(I) Atr=01(Isoc) MxPS=3D 33 Ivl=3D1ms I: If#=3D 1 Alt=3D 5 #EPs=3D 2 Cls=E0(unk. ) Sub=01 Prot=01 Driver=3Dhci_u= sb E: Ad=03(O) Atr=01(Isoc) MxPS=3D 49 Ivl=3D1ms E: Ad=83(I) Atr=01(Isoc) MxPS=3D 49 Ivl=3D1ms I: If#=3D 2 Alt=3D 0 #EPs=3D 0 Cls=FE(app. ) Sub=01 Prot=00 Driver=3D(none) ---- cut here ---- > > '/class/bluetooth/hci0' properly (no bus >=20 > 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-li= nk > and therefore seems to be related to the other errors. Which "other errors" are you refering to? :) Thanks. Regs, Csan alias J=E1nos Hol=E1nyi 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=20 For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate=20 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