linux-kernel - Re: 3.0.3 + Bluetooth USB Dongle: no success without noapic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E5F19CA.7080909@afaics.de>
Date:	Thu, 01 Sep 2011 07:36:10 +0200
From:	Harald Dunkel <harri@...ics.de>
To:	Oliver Neukum <oliver@...kum.org>
CC:	Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: 3.0.3 + Bluetooth USB Dongle: no success without noapic

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

On 08/28/11 12:07, Oliver Neukum wrote:
> Am Sonntag, 28. August 2011, 11:49:57 schrieb Harald Dunkel:
>> 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.
> 
> 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-----
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/