Skip to contentSkip to conversation

3.0.3 + Bluetooth USB Dongle: no success without noapic

DISCUSSION Harald Dunkel 3 participants 5 messages Aug 28, 2011 – Sep 1, 2011

lore
Share & tools
lore
#0 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi folks,

If I plugin a Cambridge Bluetooth USB dongle, then I get

[   91.589073] usb 2-5: new full speed USB device number 8 using ohci_hcd
[   91.709067] usb 2-5: device descriptor read/64, error -62
[   91.930059] usb 2-5: device descriptor read/64, error -62
[   92.144054] usb 2-5: new full speed USB device number 9 using ohci_hcd
[   92.264073] usb 2-5: device descriptor read/64, error -62
[   92.485064] usb 2-5: device descriptor read/64, error -62
[   92.699091] usb 2-5: new full speed USB device number 10 using ohci_hcd
[   93.103040] usb 2-5: device not accepting address 10, error -62
[   93.216102] usb 2-5: new full speed USB device number 11 using ohci_hcd
[   93.620038] usb 2-5: device not accepting address 11, error -62
[   93.620072] hub 2-0:1.0: unable to enumerate USB device on port 5

Booting with noapic fixes this problem.

The PC is an Acer Aspire R3600 with the most recent Bios. Kernel is 3.0.3 (amd64). lsusb says:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 04fc:0c15 Sunplus Technology Co., Ltd SPIF215A SATA bridge Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 003: ID 1241:e000 Belkin
Bus 002 Device 004: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard Bus 002 Device 005: ID 046d:c525 Logitech, Inc. MX Revolution Cordless Mouse

The dongle works fine in other PCs (without OHCI).

Any helpful comment would be highly appreciated. Please mail if I can help to track this down.

Regards

Harri
- -------------------------------------------------------------------
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a12 Cambridge Silicon Radio, Ltd
idProduct 0x0001 Bluetooth Dongle (HCI mode)
bcdDevice 31.64

  iManufacturer           0
  iProduct                2 BT2.0
  iSerial                 0
  bNumConfigurations      1

Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 177
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0010 1x 16 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0000 1x 0 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0009 1x 9 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0011 1x 17 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0019 1x 25 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0021 1x 33 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type None
Usage Type Data
wMaxPacketSize 0x0031 1x 49 bytes
bInterval 1
Device Status: 0x0001
Self Powered
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5aDz8ACgkQUTlbRTxpHjekIQCeJZgurJ77fxv+7/yG7j96TTRN JSkAoI6EYMKFS3khu3SodcRYyuF+xGZj
=g/4P
-----END PGP SIGNATURE-----

#1 lore raw

Am Sonntag, 28. August 2011, 11:49:57 schrieb Harald Dunkel:

Quoted 16 lines

Hi folks,

If I plugin a Cambridge Bluetooth USB dongle, then I get

[   91.589073] usb 2-5: new full speed USB device number 8 using ohci_hcd
[   91.709067] usb 2-5: device descriptor read/64, error -62
[   91.930059] usb 2-5: device descriptor read/64, error -62
[   92.144054] usb 2-5: new full speed USB device number 9 using ohci_hcd
[   92.264073] usb 2-5: device descriptor read/64, error -62
[   92.485064] usb 2-5: device descriptor read/64, error -62
[   92.699091] usb 2-5: new full speed USB device number 10 using ohci_hcd
[   93.103040] usb 2-5: device not accepting address 10, error -62
[   93.216102] usb 2-5: new full speed USB device number 11 using ohci_hcd
[   93.620038] usb 2-5: device not accepting address 11, error -62
[   93.620072] hub 2-0:1.0: unable to enumerate USB device on port 5
Quoted 1 line

Booting with noapic fixes this problem.

Do any other USB devices work on that OHCI?

Regards
Oliver

#2 lore raw

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 5 lines · Oliver Neukum

Am Sonntag, 28. August 2011, 11:49:57 schrieb Harald Dunkel:

Quoted 4 lines

Hi folks,

If I plugin a Cambridge Bluetooth USB dongle, then I get

Quoted 8 lines
Quoted 5 lines
[   91.589073] usb 2-5: new full speed USB device number 8 using ohci_hcd [   91.709067] usb 2-5: device descriptor read/64, error -62 [   91.930059] usb 2-5: device descriptor read/64, error -62 [   92.144054] usb 2-5: new full speed USB device number 9 using ohci_hcd [   92.264073] usb 2-5:

device descriptor read/64, error -62 [ 92.485064] usb 2-5: device descriptor read/64, error -62 [ 92.699091] usb 2-5: new full speed USB device number 10 using ohci_hcd [ 93.103040] usb 2-5: device not accepting address 10, error -62 [ 93.216102] usb 2-5: new full speed USB device
number 11 using ohci_hcd [ 93.620038] usb 2-5: device not accepting address 11, error -62 [ 93.620072] hub 2-0:1.0: unable to enumerate USB device on port 5

Booting with noapic fixes this problem.

