Skip to contentSkip to conversation

[2.4.21] bluez/usb-ohci bulk_msg timeout

DISCUSSION Florian Lohoff 2 participants 5 messages Jul 18, 2003 – Jul 25, 2003

lore
Share & tools
lore

Florian Lohoff

author
#0 lore raw

Hi,
since 2.4.21 + mh2 bluez patch i am seeing these errors. 2.4.20 + mh7 bluez patch did not show these errors. Results are very instable Bluetooth connections.

[...]
ohci1394: $Rev: 896 $ Ben Collins <[email protected]>
ohci1394_0: OHCI-1394 1.1 (PCI): IRQ=3D[9] MMIO=3D[e8102000-e81027ff] Max=
Packet=3D[2048]
ieee1394: Host added: Node[00:1023] GUID[0800460300de6e57] [Linux OHCI-13= 94]
usb.c: registered new driver usbdevfs
usb.c: registered new driver hub
PCI: Enabling device 00:0f.0 (0010 -> 0012)
usb-ohci.c: USB OHCI at membase 0xd007b000, IRQ 9
usb-ohci.c: usb-00:0f.0, ALi Corporation. [ALi] USB 1.1 Controller usb.c: new USB bus registered, assigned bus number 1
hub.c: USB hub found
hub.c: 2 ports detected
usb-ohci.c: USB OHCI at membase 0xc00e0000, IRQ 9
usb-ohci.c: usb-00:14.0, ALi Corporation. [ALi] USB 1.1 Controller (#2) usb.c: new USB bus registered, assigned bus number 2
hub.c: USB hub found
hub.c: 2 ports detected
hub.c: new USB device 00:0f.0-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x54c/0x69) is not claimed by any active dri= ver.

[...]
hub.c: new USB device 00:0f.0-2, assigned address 3
usb.c: USB device 3 (vend/prod 0x44e/0x3001) is not claimed by any active d= river.
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -110
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 193 ret -110 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 49 ret -110
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 49 ret -110 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -110
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -110
eth1: New link status: AP Changed (0003)
usb.c: USB disconnect on device 00:0f.0-2 address 3

[ ... retry ... ]

hub.c: new USB device 00:0f.0-2, assigned address 4
usb.c: USB device 4 (vend/prod 0x44e/0x3001) is not claimed by any active d= river.
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 193 ret -110
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 9 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 193 ret -110
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 18 ret -75
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 18 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 4 rqt 128 rq 6 len 18 ret -110 BlueZ Core ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <[email protected]>
BlueZ HCI USB driver ver 2.4 Copyright (C) 2000,2001 Qualcomm Inc Written 2000,2001 by Maxim Krasnyansky <[email protected]> usb.c: registered new driver hci_usb
BlueZ RFCOMM ver 1.0
Copyright (C) 2002 Maxim Krasnyansky <[email protected]> Copyright (C) 2002 Marcel Holtmann <[email protected]>
BlueZ L2CAP ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <[email protected]> usb.c: USB disconnect on device 00:0f.0-2 address 4

[ ... retry ... ]

hub.c: new USB device 00:0f.0-2, assigned address 5 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len 9 ret -110
usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len 9 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len 193 ret -110
usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len 18 ret -75
usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len 18 ret -75 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 5 rqt 128 rq 6 len 9 ret -110

Flo

Signature · 2 lines
Florian Lohoff                  [email protected]             +49-171-2280134
                        Heisenberg may have been here.
#1 lore raw
Quoted 4 lines · Florian Lohoff

Hi,
since 2.4.21 + mh2 bluez patch i am seeing these errors. 2.4.20 + mh7 bluez patch did not show these errors. Results are very instable Bluetooth connections.

Those errors don't seem to be related to the driver update. But you could try this. In drivers/bluetooth/hci_usb.h set HCI_MAX_BULK_TX define to 1 (instead of 4) and rebuild the module. Does it make any difference ?

Max

author
#2 lore raw
Quoted 9 lines · Max Krasnyansky
Quoted 4 lines · Florian Lohoff

Hi,
since 2.4.21 + mh2 bluez patch i am seeing these errors. 2.4.20 + mh7 bluez patch did not show these errors. Results are very instable Bluetooth connections.

Those errors don't seem to be related to the driver update. But you could try this. In drivers/bluetooth/hci_usb.h set HCI_MAX_BULK_TX define to 1 (instead of 4) and rebuild the module. Does it make any difference ?

Doesnt help at all - So the OHCI changes are to blame ?

Flo

Signature · 2 lines
Florian Lohoff                  [email protected]             +49-171-2280134
                        Heisenberg may have been here.
#3 lore raw
Quoted 7 lines · Florian Lohoff
Quoted 6 lines · Max Krasnyansky
Quoted 4 lines · Florian Lohoff

Hi,
since 2.4.21 + mh2 bluez patch i am seeing these errors. 2.4.20 + mh7 bluez patch did not show these errors. Results are very instable Bluetooth connections.

Quoted 5 lines
Quoted 3 lines

Those errors don't seem to be related to the driver update. But you could try this. In drivers/bluetooth/hci_usb.h set HCI_MAX_BULK_TX define to 1 (instead of 4) and rebuild the module. Does it make any difference ?

Doesnt help at all - So the OHCI changes are to blame ?

Probably. Could try the prev revision of the HCI USB driver though. ie The one without SCO support. Just copy hci_usb.[ch] over from older kernel and see if it works with newer OHCI.

Max

author
#4 lore raw
Quoted 2 lines · Max Krasnyansky

Probably. Could try the prev revision of the HCI USB driver though. ie The one without SCO support. Just copy hci_usb.[ch] over from older kernel and see if it works with newer OHCI.

I tried the ones from 2.4.20 and the same error messages appear - So i think its the OHCI stuff - It got a some major changes it seems from the 2.4.21 patch ...

Linux version 2.4.21-vaio3 (root@paradigm) (gcc version 2.95.4 20011002 (Debian prerelease)) #1 Fri Jul 25 13:12:06 CEST 2003

[...]

hub.c: new USB device 00:0f.0-2, assigned address 3
usb.c: USB device 3 (vend/prod 0x44e/0x3001) is not claimed by any active driver. usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -110 BlueZ Core ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <[email protected]>
BlueZ HCI USB driver ver 2.1 Copyright (C) 2000,2001 Qualcomm Inc Written 2000,2001 by Maxim Krasnyansky <[email protected]>
usb.c: registered new driver hci_usb
usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 193 ret -110 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 193 ret -110 usb_control/bulk_msg: timeout
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -110 BlueZ RFCOMM ver 1.0
Copyright (C) 2002 Maxim Krasnyansky <[email protected]>
Copyright (C) 2002 Marcel Holtmann <[email protected]>
usbdevfs: USBDEVFS_CONTROL failed dev 3 rqt 128 rq 6 len 9 ret -75 BlueZ L2CAP ver 2.3 Copyright (C) 2000,2001 Qualcomm Inc
Written 2000,2001 by Maxim Krasnyansky <[email protected]>
CSLIP: code copyright 1989 Regents of the University of California PPP generic driver version 2.4.2

Flo

Signature · 2 lines
Florian Lohoff                  [email protected]             +49-171-2280134
                        Heisenberg may have been here.