* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
@ 2004-10-28 21:31 ` Kay Sievers
2004-10-28 23:41 ` Csan
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Kay Sievers @ 2004-10-28 21:31 UTC (permalink / raw)
To: linux-hotplug
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?
> '/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
> '/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.
Thanks,
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
2004-10-28 21:31 ` Kay Sievers
@ 2004-10-28 23:41 ` Csan
2004-10-28 23:56 ` Kay Sievers
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Csan @ 2004-10-28 23:41 UTC (permalink / raw)
To: linux-hotplug
[-- 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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
2004-10-28 21:31 ` Kay Sievers
2004-10-28 23:41 ` Csan
@ 2004-10-28 23:56 ` Kay Sievers
2004-10-29 1:37 ` Csan
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Kay Sievers @ 2004-10-28 23:56 UTC (permalink / raw)
To: linux-hotplug
On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote:
> 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...
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
` (2 preceding siblings ...)
2004-10-28 23:56 ` Kay Sievers
@ 2004-10-29 1:37 ` Csan
2004-10-30 3:23 ` Kay Sievers
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Csan @ 2004-10-29 1:37 UTC (permalink / raw)
To: linux-hotplug
Idézés Kay Sievers <kay.sievers@vrfy.org>:
> On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote:
> 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
...
> 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)?
# lspci
0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM
Controller/Host-Hub Interface (rev 03)
0000:00:01.0 PCI bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP
Bridge (rev 03)
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
USB UHCI Controller #3 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI
Controller (rev 02)
0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82)
0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 02)
0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100
IDE Controller (rev 02)
0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus
Controller (rev 02)
0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM
(ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
0000:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem
Controller (rev 02)
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
[Radeon Mobility 9000 M9] (rev 01)
0000:02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
Controller (rev 80)
0000:02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
0000:02:04.0 CardBus bridge: O2 Micro, Inc. OZ6912 Cardbus Controller
> Which *_hcd driver (lsmod) is used?
# lsmod | grep hci | grep -v 1394
hci_usb 13888 3
bluetooth 49604 7 hci_usb,rfcomm,l2cap
uhci_hcd 33136 0
ehci_hcd 32004 0
usbcore 119012 9
cdc_acm,hci_usb,usbhid,uhci_hcd,ehci_hcd,usbmouse,usbkbd
# dmesg | grep hcd
ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
ehci_hcd 0000:00:1d.7: irq 201, pci mem e0a5b000
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB (ICH4) USB UHCI #1
uhci_hcd 0000:00:1d.0: irq 177, io base 00001800
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB (ICH4) USB UHCI #2
uhci_hcd 0000:00:1d.1: irq 185, io base 00001820
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB (ICH4) USB UHCI #3
uhci_hcd 0000:00:1d.2: irq 193, io base 00001840
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
BR,
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
` (3 preceding siblings ...)
2004-10-29 1:37 ` Csan
@ 2004-10-30 3:23 ` Kay Sievers
2004-10-30 16:00 ` Greg KH
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Kay Sievers @ 2004-10-30 3:23 UTC (permalink / raw)
To: linux-hotplug
On Fri, Oct 29, 2004 at 03:37:28AM +0200, Csan wrote:
> Idézés Kay Sievers <kay.sievers@vrfy.org>:
> > On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote:
>
>
> > 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
Greg, any idea how it can happen, that the usb subsys does not create any
/sys/bus/usb/* entry at all?
Thanks,
Kay
> > What usb chipset is that (lspci)?
>
> # lspci
> 0000:00:00.0 Host bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE DRAM
> Controller/Host-Hub Interface (rev 03)
> 0000:00:01.0 PCI bridge: Intel Corp. 82845G/GL[Brookdale-G]/GE/PE Host-to-AGP
> Bridge (rev 03)
> 0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #1 (rev 02)
> 0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #2 (rev 02)
> 0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M)
> USB UHCI Controller #3 (rev 02)
> 0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI
> Controller (rev 02)
> 0000:00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 82)
> 0000:00:1f.0 ISA bridge: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) LPC Bridge (rev 02)
> 0000:00:1f.1 IDE interface: Intel Corp. 82801DB/DBL (ICH4/ICH4-L) UltraATA-100
> IDE Controller (rev 02)
> 0000:00:1f.3 SMBus: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) SMBus
> Controller (rev 02)
> 0000:00:1f.5 Multimedia audio controller: Intel Corp. 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 02)
> 0000:00:1f.6 Modem: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Modem
> Controller (rev 02)
> 0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf
> [Radeon Mobility 9000 M9] (rev 01)
> 0000:02:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host
> Controller (rev 80)
> 0000:02:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
> 0000:02:04.0 CardBus bridge: O2 Micro, Inc. OZ6912 Cardbus Controller
>
>
> > Which *_hcd driver (lsmod) is used?
>
> # lsmod | grep hci | grep -v 1394
> hci_usb 13888 3
> bluetooth 49604 7 hci_usb,rfcomm,l2cap
> uhci_hcd 33136 0
> ehci_hcd 32004 0
> usbcore 119012 9
> cdc_acm,hci_usb,usbhid,uhci_hcd,ehci_hcd,usbmouse,usbkbd
>
> # dmesg | grep hcd
> ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
> ehci_hcd 0000:00:1d.7: irq 201, pci mem e0a5b000
> ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
> ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
> uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB (ICH4) USB UHCI #1
> uhci_hcd 0000:00:1d.0: irq 177, io base 00001800
> uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
> uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB (ICH4) USB UHCI #2
> uhci_hcd 0000:00:1d.1: irq 185, io base 00001820
> uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
> uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB (ICH4) USB UHCI #3
> uhci_hcd 0000:00:1d.2: irq 193, io base 00001840
> uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&opÃk
_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
` (4 preceding siblings ...)
2004-10-30 3:23 ` Kay Sievers
@ 2004-10-30 16:00 ` Greg KH
2004-10-31 0:35 ` Kay Sievers
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Greg KH @ 2004-10-30 16:00 UTC (permalink / raw)
To: linux-hotplug
On Sat, Oct 30, 2004 at 05:23:41AM +0200, Kay Sievers wrote:
> On Fri, Oct 29, 2004 at 03:37:28AM +0200, Csan wrote:
> > Id??z??s Kay Sievers <kay.sievers@vrfy.org>:
> > > On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote:
> >
> >
> > > 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
>
> Greg, any idea how it can happen, that the usb subsys does not create any
> /sys/bus/usb/* entry at all?
Ick, no, I don't know how that could happen :(
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
` (5 preceding siblings ...)
2004-10-30 16:00 ` Greg KH
@ 2004-10-31 0:35 ` Kay Sievers
2004-11-06 7:51 ` Csan
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Kay Sievers @ 2004-10-31 0:35 UTC (permalink / raw)
To: linux-hotplug
On Sat, Oct 30, 2004 at 09:00:37AM -0700, Greg KH wrote:
> On Sat, Oct 30, 2004 at 05:23:41AM +0200, Kay Sievers wrote:
> > On Fri, Oct 29, 2004 at 03:37:28AM +0200, Csan wrote:
> > > Id??z??s Kay Sievers <kay.sievers@vrfy.org>:
> > > > On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote:
> > >
> > >
> > > > 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
> >
> > Greg, any idea how it can happen, that the usb subsys does not create any
> > /sys/bus/usb/* entry at all?
>
> Ick, no, I don't know how that could happen :(
So let's see if we come closer. :)
Hi Csan,
what kernel is that? Did you apply any patches to it? Any chance to try
a different version? Which distribution?
Does reloading the driver:
rmmod ehci_hcd uhci_hcd
modprobe uhci_hcd
create anything in /sys/bus/usb/devices/*?
Thanks,
Kay
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
` (6 preceding siblings ...)
2004-10-31 0:35 ` Kay Sievers
@ 2004-11-06 7:51 ` Csan
2004-11-06 17:08 ` Greg KH
2004-11-06 18:02 ` Fwd: Re: wait_for_sysfs needs an update to handle the device Kay Sievers
9 siblings, 0 replies; 11+ messages in thread
From: Csan @ 2004-11-06 7:51 UTC (permalink / raw)
To: linux-hotplug
Idézés Kay Sievers <kay.sievers@vrfy.org>:
> On Sat, Oct 30, 2004 at 09:00:37AM -0700, Greg KH wrote:
> > On Sat, Oct 30, 2004 at 05:23:41AM +0200, Kay Sievers wrote:
> > > On Fri, Oct 29, 2004 at 03:37:28AM +0200, Csan wrote:
> > > > Id??z??s Kay Sievers <kay.sievers@vrfy.org>:
> > > > > On Fri, Oct 29, 2004 at 01:41:32AM +0200, Csan wrote:
> > > >
> > > >
> > > > > 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
> > >
> > > Greg, any idea how it can happen, that the usb subsys does not create
> any
> > > /sys/bus/usb/* entry at all?
> >
> > Ick, no, I don't know how that could happen :(
>
> So let's see if we come closer. :)
>
> Hi Csan,
Hi,
> what kernel is that?
That was the stock Debian kernel 2.6.8-1-686
> Did you apply any patches to it?
No patches.
> Any chance to try
> a different version?
Yes. The reason I've waited a few days before I reply to this has been that
2.6.9 hit the unstable repository and now I am running 2.6.9... and no
improvement around here:
# ls -l /sys/bus/usb/devices
-r--r--r-- 1 root root 0 2004-11-06 07:05 /sys/bus/usb/devices
> Which distribution?
Debian, Debian, Debian... what else? - Check my sig ;)
> Does reloading the driver:
> rmmod ehci_hcd uhci_hcd
> modprobe uhci_hcd
>
> create anything in /sys/bus/usb/devices/*?
Still nothing:
# ls -l /sys/bus/usb/devices
-r--r--r-- 1 root root 0 2004-11-06 08:17 /sys/bus/usb/devices
Strangely enough, on a few other machines that I run 2.6, the subdir is properly
present:
# ls -l /sys/bus/usb/devices/
lrwxrwxrwx 1 root root 53 2004-09-27 20:26 1-0:1.0 ->
../../../devices/pci0000:00/0000:00:01.2/usb1/1-0:1.0
lrwxrwxrwx 1 root root 45 2004-09-27 20:26 usb1 ->
../../../devices/pci0000:00/0000:00:01.2/usb1
# uname -r
2.6.2-1-586tsc
# ls -l /sys/bus/usb/devices/
lrwxrwxrwx 1 root root 0 Nov 2 06:07 1-0:1.0 ->
../../../devices/pci0000:00/0000:00:07.2/usb1/1-0:1.0
lrwxrwxrwx 1 root root 0 Nov 2 06:07 2-0:1.0 ->
../../../devices/pci0000:00/0000:00:07.3/usb2/2-0:1.0
lrwxrwxrwx 1 root root 0 Nov 2 06:07 usb1 ->
../../../devices/pci0000:00/0000:00:07.2/usb1
lrwxrwxrwx 1 root root 0 Nov 2 06:07 usb2 ->
../../../devices/pci0000:00/0000:00:07.3/usb2
# uname -r
2.6.8-1-686-smp
So the problem might seem to be of local origin, but then what would that be?
I'm gonna try some older kernels (2.6.7) on this laptop... brb.
...and no, no change:
# ls -l /sys/bus/usb/devices
-r--r--r-- 1 root root 0 2004-11-06 08:48 /sys/bus/usb/devices
# uname -r
2.6.7-1-686
Regards,
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 SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device properly
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
` (7 preceding siblings ...)
2004-11-06 7:51 ` Csan
@ 2004-11-06 17:08 ` Greg KH
2004-11-06 18:02 ` Fwd: Re: wait_for_sysfs needs an update to handle the device Kay Sievers
9 siblings, 0 replies; 11+ messages in thread
From: Greg KH @ 2004-11-06 17:08 UTC (permalink / raw)
To: linux-hotplug
On Sat, Nov 06, 2004 at 08:51:26AM +0100, Csan wrote:
> Yes. The reason I've waited a few days before I reply to this has been that
> 2.6.9 hit the unstable repository and now I am running 2.6.9... and no
> improvement around here:
>
> # ls -l /sys/bus/usb/devices
> -r--r--r-- 1 root root 0 2004-11-06 07:05 /sys/bus/usb/devices
Are you sure you actually _have_ a usb controller on this machine? It
sure doesn't look like it.
thanks,
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread* Re: Fwd: Re: wait_for_sysfs needs an update to handle the device
2004-10-28 1:02 Fwd: Re: wait_for_sysfs needs an update to handle the device properly Csan
` (8 preceding siblings ...)
2004-11-06 17:08 ` Greg KH
@ 2004-11-06 18:02 ` Kay Sievers
9 siblings, 0 replies; 11+ messages in thread
From: Kay Sievers @ 2004-11-06 18:02 UTC (permalink / raw)
To: linux-hotplug
On Sat, 2004-11-06 at 09:08 -0800, Greg KH wrote:
> On Sat, Nov 06, 2004 at 08:51:26AM +0100, Csan wrote:
> > Yes. The reason I've waited a few days before I reply to this has been that
> > 2.6.9 hit the unstable repository and now I am running 2.6.9... and no
> > improvement around here:
> >
> > # ls -l /sys/bus/usb/devices
> > -r--r--r-- 1 root root 0 2004-11-06 07:05 /sys/bus/usb/devices
>
> Are you sure you actually _have_ a usb controller on this machine? It
> sure doesn't look like it.
Looks like a "normal" Intel controller. In earlier mails Csan posted
this:
# lspci
0000:00:1d.0 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 (rev 02)
0000:00:1d.1 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 (rev 02)
0000:00:1d.2 USB Controller: Intel Corp. 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 (rev 02)
0000:00:1d.7 USB Controller: Intel Corp. 82801DB/DBM (ICH4/ICH4-M) USB 2.0 EHCI Controller (rev 02)
# dmesg | grep hcd
ehci_hcd 0000:00:1d.7: Intel Corp. 82801DB (ICH4) USB2 EHCI Controller
ehci_hcd 0000:00:1d.7: irq 201, pci mem e0a5b000
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: USB 2.0 enabled, EHCI 1.00, driver 2004-May-10
uhci_hcd 0000:00:1d.0: Intel Corp. 82801DB (ICH4) USB UHCI #1
uhci_hcd 0000:00:1d.0: irq 177, io base 00001800
uhci_hcd 0000:00:1d.0: new USB bus registered, assigned bus number 2
uhci_hcd 0000:00:1d.1: Intel Corp. 82801DB (ICH4) USB UHCI #2
uhci_hcd 0000:00:1d.1: irq 185, io base 00001820
uhci_hcd 0000:00:1d.1: new USB bus registered, assigned bus number 3
uhci_hcd 0000:00:1d.2: Intel Corp. 82801DB (ICH4) USB UHCI #3
uhci_hcd 0000:00:1d.2: irq 193, io base 00001840
uhci_hcd 0000:00:1d.2: new USB bus registered, assigned bus number 4
# /sys/bus/usb/devices:
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)
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_idU88&alloc_id\x12065&op=click
_______________________________________________
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
^ permalink raw reply [flat|nested] 11+ messages in thread