Bug 580437
| Summary: | unstable bluetooth networking with Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Igor Bukanov <igor> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 13 | CC: | ajeet_singh1978, anton, dougsland, gansalmon, itamar, jonathan, kernel-maint, markhobley |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-06-27 15:28:21 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Igor Bukanov
2010-04-08 09:38:14 UTC
Try adding usbcore.autosuspend=0 to the kernel boot options. (In reply to comment #1) > Try adding usbcore.autosuspend=0 to the kernel boot options. Thanks, that fixed the issue. This doesn't fix anything for me. [root@virus ~]# hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1 UP RUNNING RX bytes:687 acl:0 sco:0 events:22 errors:0 TX bytes:88 acl:0 sco:0 commands:26 errors:5 Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH HOLD SNIFF PARK Link mode: SLAVE ACCEPT Can't read local name on hci0: Connection timed out (110) [root@virus ~]# lsusb Bus 002 Device 012: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 002 Device 004: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 05ca:1814 Ricoh Co., Ltd Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [root@virus ~]# dmesg [ 5000.984154] usb 2-1.2: USB disconnect, address 11 [ 5000.984190] btusb_intr_complete: hci0 urb f1d2f700 failed to resubmit (19) [ 5000.984260] btusb_bulk_complete: hci0 urb f1d2f400 failed to resubmit (19) [ 5000.984266] btusb_bulk_complete: hci0 urb f1d2fd00 failed to resubmit (19) [ 5000.984364] btusb_send_frame: hci0 urb f1d36f80 submission failed [ 5004.480408] usb 2-1.2: new full speed USB device using ehci_hcd and address 12 [ 5004.567774] usb 2-1.2: New USB device found, idVendor=0a12, idProduct=0001 [ 5004.567779] usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 5006.530932] hci_cmd_task: hci0 command tx timeout [ 5008.427149] hci_cmd_task: hci0 command tx timeout [ 5010.040226] hci_cmd_task: hci0 command tx timeout [ 5011.804080] hci_cmd_task: hci0 command tx timeout [ 5013.665181] hci_cmd_task: hci0 command tx timeout [ 5026.853835] lo: Disabled Privacy Extensions Please suggest some quick fixes, I have been searching for this since long time. My BroadCom dongle used to work with this one. But the new Cambridge one doesn't seems to work with any available work around on net. I have added usbcore.autosuspend=-1 to kernel parameter as well, doesn't seems to do any effect. I have modified the main.conf to RememberedPower=false from true. I am using Dell Latitude E6510 & Fedora 13 i686 platform. Regards, AJeet Kernel bug #10126 regarding Cambridge Silicon Radio devices is related to this bug. This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |