From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Thu, 28 Oct 2004 23:56:16 +0000 Subject: Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly Message-Id: <20041028235616.GA9562@vrfy.org> 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="utf-8" Content-Transfer-Encoding: 8bit To: linux-hotplug@vger.kernel.org On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote: > Idézés Kay Sievers : > > > 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... Fine! > 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 don't think so. Looks more like kernel config problem. > > 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 That's odd. It should look like that: 1-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.7/usb1/1-0:1.0 1-3 -> ../../../devices/pci0000:00/0000:00:1d.7/usb1/1-3 1-3:1.0 -> ../../../devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0 2-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-0:1.0 2-1 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1 2-1:1.0 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1:1.0 3-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.1/usb3/3-0:1.0 3-2 -> ../../../devices/pci0000:00/0000:00:1d.1/usb3/3-2 3-2:1.0 -> ../../../devices/pci0000:00/0000:00:1d.1/usb3/3-2/3-2:1.0 4-0:1.0 -> ../../../devices/pci0000:00/0000:00:1d.2/usb4/4-0:1.0 4-1 -> ../../../devices/pci0000:00/0000:00:1d.2/usb4/4-1 4-1:1.0 -> ../../../devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.0 4-1:1.1 -> ../../../devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.1 4-1:1.2 -> ../../../devices/pci0000:00/0000:00:1d.2/usb4/4-1/4-1:1.2 usb1 -> ../../../devices/pci0000:00/0000:00:1d.7/usb1 usb2 -> ../../../devices/pci0000:00/0000:00:1d.0/usb2 usb3 -> ../../../devices/pci0000:00/0000:00:1d.1/usb3 usb4 -> ../../../devices/pci0000:00/0000:00:1d.2/usb4 > > > > '/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? :) First the errors of "/sys/devices/*" and second the errors of "/sys/class/*" devices. Both classes of errors here are caused by the missing /sys/bus/usb/* entries. What usb chipset is that (lspci)? Which *_hcd driver (lsmod) is used? Kay ------------------------------------------------------- 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