168c:0036 [Acer Aspire E1-572] ath9k QCA9565/AR9565/QCWB335 Bluetooth works sporadic

[Joshua]

I got myself a brand new Acer Aspire E1-572-54204G50Mnkk, because of the shine new Haswell hardware I choose to install Ubuntu 13.10 Beta 2.

This laptop uses a Atheros AR9565 802.11 b/g/n 1 × 1 WiFi + Bluetooth 4.0 combination adapter, Wireless is working fine. But Bluetooth doesn't, it seems to be successfully detected but I can't see any other Bluetooth devices and they can't see me too:
Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless Network Adapter [168c:0036] (rev 01)
 Subsystem: Foxconn International, Inc. Device [105b:e068]

---
ApportVersion: 2.12.4-0ubuntu1
Architecture: amd64
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-10-12 (0 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Tags: saucy
Uname: Linux 3.12.0-031200rc4-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
---
ApportVersion: 2.12.5-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: joshua 1348 F.... pulseaudio
 /dev/snd/controlC0: joshua 1348 F.... pulseaudio
DistroRelease: Ubuntu 13.10
InstallationDate: Installed on 2013-10-12 (8 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20130925.1)
MachineType: Acer Aspire E1-572
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=de_DE
 TERM=xterm
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic.efi.signed root=UUID=287c8de2-616f-42ec-998d-1ac09ffb2d8a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-12-generic N/A
 linux-backports-modules-3.11.0-12-generic N/A
 linux-firmware 1.116
Tags: saucy
Uname: Linux 3.11.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 05/21/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_HW
dmi.board.vendor: Acer
dmi.board.version: V2.04
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.04:bd05/21/2013:svnAcer:pnAspireE1-572:pvrV2.04:rvnAcer:rnEA50_HW:rvrV2.04:cvnAcer:ct10:cvrChassisVersion:
dmi.product.name: Aspire E1-572
dmi.product.version: V2.04
dmi.sys.vendor: Acer

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1237296/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1237296

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joshua (njj)]

I cant run apport-collect because I wiped my drive and installed another system after Ubuntu 13.10 didn't worked.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc4-saucy/

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

apport information

[Joshua (njj)]

The BT device ID was missing in the driver. After recompiling the ath3k and btusb modules with this patch bluetooth works. But I had to modprobe ath3k manually so something is still not working right.

Can this patch be rolled out with the next saucy kernel update or do I have to wait till trusty thar?

[Joseph Salisbury (jsalisbury)]

I don't see that this patch is in the mainline(3.12-rc7) tree as of yet. Do you know the status of it upstream?

[Joshua (njj)]

Not exactly, I got this from the developer through the ath9k-devel mailinglist. He wanted to send it some way upstream yesterday evening.

[Joshua (njj)]

Change the unoffical patch with the link to upstream git at kernel.org

[Joseph Salisbury (jsalisbury)]

I built a Saucy test kernel with the patch mentioned in comment #22. The test kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1237296/

Can you test this kernel and post back if it resolves this bug?

[Joshua (njj)]

No it doesn't, dmesg shows the following:

[ 7.791682] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096
[ 7.791693] Bluetooth: Loading patch file failed
[ 7.791704] ath3k: probe of 2-5:1.0 failed with error -110
[ 7.791747] usbcore: registered new interface driver ath3k

[Joseph Salisbury (jsalisbury)]

Thanks for testing, Joshua. It sounds like you were able to get the device working, using the patch, per comment #19. Which kernel version did you apply the patch against? Was it the Ubuntu Saucy kernel, or another version?

[Joshua (njj)]

I'm not that experienced in this kind of things. So this is what I did:

apt-get install linux-source
unpack the source to some place and apply the patch
cp .conf and Module.symvers of the current saucy kernel
make prepare
make scripts
make M=drivers/bluetooth
cp the new ath3k.ko and btusb.ko to /lib/modules/3.11.0-12-generic/kernel/drivers/bluetooth/

After a reboot the ath3k modul didn't got loaded, but after issuing "modprobe ath3k" the device worked.

[Joseph Salisbury (jsalisbury)]

Do you still have your test kernel available? If so, can you boot your kernel and run:
dpkg -l | grep linux-firmware

Then also boot my test kernel and run the same command:
dpkg -l | grep linux-firmware

[Joshua (njj)]

Yes and no, as I tried to explain, I didn't compiled a whole test kernel. I only compiled the ath3k and btusb modules and copied them into the directory of the latest default kernel at that time, 3.11.0-12-generic. And linux-firmware package was version 1.116 both times.

