Bug 1248974
| Summary: | Update breaks bluetooth in GNOME on macbook pro | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gerard Ryan <fedora> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | gansalmon, itamar, jonathan, kernel-maint, litewhatever, madhu.chinakonda, mchehab |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-4.1.4-100.fc21 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-12 06:58:10 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Gerard Ryan
2015-07-31 08:58:51 UTC
Here's some dmesg output related to Bluetooth: [grdryn@redhat ~]$ dmesg -k | grep Bluetooth [ 2.490166] usb 1-8.3: Product: Bluetooth USB Host Controller [ 10.746302] Bluetooth: Core ver 2.20 [ 10.746424] Bluetooth: HCI device and connection manager initialized [ 10.746426] Bluetooth: HCI socket layer initialized [ 10.746428] Bluetooth: L2CAP socket layer initialized [ 10.746435] Bluetooth: SCO socket layer initialized [ 10.752110] Bluetooth: hci0: BCM: Read verbose config info failed (-16) [ 10.897048] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.897050] Bluetooth: BNEP filters: protocol multicast [ 10.897053] Bluetooth: BNEP socket layer initialized ^It was the "hci0: BCM: Read verbose config info failed (-16)" that shows up in red that made me think of providing this info. Let me know if there's any other info that you would like me to provide. Looks like bug has been identified in upstream: https://bugzilla.kernel.org/show_bug.cgi?id=100651 Perhaps someone could apply the patch/build kernel package for us to test? (In reply to Kristjan Kullerkann from comment #2) > Looks like bug has been identified in upstream: > https://bugzilla.kernel.org/show_bug.cgi?id=100651 > > Perhaps someone could apply the patch/build kernel package for us to test? If I read the bug correctly, it was included in upstream 4.1.4. We have that built and in updates-testing already. You should be able to test it from there and let us know. Sorry, I'm unable to find 4.1.4 in updates-testing. It hasn't been staged yet? Never mind, found it: https://admin.fedoraproject.org/updates/kernel-4.1.4-200.fc22?_csrf_token=6ef7cba4bc74cb731bb96312542a36026891a8aa It's fixed in 4.1.4, thank you! kernel-4.1.4-200.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/kernel-4.1.4-200.fc22 kernel-4.1.4-100.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/kernel-4.1.4-100.fc21 Package kernel-4.1.4-200.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-4.1.4-200.fc22' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-12908/kernel-4.1.4-200.fc22 then log in and leave karma (feedback). kernel-4.1.4-200.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report. kernel-4.1.4-100.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report. |