On Monday 05 January 2004 16:31, Simone Gotti wrote: Hi, Listening the various discussion of Marcel Holtmann on the usb-devel mailinglist about usbfs problems, I've decided to umount it before plugging my usb device and then it worked without any problem.
So, the reason that it worked when I plugged it before the init script start was that in that moment the usbfs wasn't mounted. So the usbfs issue is true. Someone think that I have to send this email to the usb-devel too? > Hi, > I don't know if this is the right place for this problem because I don't > know if it's a bluez or a usb problem. > > I'm using the last kernel 2.6.1-rc1 patch with patch-2.6.0-mh1 but this > happens with 2.6.0, 2.6.0-mm1, 2.6.0-mm2, 2.6.1-rc1-mm1 and with the 2.4.22 > and 2.4.23 kernels. > > I've got a DIGICOM PALLADIO bluetooth USB adapter with a CSR chipset: > > When I start my system with this device already plugged it works well with > NO problems but when I plug it after the init scripts I've got a lot of > this errors from dmesg: > > Jan 3 13:47:44 localhost hub 2-0:1.0: new USB device on port 2, assigned > address 2 > Jan 3 13:47:45 localhost Bluetooth: HCI USB driver ver 2.4 > Jan 3 13:47:45 localhost hci_usb: probe of 2-2:1.2 failed with error -5 > Jan 3 13:47:45 localhost drivers/usb/core/usb.c: registered new driver > hci_usb > Jan 3 13:47:45 localhost hcid[4695]: HCI dev 0 registered > Jan 3 13:47:45 localhost hci_usb_isoc_rx_submit: hci0 isoc rx submit > failed urb ccbbfc14 err -22 > Jan 3 13:47:45 localhost hci_usb_isoc_rx_submit: hci0 isoc rx submit > failed urb ccbbfc14 err -22 > Jan 3 13:47:45 localhost usb 2-2: control timeout on ep0in > Jan 3 13:47:45 localhost usbfs: USBDEVFS_CONTROL failed cmd usbmodules dev > 2 rqt 128 rq 6 len 18 ret -110 > Jan 3 13:47:45 localhost usb 2-2: control timeout on ep0in > Jan 3 13:47:45 localhost usbfs: USBDEVFS_CONTROL failed cmd usbmodules dev > 2 rqt 128 rq 6 len 18 ret -110 > Jan 3 13:47:45 localhost usb 2-2: control timeout on ep0in > Jan 3 13:47:45 localhost usbfs: USBDEVFS_CONTROL failed cmd usbmodules dev > 2 rqt 128 rq 6 len 193 ret -110 > Jan 3 13:47:45 localhost usb 2-2: control timeout on ep0in > Jan 3 13:47:45 localhost usbfs: USBDEVFS_CONTROL failed cmd usbmodules dev > 2 rqt 128 rq 6 len 18 ret -110 > > [......] > > Jan 3 13:47:56 localhost usb 2-2: control timeout on ep0in > Jan 3 13:47:56 localhost usbfs: USBDEVFS_CONTROL failed cmd usbmodules dev > 2 rqt 128 rq 6 len 193 ret -110 > Jan 3 13:47:56 localhost usb 2-2: control timeout on ep0in > Jan 3 13:47:56 localhost usbfs: USBDEVFS_CONTROL failed cmd usbmodules dev > 2 rqt 128 rq 6 len 193 ret -110 > Jan 3 13:47:56 localhost usb 2-2: control timeout on ep0in > Jan 3 13:47:56 localhost usbfs: USBDEVFS_CONTROL failed cmd usbmodules dev > 2 rqt 128 rq 6 len 193 ret -110 > > Then I disconnect the adapter. > > Jan 3 13:48:45 localhost usb 2-2: USB disconnect, address 2 > Jan 3 13:48:45 localhost hcid[4695]: HCI dev 0 unregistered > > When I reconnect it I've got the same errors. > > On kernels 2.4.20-21-22-23 I've got the same errors but with > localhost usb_control/bulk_msg: timeout > and not > localhost usb 2-2: control timeout on ep0in > > On the bluez mailinglist they said that this is probably a KNOW usb-uhci > problem but I can't find any solution or patch to it. I've tried unloading > and reloading the modules, using noapic and acpi=no, disabling the ehci but > nothing changed. > > I've got a via chipset :-( and I've disabled the USB 2.0 capabilities (but > nothing changed too). > > 00:00.0 Host bridge: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge > Subsystem: VIA Technologies, Inc. VT8377 [KT400 AGP] Host Bridge > Flags: bus master, 66Mhz, medium devsel, latency 8 > Memory at d0000000 (32-bit, prefetchable) [size=128M] > Capabilities: [a0] AGP version 2.0 > Capabilities: [c0] Power Management version 2 > > 00:01.0 PCI bridge: VIA Technologies, Inc. VT8235 PCI Bridge (prog-if 00 > [Normal decode]) > Flags: bus master, 66Mhz, medium devsel, latency 0 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > Memory behind bridge: e8000000-e9ffffff > Prefetchable memory behind bridge: d8000000-e7ffffff > Capabilities: [80] Power Management version 2 > > 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 > [UHCI]) > Subsystem: Unknown device 1695:3005 > Flags: bus master, medium devsel, latency 32, IRQ 201 > I/O ports at d000 [size=32] > Capabilities: [80] Power Management version 2 > > 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 > [UHCI]) > Subsystem: Unknown device 1695:3005 > Flags: bus master, medium devsel, latency 32, IRQ 201 > I/O ports at d400 [size=32] > Capabilities: [80] Power Management version 2 > > 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) (prog-if 00 > [UHCI]) > Subsystem: Unknown device 1695:3005 > Flags: bus master, medium devsel, latency 32, IRQ 201 > I/O ports at d800 [size=32] > Capabilities: [80] Power Management version 2 > > > If this isn't the right place excuse me. Bye! -- Simone Gotti <[EMAIL PROTECTED]> ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