Offtopic: I have some other issues, one of them is a shutdown problem. So I'm doing a lot of shutdown and reboot testing atm.
Ontopic: I recently noticed that bluetooth suddenly worked after startup (I'm using your kernel all the time atm). After the next reboot it was broken again. And some reboots later it worked again. But I can't reproduce the reason, no matter how often I try. Some rare times it works and I can't figure out why.

I'm using a SSD and UEFI so startup is very fast, could it be, that there is some problem with the loading order most of the time?

[Joshua (njj)]

If I copy the modules I compiled into the modules dir of your kernel bluetooth works fine. These are the modules I compiled.

[Joshua (njj)]

Forget about my last post, after a reboot bluetooth is broken again. "Loading patch file failed" Seriously wtf!

[Joseph Salisbury (jsalisbury)]

Can you give the latest 3.12 kernel[0] a test?

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-trusty/

[Joshua (njj)]

It definitly won't, because the patch arrive upstream just 3 days ago, excatly 2013-11-18 15:46:05.

But I gave 3.12.0-999.201311200458 kernel[0] a try, without success. The bluetooth service doesn't start at all: http://paste.ubuntu.com/6452404/

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2013-11-20-trusty/

[Joshua (njj)]

Somehow through Google I ended up reading this article [0] and followed the instructions under "Kernel Event Sent to Udev". But no event: "If you do not see an event with these three items, then the kernel request is not being propagated to udev. You should file a bug at this point against the udev package." These are the events [1] which are logged.

However dunno if this helpful in any way or even has todo with the bug at all, just wanted to tell.

[0] https://wiki.ubuntu.com/Kernel/Firmware
[1] http://paste.ubuntu.com/6453360/

[Joseph Salisbury (jsalisbury)]

Yeah, I don't see the patch mentioned in comment #23 in Linus' tree as of yet. It may not land until v3.13-rc1.

[Joshua (njj)]

rc3 and it still hasn't landed, I'm a bit depressed. Could you propably build a rc3 test kernel with patch applied, so I could test if something has changed?

[Joseph Salisbury (jsalisbury)]

You mentioned that you got the patch from the author on the ath9k-devel mailinglist. Can you ping the patch author and see if you submitted the patch upstream or if there is a reason why he did not? Once the patch lands upstream, we can cherry-pick it into the Ubuntu kernel.

[Joshua (njj)]

I successfully flashed the new BIOS version and used the patched kernel from comment #24 but the problem is still the same (Bluetooth: Loading patch file failed).

Full dmesg output: http://paste.ubuntu.com/6681124/
The dmidecode output is as expected:
V2.12
11/04/2013

[joey reichard (smokin420papi)]

ive tried everything in the post and it does not work ive tried xhci and logmon and nothing worked i know nothing about commands it wont load module

[Vasil Yakauleu (vasilbelarus)]

reproducible on LTS 14.04 with latest updates on Packard Bell Z5WT1 laptop

[penalvch (penalvch)]

Vasil Yakauleu, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Antonio J. de Oliveira (ajoliveira)]

Hi. no way, the module is useless bluetooth does not work,never on my hardware. have you checked it? need help in debugging? All the best

[penalvch (penalvch)]

Antonio J. de Oliveira, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Antonio J. de Oliveira (ajoliveira)]

ApportVersion: 2.14.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ajoliveira 3380 F.... panel-21-mixer
                      ajoliveira 3426 F.... pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=a116cc7d-cad3-4aa7-99cf-9e2e5c609029
