AR3012 Bluetooth not start after an upgrade to 4.4.0-127

Bug #1773635 reported by Andrey Mokrousov
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I have an Atheros mixed WiFi+Bluetooth device which worked nice on a kernels prior to 4.4.0-127
But unfortunately after last upgrade (from 4.4.0-124 to 4.4.0-127) bluetooth is unable to start - no bluetooth indicator appears in notifications tray and no device could be discovered or connected to via bluetooth.

Tailing a syslog provides following lines, related to bluetooth:
May 27 12:15:16 K43T kernel: [ 228.102799] usbcore: registered new interface driver btusb
May 27 12:15:16 K43T kernel: [ 228.109562] Bluetooth: hci0: don't support firmware rome 0x1020200
May 27 12:15:16 K43T systemd-udevd[4634]: Process '/bin/hciconfig hci0 up' failed with exit code 1.
May 27 12:15:16 K43T kernel: [ 228.112017] Bluetooth: hci0: don't support firmware rome 0x1020200

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-127-generic 4.4.0-127.153
ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
Uname: Linux 4.4.0-127-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: insanedeveloper 1937 F.... pulseaudio
 /dev/snd/controlC0: insanedeveloper 1937 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun May 27 12:33:42 2018
HibernationDevice: RESUME=UUID=4a7e8ac6-783b-4a23-bfa9-8130cfef7945
InstallationDate: Installed on 2015-11-28 (910 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: ASUSTeK Computer Inc. K43TK
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic.efi.signed root=UUID=7dbd7b42-e67f-4416-8f6d-6c918e744fb7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-127-generic N/A
 linux-backports-modules-4.4.0-127-generic N/A
 linux-firmware 1.157.18
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2017-01-08 (503 days ago)
dmi.bios.date: 03/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 206
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K43TK
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd03/20/2012:svnASUSTeKComputerInc.:pnK43TK:pvr1.0:rvnASUSTeKComputerInc.:rnK43TK:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K43TK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Andrey Mokrousov (insane-developer) wrote :
description: updated
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Please try this kernel
https://people.canonical.com/~khfeng/lp1773635/

Possible regression from this commit:
commit c9829dd3f00809ccf10afeb904ba5c53c3c3d6e7
Author: Takashi Iwai <email address hidden>
Date: Thu Mar 15 17:02:34 2018 +0100

    Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174

    BugLink: http://bugs.launchpad.net/bugs/1764973

    commit f44cb4b19ed40b655c2d422c9021ab2c2625adb6 upstream.

    The Atheros 1525/QCA6174 BT doesn't seem working properly on the
    recent kernels, as it tries to load a wrong firmware
    ar3k/AthrBT_0x00000200.dfu and it fails.

    This seems to have been a problem for some time, and the known
    workaround is to apply BTUSB_QCA_ROM quirk instead of BTUSB_ATH3012.

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: needs-bisect
tags: removed: needs-bisect
Revision history for this message
Andrey Mokrousov (insane-developer) wrote :

It seems that the build provided at https://people.canonical.com/~khfeng/lp1773635/ resolves the problem.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Do you have the problem with latest mainline kernel?

Revision history for this message
Andrey Mokrousov (insane-developer) wrote :
Revision history for this message
Danny Smith (dsnt02518) wrote :

I seem to have the same problem (Dell XPS L421X). Bluetooth failing on 4.4.0-127, but works on 4.4.0-124.

Happy to provide any logs/diags under each kernel if you let me know what would be useful.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

This commit fixes the issue.

commit 544a591668813583021474fa5c7ff4942244d654
Author: Hans de Goede <email address hidden>
Date: Thu Apr 26 14:18:19 2018 +0200

    Revert "Bluetooth: btusb: Fix quirk for Atheros 1525/QCA6174"

    Commit f44cb4b19ed4 ("Bluetooth: btusb: Fix quirk for Atheros
    1525/QCA6174") is causing bluetooth to no longer work for several
    people, see: https://bugzilla.redhat.com/show_bug.cgi?id=1568911

    So lets revert it for now and try to find another solution for
    devices which need the modified quirk.

    Cc: <email address hidden>
    Cc: Takashi Iwai <email address hidden>
    Signed-off-by: Hans de Goede <email address hidden>
    Signed-off-by: Marcel Holtmann <email address hidden>

This commit will be included in later kernel updates.

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1542743, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.