Do any other USB devices work on that OHCI?

Sorry for the delay.

It seems that this problem comes up by chance (with or without noapic). If I move the dongle to another USB slot then the problem is gone. By now the Bluetooth dongle is the only device showing this problem.

Here is the output of lsusb with all devices plugged in and working:

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04fc:0c15 Sunplus Technology Co., Ltd SPIF215A SATA bridge Bus 001 Device 007: ID 046d:c525 Logitech, Inc. MX Revolution Cordless Mouse Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 009: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard

Removing the usb drive or the keyboard doesn't make the bluetooth dongle more stable.

Regards

Harri
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk5fGcYACgkQUTlbRTxpHjcZyACbBZ4ZUWRS80i74DB250dd4c55 JgkAmwdl9FZIgtDrfEiUBkB9bY9saGtu
=unbE
-----END PGP SIGNATURE-----

#3 lore raw

Am Donnerstag, 1. September 2011, 07:36:10 schrieb Harald Dunkel:

Quoted 2 lines · Oliver Neukum
Quoted 1 line

Am Sonntag, 28. August 2011, 11:49:57 schrieb Harald Dunkel:

Hi,

Quoted 26 lines
Quoted 8 lines
Quoted 5 lines
[   91.589073] usb 2-5: new full speed USB device number 8 using ohci_hcd [   91.709067] usb 2-5: device descriptor read/64, error -62 [   91.930059] usb 2-5: device descriptor read/64, error -62 [   92.144054] usb 2-5: new full speed USB device number 9 using ohci_hcd [   92.264073] usb 2-5:

device descriptor read/64, error -62 [ 92.485064] usb 2-5: device descriptor read/64, error -62 [ 92.699091] usb 2-5: new full speed USB device number 10 using ohci_hcd [ 93.103040] usb 2-5: device not accepting address 10, error -62 [ 93.216102] usb 2-5: new full speed USB device
number 11 using ohci_hcd [ 93.620038] usb 2-5: device not accepting address 11, error -62 [ 93.620072] hub 2-0:1.0: unable to enumerate USB device on port 5

Booting with noapic fixes this problem.

Do any other USB devices work on that OHCI?

Sorry for the delay.

It seems that this problem comes up by chance (with or without noapic). If I move the dongle to another USB slot then the problem is gone. By now the Bluetooth dongle is the only device showing this problem.

Here is the output of lsusb with all devices plugged in and working:

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04fc:0c15 Sunplus Technology Co., Ltd SPIF215A SATA bridge Bus 001 Device 007: ID 046d:c525 Logitech, Inc. MX Revolution Cordless Mouse Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 009: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard

Quoted 2 lines

Removing the usb drive or the keyboard doesn't make the bluetooth dongle more stable.

Voodoo. Does anybody have any ideas?

Regards
Oliver

#4 lore raw
Quoted 32 lines · Oliver Neukum

Am Donnerstag, 1. September 2011, 07:36:10 schrieb Harald Dunkel:

Quoted 2 lines · Oliver Neukum
Quoted 1 line

Am Sonntag, 28. August 2011, 11:49:57 schrieb Harald Dunkel:

Hi,

Quoted 26 lines
Quoted 8 lines
Quoted 5 lines
[   91.589073] usb 2-5: new full speed USB device number 8 using ohci_hcd [   91.709067] usb 2-5: device descriptor read/64, error -62 [   91.930059] usb 2-5: device descriptor read/64, error -62 [   92.144054] usb 2-5: new full speed USB device number 9 using ohci_hcd [   92.264073] usb 2-5:

device descriptor read/64, error -62 [ 92.485064] usb 2-5: device descriptor read/64, error -62 [ 92.699091] usb 2-5: new full speed USB device number 10 using ohci_hcd [ 93.103040] usb 2-5: device not accepting address 10, error -62 [ 93.216102] usb 2-5: new full speed USB device
number 11 using ohci_hcd [ 93.620038] usb 2-5: device not accepting address 11, error -62 [ 93.620072] hub 2-0:1.0: unable to enumerate USB device on port 5

Booting with noapic fixes this problem.

Do any other USB devices work on that OHCI?

Sorry for the delay.

It seems that this problem comes up by chance (with or without noapic). If I move the dongle to another USB slot then the problem is gone. By now the Bluetooth dongle is the only device showing this problem.

Here is the output of lsusb with all devices plugged in and working:

Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 04fc:0c15 Sunplus Technology Co., Ltd SPIF215A SATA bridge Bus 001 Device 007: ID 046d:c525 Logitech, Inc. MX Revolution Cordless Mouse Bus 001 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 009: ID 04f2:0402 Chicony Electronics Co., Ltd Genius LuxeMate i200 Keyboard

Quoted 4 lines
Quoted 2 lines

Removing the usb drive or the keyboard doesn't make the bluetooth dongle more stable.

Voodoo. Does anybody have any ideas?

It sounds like the dongle is making a bad electrical connection, or there's a bad voltage, or something like that.

Alan Stern