InstallationDate: Installed on 2014-03-19 (62 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
MachineType: Acer Aspire E1-570G
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-20-generic root=UUID=08f4eaf7-f115-466c-b87f-000108c27cab ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-20-generic N/A
 linux-backports-modules-3.13.0-20-generic N/A
 linux-firmware 1.127.2
Tags: trusty
Uname: Linux 3.13.0-20-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-03-29 (52 days ago)
UserGroups: adm audio bumblebee cdrom dip lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 07/30/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V2.02
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EA50_CX
dmi.board.vendor: Acer
dmi.board.version: V2.02
dmi.chassis.asset.tag: Acer Asset Tag String
dmi.chassis.type: 10
dmi.chassis.vendor: Insyde Corp.
dmi.chassis.version: V2.02
dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.02:bd07/30/2013:svnAcer:pnAspireE1-570G:pvrV2.02:rvnAcer:rnEA50_CX:rvrV2.02:cvnInsydeCorp.:ct10:cvrV2.02:
dmi.product.name: Aspire E1-570G
dmi.product.version: V2.02
dmi.sys.vendor: Acer

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

apport information

[Antonio J. de Oliveira (ajoliveira)]

Coudn't use ubuntu-bug. Reports kernel is not an official one. So opted for posting here. This bug looks like a duplicate of Bug #1287811 .

[penalvch (penalvch)]

Antonio J. de Oliveira, please do not apport-collect to another persons report. The reason you weren't able to use ubuntu-bug is because you are using an old kernel, which is not officially supported. Please update your kernel, and then file the new report.

[Antonio J. de Oliveira (ajoliveira)]

Ok, sorry for the inconvenience. This bug remains in 3.13.0-24 after I upgraded to it installing the linux-imagepackage and seems to be solved in 3.14.1-031401-generic. A quick fix in trusty seems to be what I did on my 64-bit system:

$ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401_3.14.1-031401.201404141220_all.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401-generic_3.14.1-031401.201404141220_amd64.deb

$ wget http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-image-3.14.1-031401-generic_3.14.1-031401.201404141220_amd64.deb

$ sudo dpkg -i linux-headers-3.14.1-*.deb linux-image-3.14.1-*.deb

Thanks.

[Antonio J. de Oliveira (ajoliveira)]

On 32-bit systems:

$ wget kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401_3.14.1-031401.201404141220_all.deb

$ wget kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-headers-3.14.1-031401-generic_3.14.1-031401.201404141220_i386.deb

$ wget kernel.ubuntu.com/~kernel-ppa/mainline/v3.14.1-trusty/linux-image-3.14.1-031401-generic_3.14.1-031401.201404141220_i386.deb

$ sudo dpkg -i linux-headers-3.14.1-*.deb linux-image-3.14.1-*.deb

Don't forget to reboot...

[LE BIDEAU (elbc)]

Any news on this issue ? with kernels older than 3.15 device 0cf3:311f is not recognized and with kernels equal or newer than 3.15 it works sporadic

[penalvch (penalvch)]

LE BIDEAU, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Joseph Salisbury (jsalisbury)]

This bug was nominated against a series that is no longer supported, ie saucy. The bug task representing the saucy nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Mauro (mauromol)]

I have the same wifi card on an HP ProBook 450 G1 laptop. In Linux Mint 17 KDE (based on Ubuntu 14.04) wifi works, Bluetooth doesn't.
Yesterday it couldn't find any Bluetooth devices, nor it was detectable by another Bluetooth device even if visible.
Today the Bluetooth adapter seems to have disappeared completely and I don't understand how it is possible (rfkill list shows only the wifi device, while previously it used to show the non-working Bluetooth device too...).

I read the whole report but I'm a bit lost. Was this bug fixed somewhere? Can we expect to have it working on an upcoming kernel upgrade for Trusty?

[penalvch (penalvch)]

Mauro, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Mauro (mauromol)]

Hi Christopher, in order to track my problem I downloaded the official Ubuntu Desktop Linux 14.04.1 amd64 image with a torrent file from the Ubuntu website, burnt it on a USB stick and booted from it. I reproduced this problem. However, when I type "ubuntu-bug linux" in a terminal, the following error message is shown, after the "collecting data" phase:
Problem in linux-image-3.13.0-32-generic
This is not an official Ubuntu package. Please remove any third-party package and try again.

However, I used the ISO image as-is and didn't install any third-party package!!

In this way, I can't proceed with the bug reporting. What's wrong?

[penalvch (penalvch)]

Mauro, please try http://cdimage.ubuntu.com/daily-live/current/ . If it still doesn't work, please contact me directly so as to not impede this report with non-relevant information.

[Mauro (mauromol)]

Hi Christopher,
I'm still writing here because I think this is useful to know for other people with this problem (affecting ath9k).
with http://cdimage.ubuntu.com/daily-live/current/vivid-desktop-amd64.iso Bluetooth works! However, is it useful to track it anyway for a possible backporting to Trusty? If so, which image should I use, since the 14.04.1 image is giving me the mentioned error with ubuntu-bug command?

Also please note that with Vivid there's a regression with the wireless button switch, I'm going to add a note to bug #1313196.

[Mauro (mauromol)]

oh well, it seems like with Trusty and kernel version 3.13.0-39-generic I just installed, Bluetooth is working correctly! So, I think this can be considered fixed, at least on my hardware.

[António J. de Oliveira (barcarossa-g)]

With Trusty 3.16.2-031602-generic #201409052035 SMP Sat Sep 6 00:36:44 UTC 2014 x86_64 x86_64 x86_64 bluetooth works as expected.

[Daniel van Vugt (vanvugt)]

This bug is 8 years old so we should defer to more current bugs like bug 1925318 and bug 1940759